
GPGController forces --armor or --no-armor argument
Reported by C Fraire | February 29th, 2012 @ 07:26 PM
The released version of GPGServices allows using gpg.conf to control whether encrypted files are armored, but the development version of GPGController forces a command-line switch.
GPGController should only force an "--armor" switch. Otherwise, no argument should be added, and gpg.conf default will again be respected.
Comments and changes to this ticket
-
Mento February 29th, 2012 @ 07:38 PM
- State changed from new to invalid
This behavior is intended.
If GPGServices should respect the conf, you need to read the conf and set the value in GPGController.
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 your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป