3 ms·
Is there any Korean here that can give a perspective on how the Korean open source community has adapted to the proprietary SEED cipher? Has there ever been att
by mrb 14y ago
Is there any Korean here that can give a perspective on how the Korean open source community has adapted to the proprietary SEED cipher? Has there ever been attempt to implement it in openssl, gnutls, etc, so as to not depend on this ActiveX plugin?
- qxcv 14y ago> Has there ever been attempt to implement it in openssl, gnutls, etc, so as to not depend on this ActiveX plugin? SEED is implemented in NSS (Firefox's network security backend)[0] as of 2010. I'm not sure whether or not that removes the dependency on IE, though. Edit: looks like it's implemented in OpenSSL as well[1]. [0]: https://bugzil.la/453234 https://bugzil.la/453234 [1]: https://www.openssl.org/docs/apps/ciphers.html#SEED_ciphersuites_from_RFC4162_ https://www.openssl.org/docs/apps/ciphers.html#SEED_ciphersu...
- mcpie 14y agoThe dependency on IE is also a result of Korean coders/designers relying on the quirks and bugs and specificities of IE6 for their websites. Even when it comes to non-e-commerce sites, many (most?) sites won't function properly if you don't use IE. This is the end result of the encryption-thing, so getting rid of that would be a proper step forward, but wouldn't solve the problem itself. By now IE it's systemic :[
- gkanai 14y agoSupporting SEED alone in Webkit or Gecko won't work because neither will implement Active-X support, especially because Microsoft itself is deprecating Active-X in future versions of Windows.