Certbot came with a systemd timer running twice a day (0, 12 +12h random) that only renews –iirc– when the certificate has 30 days or less to live. Also I looked it up and my (version 6.7) Certbot neither mentions the option with the --help option, nor in the manual (where there is just one instance of “profiles exist, no other details given”).

So they probably need another way than a random blog post when they want users to use (or even just know about) that option…

It’s been pretty much a set-and-forget experience

Yeah, that’s what it always has been. So no need to change anything unless they make it the new standard on their side with an update…

So exactly like an AGI emerging after just one more update.

You mean they are reaching geo-synchronous orbit after already skyrocketing this year?

Wait… IT isn’t informations technology?

Not OP, but it’s two-way TLS. It’s not only your server providing a certificate to prove it’s the real thing and not just some men-in-the-middle device or your connection for redirected, but the other side of the connection using a certificate, too, to show they are actually the devices allowed to communicate.

So this basically reverts the security. You are no longer trying to filter out access attempts when they show questionable behavior, but completely reject anything unless it’s explicitly authorized. Which of course only works when you or (a small number you can manually manage of) others access that stuff from fixed devices that you can set up properly.

PS: For me fail2ban does basically something similiar. I have several web interfaces exposed via reverse proxy. But I barely ever use those interfaces manually; normally it’s via apps that access the services via that web interface. So things like failed authentifications or misstyped passwords don’t happen (unless when setting up something new maybe and then I’m there to unban a device manually if I screwed up). So fail2ban is set up to aggressively bans IPs for hours just for a single failed attempt.

That’s keeping all those spammy bots looking for easy targets away very effectively, yet completely invisible for my legitimate use. After all that’s always the core issue: security vs. convenience. You build the best possible security that also doesn’t overly interfere with your normal use. Also the reason there is no on-size-fits-all solution because it’s about your use-case.

it will bring value to […] the community.

I’m inclined to find this more believable than similiar statements of all the usual AI suspects.

In my case it was Syncthing and Radicale that replaced basically all my Nextcloud use.

Nextcloud isn’t bad actually but you really need to use a lot of the million optional features to justify that behemoth.

https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing

That’s the probably most unhelpful and stupid thing I saw in quite some time. The AI or Not Quiz right at the beginning in particular regularly links the exact same things to human or to AI (404 links are a sign or AI hallucination or just natural link decay that show it’s from a human; wonky grammar is a sign for AI unless the text is human-written where it’s just bad english that LLMs would not produce intentionally…).

Yes, spotting AI by clear attributes isn’t easy. If it was those points would be changed first in training of AI. But lengthily discussing tell–tale signs then interpreting them in contrary ways depending on source is absolute bullshit.

Not surprising given that they are also produced by people who don’t do consent.

Nobody is saying “Linux is obscure”

How about scrolling up to the exact comment I anwered to? Or -as you seem to be on the exceptional dense side- let me do it for you…

Linux’s “security through obscurity” was never going to last.

As already explained above I did not expect that statement to use the common “long-standing industry term” because -again- it would be utterly insane to claim security through obscurity for something open source.

Just google the term

Yes, please do.

The actual notion of “security through obscurity” (that will surely come up on Google if their AI bullshittery hasn’t screwed up completely…) for Linux is insane because open source is the polar opposite. By that definition proprietary code is actually much more linked to the concept.

The often more unprecise and colloquial usage I thus assumed you were using doesn’t apply either, for the reasons I summarised.

So which imaginary definition of “security through obscurity” are you using and assuming that it will come up on Google when none of the real ones makes any sense?

You are right. I don’t know what your personal definition of “security through obscurity” is as it’s very obviously not matching actual reality.

There was never an actual notion of “security through obscurity”. LInux runs the complete Internet and most coporate server infrastructure. That’s where the actual money is.

People hallucinating that Linux is something obscure simply have no clue and confused their home desktop for real computing. Windows desktops are constantly targeted not because they are -unlike Linux- so wide-spread but because they are already insanely insecure. They are the low hanging fruit where you can cobble together some cheap shit and will still find million of PCs vulnerable. If you want to find a Linux comparison it’s definitely not server or desktops but cheap IoT devices not having seen an update (or any security to speak of) for many years.

For reference: We are talking about guests in a virtual pc escaping it’s container. That’s not something obcure. That’s basically all cloud hoster’s whole business model, thus the reason Google pays a lot of money for finding such exploits.

Petitions are useless

Protests are useless

Governments and corporations conspire to implement surveilance knowing what comes next

<-- we are here

Actual resistence

the agent is a tool you used

My hammer is also a tool. But if I start using (and talking about) it to wash my cloth and do my dishes I would really hope to get called out for being stupid.

I’m using the default calendar app that a long time ago came with that lineageos install.

Should be this one iirc…

Don’t host the calendar, just host some WebDAV/CalDAV. That format is supported by basically all apps on every platform (usually including the default app on most phones), so everyone can pick what they want (or just stick with what they already use).

My personal pick for that purpose is Radicale.

A mandatory [AI] tag? Sure.

A [NOT AI] tag? No, that’s the default. Why normalise AI bullshit even further?

While you are right in general, you are just creating a file with a <user>:<hashed password> line without any identifying context. So have fun searching the world for where I might have actually used it. Sounds like a really bad use of ressources to create list of passwords.

PS: Yes, as an Arch user I am still pissed that this tool is not available in the repos beside installing the complete Apache server…

The options to password protect it are in the (usually /etc/radicale/)config file under [auth].

For proper security you could use

type = htpasswd

htpasswd_filename = /etc/radicale/users

htpasswd_encryption = bcrypt

then create a users file with apache tools (htpasswd -c -B users User1) or one of the million online htpasswd file creators.