[db-wg] Re: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es
-
To: Brian Riddle brian@localhost
-
From: Gert Doering gert@localhost
-
Date: Wed, 20 Dec 2006 11:46:45 +0100
-
Cc: Gert Doering gert@localhost, "ncc-services-wg@localhost" ncc-services-wg@localhost, "db-wg@localhost" db-wg@localhost
-
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
-
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=testkey; d=space.net; b=aOF1CXuYFYJtUSgO+tLC0Qy+egUjQmK7+wg1NfQLk+BPU/c61iy493OebDSJPn3g ;
Hi,
On Wed, Dec 20, 2006 at 11:42:07AM +0100, Brian Riddle wrote:
> We did see a problem with "Communigate Pro" open SSL/TLS compatibility,
> simple fix upgrade to latest version/patch. Otherwise no problems.
That's very good news.
Thanks!
Gert Doering
-- NetMaster
--
Total number of prefixes smaller than registry allocations: 98999
SpaceNet AG Mail: netmaster@localhost
Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0
D- 80807 Muenchen Fax : +49-89-32356-234
Attachment:
pgpdXIpic4cdg.pgp
Description: PGP signature
|
you are here: RIPE -> RIPE Maillists > Archives
