GpgFrontend VS scrypt

- GPGFrontEnd - https://github.com/saturneric/GpgFrontend - Gpg4Win (For Windows users) - https://www.gpg4win.org/download.html - Kleopatra (For Linux users -> Best-suited for KDE users) - available in most distributions' package repositories

If there is enough text space for OpenPGP payloads (they can get quite large), you could secure your privacy by using this tool https://github.com/saturneric/GpgFrontend and copy and paste that into Mastodon chats.

Use this https://github.com/saturneric/GpgFrontend on top of it, then they need a $10 wrench to get the private key. This way you and only you have the private key.

In my experience, I have not seen much luck in automating GPG on the Windows platform. Instead, almost all automation is either done via GPG on Linux. GPGFrontend might be your answer, and it has seen relatively recent updates.

You can use GPG on every platform. On android, there is OpenKeyChain and on Windows you can use something like this. GPG keys can also be used to sign stuff. You can upload them to key-servers and sign files and emails with it.

If you want to digitally sign and/or encrypt messages on such a forum you can use a tool like https://github.com/saturneric/GpgFrontend

Check out the scrypt encryption tool.

Given that the encryption algorithm is open source (https://github.com/Tarsnap/scrypt) can you try to explain what you mean here?

I wouldn't use OpenSSL personally. If you just need simple but secure symmetric encryption, checkout the scrypt(1) encryption utility from Tarsnap. If you need support for public keys, check out age(1).

scrypt if you strictly only need symmetric encryption.

^ "scrypt page on the Tarsnap website". Retrieved 21 January 2014.

First of all I know that "implementing your own cryptography is bad". However, at some point, one does stumble upon a use-case that is not (well) covered by existing tools.

Now, assuming one has already done his due-diligence and has read (and hopefully understood at least the main ideas of) cryptography related articles / posts / etc. (especially in the area pertaining to what one wants to build), and thus we can assume one is not a complete newbie in this mater, however, nor is he an expert. Basically we can assume he is an "amateur".

Where would one go with his design to ask for feedback about it, in the hope to at least eliminate some weaknesses that one (as a non expert) might have overlooked. (I'm not speaking here about "proofs" or "audits".)

----

More specifically ---- but please let's not get into this right now, this being just an example ---- I'm trying to implement something similar to `scrypt` (the encryption utility, that uses the `scrypt` PBKDF, ) or `age` (), as a replacement to my current solution that relies on GnuPG.

It entirely does and that's exactly my point. Most "hashes" are designed to be fast, for data validation/checking whatever. For securing data (passwords, anonymisation, etc) you want a "hash" to be as slow as possible. Scrypt for example is designed to be extremely slow and use much memory (making GPU-based parallelisation useless and driving up the cost of CPU-based work). The default settings for five-second hashes changes their 18 hour estimate to a bit over two years... and that's assuming you don't turn it up further.