C# client support for SSL

[Boris Mazniker <bm...@yahoo.com>]

Hi, 

I'm wondering if C# client for Active MQ supports SSL. If it doesn't, are
there any plans on adding the support in the near future?

Thanks,
Boris.
-- 
View this message in context: http://www.nabble.com/C--client-support-for-SSL-tp14308272s2354p14308272.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: C# client support for SSL

[Nathan Mittler <na...@gmail.com>]

On a side note, we've got SSL on our todo list for C++ as well :).  If  
you're thinking about putting SSL into C#, it might help work together  
to nail down the basic user interface.  Some of our thoughts on how it  
should work from the user perspective were captured here:

http://issues.apache.org/activemq/browse/AMQCPP-140

Regards,
Nate


On Dec 13, 2007, at 6:27 AM, ewhauser wrote:

>
> Boris,
>
> I was taking a look at this yesterday, and it does not look like the  
> C#
> client supports SSL.  If you only need to support SSL communications  
> and
> want to patch the client, I think it would not be too difficult to  
> alter
> TcpTransport to use System.Net.Security.SslStream when writing data  
> to the
> socket.
>
> I believe to completely implement the feature, you would have to  
> change it
> so that NMS understood "ssl://" in the connection string and you  
> would have
> to create an SslTransport (that used most of the functionality in
> TcpTransport).  I had not gotten this far yet, but was investigating.
>
> I am not sure if there are any SSL compatible issues to worry about  
> between
> .NET and Java.  I would not thing so, but...
>
>
>
>
> -- 
> View this message in context: http://www.nabble.com/C--client-support-for-SSL-tp14308272s2354p14316878.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: C# client support for SSL

[ewhauser <ew...@gmail.com>]

Boris,

I was taking a look at this yesterday, and it does not look like the C#
client supports SSL.  If you only need to support SSL communications and
want to patch the client, I think it would not be too difficult to alter
TcpTransport to use System.Net.Security.SslStream when writing data to the
socket.

I believe to completely implement the feature, you would have to change it
so that NMS understood "ssl://" in the connection string and you would have
to create an SslTransport (that used most of the functionality in
TcpTransport).  I had not gotten this far yet, but was investigating.

I am not sure if there are any SSL compatible issues to worry about between
.NET and Java.  I would not thing so, but...




-- 
View this message in context: http://www.nabble.com/C--client-support-for-SSL-tp14308272s2354p14316878.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.