Is WCF Username Authentication without Transport Security a security risk? -


I am trying to use username protection in WCF. I am trying to figure out whether the transport None of the Credential Type / Anonymous will create a certain security risk.

My concern is with the initial exchange where binary data is created using the WS-Trust specification (TLS negotiation)

Any ideas are welcome.

Thank you.

 

  & lt; Security mode = "message" & gt; & Lt; Transport Customer Credential Type = "None" /> & Lt; Message Customer Credential Type = "User Name" Conversation Service Credential = "True" AlgorithmSite = "Default" Install SecurityContact = "True" /> & Lt; / Safety & gt; According to the specs for security of the WS-username, the user name in the token can be both.  

And passwords, unencrypted. It will be obvious that this information will be clearly transferred to unencrypted wire. Binary formatting is not preventive, usually referred to as "security by ambiguity" and security measures are not at all.

Coincidentally, while reading an article by Scott Hanselman I had received a lot of information, it indicates issues you are having

If you enable this feature If you intend, you definitely want to enable some transport-level security here.

Here are the Oasis documents on WS-Security UsernameToken. It appears to allow many scenarios, but I'm not sure what WCF uses by default:

If you are curious, you want to enable message logging And want to inspect the message to see what is being sent.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -