GnuPG 2.0.3: gpgconf.conf and allow-mark-trusted

Hello Werner,

I realized that "allow-mark-trusted" is set to
"no-change" hardwired
in the source code. I am aware it is set to
"change" through gpgconf.conf
(if installed correctly).

However, I think GnuPG should not hardwire any such things.
Or are there good reasons to do so?

Next, the default gpgconf.conf should not set anything but
only
keep some examples (like the one for 
"allow-mark-trusted") commented
out.

Then we would have a liberal default and it is subject to
packagers or
sysadmins to define policies.

All the best

	Jan

-- 
Dr. Jan-Oliver Wagner                        Intevation
GmbH, Osnabrück
Amtsgericht Osnabrück, HR B 18998             http://www.intevation.de/
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr.
Jan-Oliver Wagner

_______________________________________________
Gnupg-devel mailing list
Gnupg-develgnupg.org
h
ttp://lists.gnupg.org/mailman/listinfo/gnupg-devel

On Fri, 30 Mar 2007 13:54, jan-oliver.wagnerintevation.de said:

> I realized that "allow-mark-trusted" is set
to "no-change" hardwired
> in the source code. I am aware it is set to
"change" through gpgconf.conf
> (if installed correctly).

I reverted that.  The gpgconf.conf now has a no-change
example.

> Next, the default gpgconf.conf should not set anything
but only
> keep some examples (like the one for 
"allow-mark-trusted") commented
> out.

There is no default ggconf.conf - it is just an example on
what can be done.

> Then we would have a liberal default and it is subject
to packagers or
> sysadmins to define policies.

I don't agree that liberal defaults are a Good Thing. 
However in this
case I reverted it because we should not be more restrictive
than in the
past.


Shalom-Salam,

   Werner


_______________________________________________
Gnupg-devel mailing list
Gnupg-develgnupg.org
h
ttp://lists.gnupg.org/mailman/listinfo/gnupg-devel