2 ms·
Why? XML in S/MIME over SMTP might not be cutting edge, but it's still state-of-the-art. I would be hard pressed to come up with something better that's equally
by wongarsu 6y ago
Why? XML in S/MIME over SMTP might not be cutting edge, but it's still state-of-the-art. I would be hard pressed to come up with something better that's equally based on open, established standards. XML is the only thing I would like to replace, but that's probably not worth it given the number of existing legacy systems
- jmnicolas 6y ago> for the exchange of DNA profile information So you're fine that your DNA information is transmitted in clear in an email?
- matthewmacleod 6y agoIt’s not “in clear” though, is it? It’s encrypted.
- wongarsu 6y agoOf course it's encrypted, the deal reads "The open standard s/MIME as extension to de facto e-mail standard SMTP will be deployed to encrypt messages containing DNA profile information" (highlight mine). Then it goes on with technical details (that could be updated a bit), then the mention that common email software already supports this (including those from the headline, which is how we got this headline). https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/948119/EU-UK_Trade_and_Cooperation_Agreement_24.12.2020.pdf https://assets.publishing.service.gov.uk/government/uploads/... page 921
- Piskvorrr 6y agoExcept...not. HTTP is also cleartext, but it is usually tunelled through TLS. The entire stack matters, not that this one part is insecure when considered in isolation.