Re:iOS 18 breaks IMAPS self-signed certs
by stackskipton on Thursday September 19, 2024 @12:07AM
(#41588404)
.local also hasn't been best practice since 2005. Current recommendation, because of Certificates is to use internal only subdomain of domain you have control over.
Re:iOS 18 breaks IMAPS self-signed certs
by lxgr on Thursday September 19, 2024 @08:26AM
(#41591100)
What? .local is the dedicated TLD for Zeroconf/Bonjour/mDNS! How is that deprecated?
And you’re just reconfirming my point: All of these recommendations are great for publicly hosted sites or corporate environments, but largely impracticable for home users that don’t know how to, or don’t want to, have a second job as sysadmins.
Re:iOS 18 breaks IMAPS self-signed certs
by stackskipton on Thursday September 19, 2024 @10:09AM
(#41592044)
Home users also don't have IMAP servers they run themselves. They are in public email service.
Re:iOS 18 breaks IMAPS self-signed certs
by lxgr on Thursday September 19, 2024 @11:55AM
(#41593170)
I don't think it's crazy for a NAS to provide an IMAP server, e.g. to backup or archive a large mailbox.
One of the selling points of a NAS is that storage is much cheaper than what the large cloud providers charge per GB and month.
Re:iOS 18 breaks IMAPS self-signed certs
by stackskipton on Thursday September 19, 2024 @12:11PM
(#41593360)
Cool, you don't but obviously you don't deal with a ton of normal users. They are not running NASes, they will just toss Google some cash for bigger GMail box.
Right now, .local is completely impossible to encrypt, as well as impossible to use “secure origin” APIs on, which is a shame.