You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.
Just ran a few tests with IE10 on Windows7 and IE8 on WinXP... no good.
E.g. generating a key pair just doesn't work at all, neither does sending an encrypted message. Some other operations do work, but are very very slow.
This can all be traced back to openpgpjs, looks like IE support either isn't quite there yet or not really feasible.
I guess we should at least mention this in the documentation / FAQ, and maybe even do a browser check in the plugin to warn users?
Perhaps #99, #101 and #116 are related to this.
The text was updated successfully, but these errors were encountered:
#101 is Firefox 21, so it should be irrelevant. Waiting for response on #116, most likely outdated browser.
Browser detection, hm, meh... We could debate that it's a feature that it fails silently. Personally I think it's a bit of a paradox that security oriented software supports outdated software, especially in terms of Internet Explorer 10 on Windows XP, which are both unsupported by the vendor(!) for years.
Personally I think it's a bit of a paradox that security oriented software supports outdated software
I fully agree and I don't see much of a need for the plugin to support such software. But I think we should inform the user as to why encryption, key pair generation etc. is not available to him/her: simply because of the browser and not because of user error, server problems, a bug in the plugin or what have you.
Hi all,
Just ran a few tests with IE10 on Windows7 and IE8 on WinXP... no good.
E.g. generating a key pair just doesn't work at all, neither does sending an encrypted message. Some other operations do work, but are very very slow.
This can all be traced back to openpgpjs, looks like IE support either isn't quite there yet or not really feasible.
I guess we should at least mention this in the documentation / FAQ, and maybe even do a browser check in the plugin to warn users?
Perhaps #99, #101 and #116 are related to this.
The text was updated successfully, but these errors were encountered: