• 0 Posts
  • 28 Comments
Joined 3 years ago
cake
Cake day: July 2nd, 2023

help-circle

  • Tetsuo@jlai.lutoSelfhosted@lemmy.world[AIT] The Codeberg ban on LLM content
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    3
    ·
    1 month ago

    https://malus.sh/

    AIs already pillaged all the code in the world. This is fighting a lost fight. We won’t manage to force big AI firms that literally props a country to stay afloat to make their AI “forget” or “untrained”.

    Regulators let the pillaging happen so now AI does know how to code. They dont imitate they truly code.

    But IMO the real fight is about things like malus that are the real dangerous and malevolent actor here. They will take your open source code and resell it to big businesses.



  • I worked for years on a large email infrastructure for a job and for me it’s absolutely not worth it either.

    I would prefer to take a subscription on a reputable host.

    Why?

    Because even if I do everything perfectly at setup (TLS, SPF, DKIM, DMARC) that will still be precarious.

    The security of SMTP is a patchwork of protocols added on top of it and a bunch of opaque reputation systems. If anything ever goes wrong with my email my domain’s reputation would fall. And that’s the thing, once your domain reputation goes too low, you can’t fix right away and say “my bad” and recover. Your mail will be silently blocked like Spam until a few days of sending perfectly clean emails. You need time to recover.

    So mail self hosting is accepting that at any time if you make a slight mistake, your communications to other will be almost impossible for days. And again since a lot of it is reputation based you can’t fix the issue and recover immediately.

    The business I was working for had everyday scenarios like that. A client that failed to update its DKIM and didn’t notice right away. When they do their reputation on for example Cisco’s platform is super low and we filter them as spam. And then it took days for them to recover even if they fixed the DKIM just one or two days after their mistake.

    On the other hand I could take a protonmail subscription and use a domain that has so much volume and is tracked so carefully in term of reputation that I know my mails will be received and have all the necessary security done right.

    These reputation systems are inherently difficult for small volume mail domains. There is no other users ln your domain so one mistake is all it takes to start having delivery issues and most importantly silent failed deliveries that you dont know about.

    Is it possible? Yes. Is it necessary? Not really. If you can pay for a privacy respecting host…

    Hence for me it’s not worth it because there are privacy respecting providers so it’s not like I absolutely have to self host it.


  • I think you choose a poor example.

    When I say long name I wasn’t implying meaningless ones.

    Most business with a lot of machines uses long names where everything as a logical meaning.

    [Site][service][Rack][User selected 8 chars name]

    I mean you dont have to use such obtuse names. But if you have a lot of servers you have to have a long name or you will risk exhausting the available names.

    I’m just saying long names dont have to be obtuse or confusing. You can use user selected names as a suffix to a more functional initial prefix. So that people who work this area of the infrastructure can have clear names but at the same time some other sys admin that never worked on it can still know where and who is responsible of the server.

    My initial point is just that the namespace and length of hostnames mostly depends on what you want to do. For a homelab you dont need wide namespace. But for a large business using short names wouldn’t be practical either.










  • Yeah I think it’s just a false alarm.

    I would suggest looking into how sudoers works. I might just be that you asked caddy to do something that required root and forgot to sudo the command ?

    Still double check the timestamp and verify that it was when you tinkered. Use “history” to look for previous commands and maybe the timestamp ?

    The way I see it something (probably caddy) wanted to check a TLS certificate and had to concatenate all the certificate authorities to check if an adequate CA was there. And it failed to access what looks like a local CA that is autosigned ? Still worth checking your CA has adequate / similar permission as the others.


  • I’m not sure why people are trying convince me to change my mind on something.

    I have seen it in my logs with my own eyes. I wish I could be left alone without having to bother looking into it.

    Whatever the reason is. Someone is crawling through dictionaries of address. It is slow but steady. It started with abuse@ and other generic addresses and then started trying names. I blocked the sending SMTP server once I realized what was going-on.

    What am I suppose to do? Ignore it and just triage in inbox?



  • Does it?

    Do you think spammer will just stop at the first address and then call it a day?

    In my experience there is no such thing as a “catch all” domain address. The second your domain leaks then many spammer will just go into a frenzy and try hundreds or thousands of mail aliases.

    Especially since they can’t really spam Gmail as easily (since early 2024) they will even more aggressively spam any other domain.