covert-encryption

(originally posted on the Covert issue but moving here) It may need a few more than 25 lines of code in C but not much space at all because you...

As a background, our application uses existing keypairs of other software, in particular those generated by [Age Encryption](https://github.com/FiloSottile/age), which only exist in Curve25519 format. Also, for implementation it is much...

@FiloSottile Sorry for assuming that stdin was used for passwords. GPG apparently is doing that, but not Age. Special handling of armored format (and restricting it to relatively short data...

re: edited issue title: I have to emphasise that the full input should be read in any case, even when public keys are used, to avoid the security issue mentioned...

GPG does not suffer of this because it always reads until EOF. That is one way to do it, but less good UX especially for people who don't know how...

The BIP 39 wordlist has a lot of prefix words, leading to confusion when passwords are created without separators, e.g. `uselessoncereal` which can mean either **useless-once-real** or **use-lesson-cereal**, all words...

@str4d I am well aware of that, but tab completion is also a nice thing to have especially with 10-word passphrases. Four easily memorable words, autocomplete, no wordbreaks and strong...

Leaving this open for review and comments in case anyone wishes to have a word on it. In particular it should be noted that this violates the XEdDSA specification which...

Actually the flag from that function is visibility (not validity), indicating whether a random-generated password was made (and also whether the user had password input visible otherwise), allowing the password...

Passwords definitely should be refactored into a class type, where additional information such as the string shown in UI may be more easily included, and which could then be further...