On 11/25/2003 1:02 AM [EMAIL PROTECTED] noted that:
Ross,
I honestly believe you will reward us all with a very satisfactory
solution to the issues being expressed.
I also wish to appologize for anything I have said that might suggest I
believe otherwise.
Nothing you said led me to believe oth
Ross,
I honestly believe you will reward us all with a very
satisfactory solution to the issues being expressed.
I also wish to appologize for anything I have said that
might suggest I believe otherwise. Fact is I have
experianced more than my far share of offensive off list
flames and my com
On 11/24/2003 2:56 PM L.C. (Laurentiu C. Badea) noted that:
It seems to me (I might be wrong) that the OpenSRS engineers have
spent a good deal of effort to create parallel versions of the
XML-RPC and SSL protocols.
Yes - back when we did this the very first time around we needed to work
around
because we all are in this together to improve
OpenSRS.
John Roche
einfosystems.net
Microsoft Certified Partner
-Original Message-
From: L.C. (Laurentiu C. Badea)
[mailto:[EMAIL PROTECTED]
Sent: Monday, November 24, 2003 2:57 PM
To:
Subject: RE: ASP.NET DEVELOPRS encryption question
It seems to me we've been through this SSL encryption discussion on more
than one occasion already.
I would recommend searching the discussion archives rather than dredging it
all up again.
-t
My read is that HTTPS is handled via trivial (took me 15
to 30 minutes to hack and successfuly "script" the OpenSRS
RWI and code runs on Win 98+) Windows OS calls and HTTPS
is also handled in a similarly transparent manor on other
platforms as well. So, while the client is still burdened,
long
We've been mentioning this only since 2001. Quoting myself:
http://www.opensrs.org/archives/dev-list/0112/0035.html
It seems to me (I might be wrong) that the OpenSRS engineers have
spent a good deal of effort to create parallel versions of the
XML-RPC and SSL protocols. [...] the connection prea
Obviously the client has to encrypt and decrypt the data at some point -
I said the client CODE does not need to do any encryption - it is done
in the transport layer by libraries, dlls, dotnet framework classes,
etc. that we don't have to write.
For instance in vb.net:
Example
Dim myRequest As W
> If communications are encrypted using SSL, that eliminates the need to
> do any encryption in the client code.
Does it? Or does it mean the client has to do the SSL encryption?
SSL does not imply that it is an http transaction.
> John Roche
> einfosystems.net
>
>
> >>Has anyone brought up t
If communications are encrypted using SSL, that eliminates the need to
do any encryption in the client code.
John Roche
einfosystems.net
>>Has anyone brought up the possiblity of using SSL to do the encryption
instead of using blowfish?
This mail was content checked for malicious code and
Hi ASP people.
Has anyone brought up the possiblity of using SSL to do the encryption
instead of using blowfish?
It SHOULD be easy to have the perl client set up the connection in SSL.
The question is would you be able to do the client side encryption in ASP
(or in other languages...)
11 matches
Mail list logo
