Newsgroups : Borland : borland.public.delphi.internet.winsock : 2007 Jan : Re: Wrapping Inet to get HTTPS support with Indy?

www.cryer.info
Managed Newsgroup Archive

Re: Wrapping Inet to get HTTPS support with Indy?

Subject:Re: Wrapping Inet to get HTTPS support with Indy?
Posted by:"dk_sz" (dk_..@hotmail.com)
Date:Mon, 5 Feb 2007 05:57:47

> requirements.  That's why Windows ships with 40bit encryption rather
> than 128bit and the 128bit High Encryption pack was made available to US

That was how it was for Win2K as well.
(i.e. a separate disk if I recall correctly)
However, WinXP / DK had 128 builtin I believe.


> different.  In Europe, there is the "The Wassenaar Agreement".  In the
> US, the ITAR - If you are in the US (but a non-US citizen) you are still
> subject to the ITAR.  Check your laws carefully.

Thanks for the information / keywords.


> Scary stuff whenever you decide to export an application that includes
> high level encryption, eh?  That's one of the reasons I pretty much

But by using the OS / WinInet you are not exporting any
code at all. You use the same routines the OS supplies to IE.
You just select and pass a https instead of http in parameters.
If above is illegal, so is using TWebBrowser it would seem? :-)


best regards
Thomas Schulz

Replies:

none

In response to:

www.cryer.info
Managed Newsgroup Archive