Question - Is it possible to still use CryptoJS? about staticrypt HOT 4 CLOSED

Nevermind... Probably just my computer being weird...

from staticrypt.

Nope, I was right... Version 2, the CryptoJS-based version, is completely broken.

Functionality is extremely inconsistent (it worked once or twice, but not the rest of the time)

When I attempt to encrypt something using version two, either the login page doesn't load at all (showing only a loading circle and a page title of "/[|template_title|]/0", or if it does load, then the decrypt button does nothing except trigger an empty alert().

P.S. Whatever happened to the "embed cryptoJS" option? Maybe I'm just crazy or I did something weird, but it disappeared from my web server copy...

from staticrypt.

Yet another update: curiously, all those issues seem to be derived from one thing: renaming the folder staticrypt v2 is contained in.

Also, sorry for the irrelevance - you've moved on from v2 :)

from staticrypt.

Hey @AwesomeCaden73 , thanks for reporting!

So were all those issues fixed by the folder renaming? If so I don't really have a lead on why, except I assume some weird cache somewhere...

I do want to keep supporting v2 since it's the only way to use HTTP, so feel free to open issues regarding that version if you find any bugs. Also in your case: if you're viewing the files locally browsers usually consider file:// to be a secure context, so WebCrypto should work on local files as well.

from staticrypt.