DOMtegrity VS Ed25519Tool

Source code is provided here: https://github.com/toreini/DOMtegrity

For browsers this problem is partially solved as subresources may be integrity checked. Further, there have been proposals like DOMTegrity, that provides a complete solution. For now, yes, full integrity checking isn't done automatically in browser, but it may be done automatically using git or manually as is normally done for any software downloaded not using a package manager or git.

I'm concerned about the `#` character in the URL.

# means fragment and that's kept local and not sent to the server unless client side Javascript sends it to the server. I would use an identifier that doesn't already mean something to the URL.

See https://github.com/Cyphrme/URLFormJS#query-parameters-fragme... (Also see https://github.com/Cyphrme/Path)

For an example where this is relevant: https://cyphr.me/ed25519_tool/ed.html#?msg_encoding=Text&msg...

And see https://www.rfc-editor.org/rfc/rfc3986#section-3.5

For browsers this problem is partially solved as subresources may be integrity checked. Further, there have been proposals like DOMTegrity, that provides a complete solution. For now, yes, full integrity checking isn't done automatically in browser, but it may be done automatically using git or manually as is normally done for any software downloaded not using a package manager or git.

The only reason the evil tool is now the second result is because this backdoor angered me so much I created the (now) #1 tool, that runs in browser, never sends off keys, and is fully open source. Feel free to click on that one all you want and star it on Github. Just practicing, "cypherpunks write code". 😉

git clone https://github.com/Cyphrme/ed25519_applet.git