On 03/06/2002 14:56:47 dale wrote:
[snip]
wget ftp://user:[EMAIL PROTECTED]/folder1/folder2/*s.csv
I get an error message of no match and if I use:
wget --glob=on ftp://user:[EMAIL PROTECTED]/folder1/folder2/*s.csv
I also get no match
In the future, please post the output with the -d
On 05/06/2002 13:08:05 drt - lists wrote:
Thank for no help.
If this is typical of how you reply to your customers
I do *not* reply to customers. I am a developer, and post here as a private
individual. Perhaps I should unsubscribe altogether.
[snip]
The Mac machine I am using for testing
this message gets added to the mail automatically and I don't have any control over
it.
Hm thats bad so if you see i digital sign all mails, but if they become
manipulated or added text so how should an digital signment work ?
Yes, I was also worried about the fact that if OpenSSL will work
On Wed, 5 Jun 2002, Thomas Lussnig wrote:
And Try if openssl/gnutls handle it on used connection (i think yes, if no
data readable for the moment).
You pass the socket descriptor to OpenSSL. It easy to do that the exact same
way, either after only a connect() or after a connect() with some
You pass the socket descriptor to OpenSSL. It easy to do that the exact same
way, either after only a connect() or after a connect() with some CONNECT
stuff.
Thanx, this is what i already hoped
The proxy communication is not available as an RFC but that is the way SSL
tunneling thru a proxy
On Wed, 5 Jun 2002, Thomas Lussnig wrote:
This is wrong. RFC2616 includes all details needed. The information was
available before too, in various (now deprecated) documents.
Does this mean an proxy connection can not be encrypted via SSL ?
It means that the CONNECT request, its associated
