3 ms·
Company regulations require all communication to be encrypted, but they don't specify the protocol to use, so TLS 1.1 is fine but no TLS is banned. I'm not mak
by pilif 9y ago
Company regulations require all communication to be encrypted, but they don't specify the protocol to use, so TLS 1.1 is fine but no TLS is banned.
I'm not making this up.
- madez 9y agoThen the regulations need to have a mechanism to be updated in the case of new knowledge. If the regulations have no process to be updated then that is a more fundamental problem to solve. After all, Debian is set to give the process of change 2 years. That is plenty of time for updating the regulation and processes.
- majewsky 9y ago> 2 years Also, you can stay on oldstable for a while if you absolutely cannot upgrade.
- user5994461 9y agoActually PCI DSS does. Funny enough, it tried to deprecate old TLS versions already but it was so widely used that they had to move back the date. https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls https://blog.pcisecuritystandards.org/migrating-from-ssl-and... https://support.cloudflare.com/hc/en-us/articles/205043158-PCI-3-1-and-TLS-1-2 https://support.cloudflare.com/hc/en-us/articles/205043158-P...
- michaelt 9y agoAny joker can start a company and declare any regulation they like. I could require that all software be written in COBOL by moustachioed developers standing on one foot. If I did that, I think Debian would not change their software to meet my bizarre "company regulations"