You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Alon <al...@cisco.com> on 2012/12/02 14:16:37 UTC

Replacing the server and client sockets in ActiveMQ

Hi,

I'd like to replace the sockets in Active MQ 5.7 (server and clients) to be
FIPS compliant (using NSS-JSS sockets)

For the server (broker) sockets i override the createSslTransportServer
method of SslBrokerService and use my own SslTransportFactory. 

For the client side i registered my SslTransportFactory by using 
TransportFactory.registerTransportFactory("ssl",new
MYSslTransportFactory());

All seems to be working fine. ActiveMQ Brokers and listeners use the NSS-JSS
sockets successfully.
Is this the right approach for replacing the SSL sockets in ActiveMQ?

Thanks,
Alon





--
View this message in context: http://activemq.2283324.n4.nabble.com/Replacing-the-server-and-client-sockets-in-ActiveMQ-tp4660069.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: Replacing the server and client sockets in ActiveMQ

Posted by Dejan Bosanac <de...@nighttale.net>.
Hi Alon,

I never worked with FIPS, but according to this

http://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/FIPS.html

you should be able to use regular sockets and configure the JVM to be
FIPS compliant.

Regards
--
Dejan Bosanac
----------------------
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosanac@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/


On Sun, Dec 2, 2012 at 2:16 PM, Alon <al...@cisco.com> wrote:
> NSS-JSS