You have both hit it "right on the head".
IMHO, HTTPS is a lie.
And I don't feel that Michael should waste his time trying to implement
a "lie" into Arachne.
(just my opinion)
On Sun, 09 Jan 2000 18:40:35 -0800, Clarence Verge wrote:
> Samuel W. Heywood wrote:
>> I do not understand how I could encrypt my credit card number, transmit
>> the encrypted number, and then have the recipient to decrypt the number
>> unless the recipient had a compatible decryption engine and had
>> knowledge of the original encryption key (i.e the password or pass
>> phrase that I use to encrypt the data). It would seem that somehow
>> this kind of thing is what would have to happen when using a "secure"
>> web site. How does this kind of "magic" work?
> Hi Sam;
> I don't know of a site that will provide the details you are looking for,
> and, the following is just my own bumble so don't take it as fact.
> Surely the simplest method would require that the recipient involved sends
> you the encryption key and then you send the encrypted data.
> How this prevents someone eavesdropping on the transaction from decrypting
> your data is unclear to me because it seems he/she can end up with all the
> necessary information.
> Like I said. My bumble.
> - Clarence Verge
> --
> - Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
> --
--
Glenn McCorkle mailto:[EMAIL PROTECTED]
North Jackson, Ohio, USA
Arachne, The Web Browser for DOS
Open the 'DOOR' to the WWW. Keep the 'windows' closed.
http://home.arachne.cz/ or http://arachne.browser.org/
