Example:
[CertificateCreationWizard] CN_placeholder=Common Name CN_prefill=false EMAIL_placeholder=name@example.com EMAIL_prefill=false NAME_placeholder=Firstname Lastname NAME_prefill=false
Example:
[CertificateCreationWizard] CN_placeholder=Common Name CN_prefill=false EMAIL_placeholder=name@example.com EMAIL_prefill=false NAME_placeholder=Firstname Lastname NAME_prefill=false
I guess this is solved. Feel free to re-open and schedule for 2.2.34
Might be a TOR Thing?
FWIW: We need a DCO; see doc/HACKING.
No, too much release work. Better just one AppImage. Or well one VSD (based on 2.2) and one regular (based on 2.3)
I have decided to use two different sets of settings for the placeholders and for controlling the prefilling of the values. Overloading the semantics of a specified placeholder text would have confused users and developers alike.