[ripe-list] RIPE NCC PGP-Key expired

Hi Dominic and all,

We are no longer PGP-signing our support emails, although we still
accept PGP-authenticated updates to the RIPE Database.

When we conducted our assessment, we weren't able to find a ticketing
system that met our requirements and supported PGP. As the service was
being used by a relatively small number of members, we decided that the
benefits of the new ticketing system outweighed the PGP-signing service.

It is also worth noting that the RIPE NCC public key was never meant for
encrypted communication. It was only used for signing emails.

However, we didn't notify members that we would not be PGP-signing our
emails any more. This was an oversight on our part, and we would like to
apologise for this.

Kind regards,

Andrew de la Haye
Chief Operations Officer
RIPE NCC

On 01/03/2018 13:20, Dominic Schallert wrote:
> Dear colleagues,
> 
> we noticed that the PGP-Key for ncc at ripe.net <mailto:ncc at ripe.net> (Key
> ID: C6839AEF) has expired
> on the 2nd of February 2018. As of writing, no new public keys have been
> published 
> over at https://www.ripe.net/manage-ips-and-asns/contact/ripe-ncc-pgp-keys 
> 
> Looking ahead to the rollout of the EU GDPR in May 2018, it might be
> beneficial to 
> allow for PGP-encrypted communication between LIRs and RIPE NCC, besides
> the existing PGP-based database authentication mechanism.
> 
> Kind Regards
> Dominic Schallert
> 
> 
> *schallert​.com e.U.* | Hauptstraße 35b, 6800 Feldkirch, Austria
>  
> FN: 440372g  | UID: ATU66209211 | Gerichtsstand: Feldkirch
>  
> Tel.: +43 680 146 1947 | Fax: +43 134 242 642 616
> 
> www.schallert.com <http://www.schallert.com>  | office at schallert.com
> <mailto:office at schallert.com>
> 
> 
> 
> 
> 
>