From: Jesper Harder <harder@myrealbox.com>
Subject: pgg security problem
Date: Thu, 24 Jul 2003 04:45:55 +0200 [thread overview]
Message-ID: <m31xwgy74s.fsf@defun.localdomain> (raw)
There's a security advisory for Semi:
<http://www.debian.org/security/2003/dsa-339>
this includes some of the pgg-files we're using.
I fixed this back in April, but then reverted the change, because it
didn't work wit gpg (a missing --yes flag it appears).
Anyway, I reapplied the change. Please check if the pgg stuff works.
It's probably also a good idea if someone knowledgeable about security
stuff took a look.
reply other threads:[~2003-07-24 2:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31xwgy74s.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).