[
https://issues.apache.org/activemq/browse/AMQNET-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58208#action_58208
]
Andreas Ländle commented on AMQNET-239:
---------------------------------------
Sorry, i was pretty unclear. As Markus assumed i was talking about the
Implementation of SSL-support for the Compact Framework.
Unfortunately I'm not able to share the patch I've used to accomplish this
goal. Don't get me wrong, I'm not selfish and I don't want to slave-drive the
Apache.NMS project - it's just licensing issues.
In spite of all that i want to outline what we have done.
- Build bouncycastle (use the latest source code version from CVS - the
released version 1.6.1 doesn't build for target netcf-2.0)
- Derive a SslStream class from the compact framework stream Stream class -
SslStream is acting as a 'proxy' to the encrypted in-/out-streams provided by
the bouncycastle library (be aware of the async calls!). Implement SslStream
similar to the CLI Implementation of Stream
(http://www.123aspx.com/rotor/RotorSrc.aspx?rot=42052).
- Add the initialization of the SSL-Stream to the SslTransport class. Create a
NetworkStream around your socket. Use the bouncycastle TlsProtocolHandler to
encrypt the network stream. Use your implementation of SslStream to wrap the
Input-/OutputStream of the TlsProtocolHandler.
No offense.
> Add support for SSL to NMS/Stomp
> --------------------------------
>
> Key: AMQNET-239
> URL: https://issues.apache.org/activemq/browse/AMQNET-239
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ, NMS, Stomp
> Affects Versions: 1.2.0
> Reporter: Andreas Ländle
> Assignee: Timothy Bish
> Fix For: 1.3.0
>
>
> As far as i can see there is still no support for SSL in NMS. I guess that
> there is a demand to secure communication between client and broker (e.g. in
> a highly distributed environment where client and broker are connected via
> the public internet).
> So my wish is a possibility to secure my communication between the client and
> the broker using NMS.
> Are there any capabilities i have missed?
> I think the same issue has been disused in august 2008
> (http://old.nabble.com/NMS-ssl-support-td19047073.html)
> Best regards,
> Andreas Ländle
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
