Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What do people do with security issues when using nServiceBus/msmq? Thinking about for example message encryption, message signing (validation?) etc
How do you know that the message is not sent to the queue from someone else. or that someone has tampered a message.
You can control the permissions of a MSMQ queue, including who (windows user/group) can send to a queue. If you wanted to encrypt the message, with MassTransit at least and likely NServiceBus, you can inject a custom serializer.
In most cases I’m familiar with, the messages are from trusted sources. If you are accepting messages from external sources they would go through some sort of entry point, such as a web service before hitting the queuing system. The controls that are in place within the organization are often enough.
Lastly, the “sender” is exposed in the MSMQ header. I do not know if this is accessible within NServiceBus but as long as you can access it from the MSMQ .NET wrapper I doubt it is out of the question to ask for.