Hi, anyone have thoughts on this:
I might need to run some code on one box but have the user on another box.
but the data is confidentail so it should be encrypted when it goes across the network.
I am wondering -- will remoting give me a way to do that ?
or should I build some kind of crypto functions ?
I know how web services can use ssl etc...
but I have not done remoting and this case is on a local network.
thanks!
I have partly answerd my own question, but still I'd like to hear from others.
remoting with .net 2.0 provides several options to make for a secure channel.
now has anyone here used that ?
looks like the pipe is like this:
app == CSLA == remoting == crypto == network ...... network == crypto == remoting == CSLA
so the CSLA classes do not need to be altered in any way.
just as the data goes out it gets crypted and then the other side reverses and the other csla app gets the data.
looks like the back of the book says a tiny bit on this.
pelinville:
Since IIS is being used to host this, couldn't you just use SSL?
I am working on a small Point Of Sale app.
so most of the time the shop will have 2-5 pc's and no server.
so for this app one pc running xp home or pro will be "in back" and run sql express.
so with a local network and few pc's I am looking to skip use of IIS
most of the data can just use sql connections -
a few things need to be secured like CreditCard numbers.
I am going to put the cc processing on the sql box and the sql data with cc# etc.. will have enctyption
so the last item is for terminal x running a sale to send a packet to the sql box and get an auth to finish the sale.
for example 4 pc's 1 in back with sql express
3 "out front" doing sales.
most of the data is ok in this case to just use sql connections to pass around info
but a few items like CC auth need to be less exposed.
so I am thinking TCP channel remoting for just CC actions.
Copyright (c) Marimer LLC