View Complete Post
I'm trying to create a .NET client that will consume AXIS WS.
Request should be signed (using x509 Signature) and after this usernametoken profile 1.0 should be attached.
Using SOAP-UI I can create Outgoing Security Policy with few steps described below:
1) Define keystore
2) Add WSS Signature entry and mark key identifier type as X509 Certificate or Binary Security Token
3) Add WSS Username entry
The order is important.
I cannot recreate SOAP request that would generate valid response.
I got "The signature or decryption was invalid" most of the time.
Here is valid SOAP Request from SOAP-UI:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:user="http://users.api.swd.zbp.pl"
This month Paul DiLascia teaches readers the right way to create dynamic dialogs, explains satellite DLLs and discusses language resource DLLs.
MSDN Magazine September 2006
MSDN Magazine July 2003
MSDN Magazine August 2002
Edited by Nancy Michell
MSDN Magazine August 2001
.net DLLs are not secure, this is such a disappointment.
What can one do to secure DLL apart from obfucation (which is nothing about making DLL secure)
I know that I can build a DLL in vb6 or Delphi (thats secure) and then COM (tlbimp.exe) it for .net using interlop tools for .net
BUT I dont want to that, I want to stay with .net (vb) , so can anything be done to truely secure a .net DLL ??
This is very important
MSVS 2005 ASP.net 2.0 vb.net 2