On Sat, Jan 09, 2010 at 05:37:58PM -0000, Daniel Richard G. wrote:
> I can see where you're coming from, but I think it would be less
> confusing to the user if local certificates were handled just the same
> as system-bundled ones. I wouldn't see it as a good thing if the
> procedure for enabling/disabling a certificate differed depending on
> whether it were locally-installed or not.
>
> That aside, the symlinks in /etc/ssl/certs/ are generated based on the
> multiselect list, so the local certificates aren't getting in there
Untrue.
| # Now process certificate authorities installed by the local system
| # administrator.
| if [ -d "$LOCALCERTSDIR" ]
| then
| find -L "$LOCALCERTSDIR" -type f -name '*.crt' | while read crt
| do
| add "$crt"
| done
| fi
It's handled just like the multiselect list, calling add will add the
symlink.
On Sat, Jan 09, 2010 at 05:37:58PM -0000, Daniel Richard G. wrote:
> I can see where you're coming from, but I think it would be less
> confusing to the user if local certificates were handled just the same
> as system-bundled ones. I wouldn't see it as a good thing if the
> procedure for enabling/disabling a certificate differed depending on
> whether it were locally-installed or not.
>
> That aside, the symlinks in /etc/ssl/certs/ are generated based on the
> multiselect list, so the local certificates aren't getting in there
Untrue.
| # Now process certificate authorities installed by the local system
| # administrator.
| if [ -d "$LOCALCERTSDIR" ]
| then
| find -L "$LOCALCERTSDIR" -type f -name '*.crt' | while read crt
| do
| add "$crt"
| done
| fi
It's handled just like the multiselect list, calling add will add the
symlink.
Kind regards,
Philipp Kern