wget and certificates?

Hi,

Is it possible to have wget download files from a https:// connection that
requires a customer certificate?

Is there any version of wget that can deal with this? I'm trying to
download files from there in batch mode, no matter if wget or anything
else. Any hints are appreciated.

Karl

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.networking Karl Moosberg <(E-Mail Removed)> suggested:
> Hi,

> Is it possible to have wget download files from a https:// connection that
> requires a customer certificate?

Take a look at 'curl', it has AFAIR some options for handling
SSL/certs. Search freshmeat.net/rpmseek.com if you don't have it.

[..]

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBAiizAkPEju3Se5QRApWEAJ9X1YuH33FEUbvZso/28EM+hMLYigCbBxno
StL8+2xZmdiNC57N/DweCBY=
=VxN7
-----END PGP SIGNATURE-----

You might have to compile your wget with SSL (https) support. Do you
have openSSL installed? You would encounter the similar problem, while
using flawed proxy.


--
raqueeb hassan
congo (drc)

Am 24 Jul 2004 10:38:55 -0700 schrieb Raqueeb Hassan:

> You might have to compile your wget with SSL (https) support. Do you
> have openSSL installed? You would encounter the similar problem, while
> using flawed proxy.

That wouldn't help. Problem is not SSL, problem is the certificate that
needs to be authentificated (password) and deposited somewhere first.

Don't see how wget-ssl would do this job here. ssl basically works, this is
not the problem I'm facing.

Karl

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.networking Karl Moosberg <(E-Mail Removed)> suggested:
> Am 24 Jul 2004 10:38:55 -0700 schrieb Raqueeb Hassan:

>> You might have to compile your wget with SSL (https) support. Do you
>> have openSSL installed? You would encounter the similar problem, while
>> using flawed proxy.

> That wouldn't help. Problem is not SSL, problem is the certificate that
> needs to be authentificated (password) and deposited somewhere first.

> Don't see how wget-ssl would do this job here. ssl basically works, this is
> not the problem I'm facing.

The reason I suggested to look into 'curl', not completely sure
about your problem, albeit this might offer a solution, you just
have to test it out.

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBAqhWAkPEju3Se5QRAh/5AJ99+2zXm9W1xFhJKne5dbTAkoGC2ACgsVan
ptHi+6PPA9AD4mDnrxjlejU=
=Oy5L
-----END PGP SIGNATURE-----

Am Sat, 24 Jul 2004 18:20:07 -0000 schrieb Michael Heiming:

> The reason I suggested to look into 'curl', not completely sure
> about your problem, albeit this might offer a solution, you just
> have to test it out.

Yes, I'll try curl next week - thanks for your hint.

I just wanted to point out for Raqueeb, that anonymous https access is not
the same as https using a password encrypted client certificate and that
this cannot be accomplished by wget-ssl.

Karl

Ah, yes.

Thanks for the pointer.


--
raqueeb hassan
congo (drc)

Am Sat, 24 Jul 2004 09:15:32 -0000 schrieb Michael Heiming:

> Take a look at 'curl', it has AFAIR some options for handling
> SSL/certs. Search freshmeat.net/rpmseek.com if you don't have it.

Thanks. It does exactly what I needed. I had to convert the certificate via
SSL first, but now it's running fine!

Karl