[ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es

Hi Tom,

We will support TLS-level negotiation as described in RFC3207. In our
case any MTA with TLS support based on OpenSSL 0.9.6 - 0.9.8 should work
without any problem.

Regards,
Brian.

tp wrote:
> Have you documented any more about the technicalities, such as which
> version.release(s) you support, level negotiation, what ciphersuites ....
> 
> Tom Petch
> 
> 
> ----- Original Message -----
> From: "Brian Riddle" <brian at ripe.net>
> To: <ncc-services-wg at ripe.net>; <db-wg at ripe.net>
> Sent: Wednesday, December 20, 2006 10:39 AM
> Subject: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es
> 
> 
>> [Apologies for duplicate e-mails]
>>
>> Dear Colleagues,
>>
>> After our successful implementation testing of Transport Layer Security
>> (TLS) over the last few months, we will be implementing TLS on our
>> external mail exchanges (MXs).
>>
>> We will upgrade our mail server software on 8 January 2007, followed by
>> implementation of TLS on 10 January 2007.
>>
>> If you experience problems with mail delivery to the RIPE NCC after the
>> implementation, please send a e-mail to ops at ripe.net. To do this,
>> however, you might have to disable TLS on your MX server or send the
>> email from a MX server that does not have TLS enabled.
>>
>>
>> Regards,
>>
>> Brian Riddle
>> IT Manager
>> RIPE NCC
>>
> 

-- 
Brian Riddle                            RIPE Network Coordination Center
IT Manager                              Singel 258 Amsterdam NL
http://www.ripe.net                     +31 20 535 4444