3 ms·
That implementation has been already reviewed by the UK years ago. The referenced document is about "stepping up of cross-border cooperation, particularly in co
by viraptor 6y ago
That implementation has been already reviewed by the UK years ago. The referenced document is about "stepping up of cross-border cooperation, particularly in combating terrorism and
cross-border crime" which goes down to details like XML format of the exchanged data and which parts of DNA are used to identify people across Europe. It's not something that UK can change on its own and definitely not something that should give anyone a pause before accepting the document as was already implemented - just because an old browser is listed in examples.
It can easily be debated as "do we have any issues with the technical details of the international exchange of forensic information or should we continue with what we have right now?"
- ben_w 6y agoIt also says to hash with SHA-1 and encrypt with 1024 bit RSA, which is more concerning and less amusing than Netscape Communicator.
- thu2111 6y agoEU law is full of stuff like this. There's no philosophical conception that law should be minimal or regulation a last resort, so they pass huge laws all the time that specify precise details of things and which get very out of date. A good example is to compare US law on digital signatures Vs EU law. The latter mandates PKIX and the former just says words to the effect of any digital equivalent of a signature. So you can imagine which is simpler and more flexible.
- realityking 6y agoSince this regulation is not a standard to be used by the public but how governments of various countries interact, I don’t see the problem. Imagine they had only specified “must be encrypted”. Now France is going with S/MIME with SHA1 but the UK with SHA-256. The French system didn’t anticipate this and the can’t decrypt it. Meanwhile Germany is using PGP and nobody can read anything. Long way to say: strong specs improve interoperability.
- viraptor 6y ago> former just says words to the effect of any digital equivalent of a signature The US has FIPS enforced at federal level. FIPS tells you not only what ciphers are allowed, but also how you're going to compile your SSL libraries and in which environment. It's typically way behind practical recommendations in real world. Tell me again how it's more simple and flexible?