Search:   Namespaces Discussions .NET v1.1 Feedback

encrypt before serializing Messages   Related Types This message was discovered on microsoft.public.dotnet.framework.remoting. Post a new message to this list... Hazzard I have some xml tokens that need to be serialized before sending off to a client. The token class inherits from MarsalByRefObject. I need to encrypt the tokens also. That should be done first before utilizing any of the serialization mechanisms. Right? thx -g p.s. I think the answer is obvious but i can't quite picture the transformation from xml string to encrypted string to serialized, I guess binary format. Reply to this message...        Lord2702 Thu. Sep. 02, 2004 12:25 PM PT You can use both Binary and SOAP serialization, since you are encrypting it first, before sending it to the other AppDomain, hence both shld work. But make sure, if you have private fields in your object, the you have to have use Binary format. Good Luck. "Hazzard" <Click here to reveal e-mail address> wrote in message news:Click here to reveal e-mail address... [Original message clipped] Reply to this message...        Ken Kolda The SOAP formatter will also emit private fields. It is the XmlFormatter (from System.Xml) which will not (and this formatter is not an option for ..NET remoting). Ken "Lord2702" <Click here to reveal e-mail address> wrote in message news:%Click here to reveal e-mail address... [Original message clipped] Reply to this message...        Lord2702 Ken, Thanks for more info. "Ken Kolda" <Click here to reveal e-mail address> wrote in message news:Click here to reveal e-mail address... [Original message clipped] Reply to this message...        Ken Kolda You have two choices here: 1) Encrypt your data at the point of serialization/deserialization. To do this, just implement ISerializable and the encrypt the data before adding it to the SerializationInfo object. Also, decrypt it once you read it out. 2) Create an encryption sink for your communications. This will allow ALL of your trasmissions between client and server to be encrypted. This is much more complex, but provides much more complete security. Alternatively, you could buy a product which already supports this, such as Genuine Channels (www.genuinechannels.com). Ken "Hazzard" <Click here to reveal e-mail address> wrote in message news:Click here to reveal e-mail address... [Original message clipped] Reply to this message...     System.AppDomain System.Runtime.Serialization.ISerializable System.Runtime.Serialization.SerializationInfo Ad MBR BootFX Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd. Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com