Prevent storing configuration settings with newline (\n) characters
Reported by Luke Le | December 5th, 2014 @ 11:11 PM
gpg.conf can't process newline (\n) characters for configuration settings (which makes sense), so if it encounters such a configuration setting it will report an invalid config.
Our tools won't start with an invalid config, since they can't properly read keys or perform other operations.
To avoid this issue, all configuration settings must be sanitized first by removing newline characters before being stored.
Comments and changes to this ticket
-
Support December 5th, 2014 @ 11:17 PM
- State changed from “new” to “fixed”
(from [20ed55cbd60b1f933285f9fd27503f8e577c288b]) [FIX] Sanitize config settings before storing them to avoid breaking gpg.conf [#131 state:fixed]
- gpg.conf can't process config settings with \n characters and reports an invalid config error if it detects these characters since everything after the \n is interpreted as a new config setting.
- To avoid breaking the gpg.conf this way, each setting is sanatized by removing \n characters before being stored in gpg.conf https://github.com/GPGTools/Libmacgpg/commit/20ed55cbd60b1f933285f9...
-
steve December 15th, 2014 @ 04:43 PM
- State changed from “fixed” to “verified”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Alex (via GPGTools)
Luke Le
steve