This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ncc-services-wg@ripe.net/
[ncc-services-wg] FW: [ncc-announce] New RIPE NCC PGP Key
- Previous message (by thread): [ncc-services-wg] FW: [ncc-announce] New RIPE NCC PGP Key
- Next message (by thread): [ncc-services-wg] 2007-01 Policy Implementation - Phase Two Deadline Extended
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber, UniVie/ACOnet
Woeber at CC.UniVie.ac.at
Fri Dec 18 15:21:50 CET 2009
Thor Kottelin wrote: >>-----Original Message----- >>From: Wilfried Woeber, UniVie/ACOnet >>[mailto:Woeber at CC.UniVie.ac.at] >>Sent: Friday, December 18, 2009 3:23 PM >>To: Thor Kottelin >>Cc: ncc-services-wg at ripe.net > > >>Thor Kottelin wrote: > > >>>the steps are basically: download the key, check its >> >>authenticity, >> >>>sign it using your copy of PGP >> >>And that is not necessary (or even useful) in order "to just verify >>the email..." > > > If you trust the key, you should sign it. Until you have signed the key, PGP considers it invalid, and rightfully warns you should you try to verify a message signed with such a key. OK, then PGP and GnuPG obviously do behave differently. Sorry for the confusion! > Please see e.g. <URL:http://www.mccune.cc/PGPpage2.htm#Bad-Invalid> in "Tom McCune's PGP Questions & Answers". Wilfried.
- Previous message (by thread): [ncc-services-wg] FW: [ncc-announce] New RIPE NCC PGP Key
- Next message (by thread): [ncc-services-wg] 2007-01 Policy Implementation - Phase Two Deadline Extended
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]