From: Steve Ankeny <sankeny@netdirect.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Problems with certificates .....
Date: Wed, 01 Sep 2004 13:58:51 +0000 [thread overview]
Message-ID: <4135D59B.10600@netdirect.net> (raw)
I diligently followed the instructions found at ....
http://lartc.org/howto/lartc.ipsec.automatic.keying.html#LARTC.IPSEC.X509
... only to have problems making it work for me.
I am trying to use 'racoon' to make IPSec connections between various
Windows clients and a SuSE 9.1 server.
Apache2, SSL and Racoon are installed correctly, as far as I can tell.
UDP:500 is listening and not blocked by the firewall.
I have no troubles setting up the certificates (with or without a
certificate authority), but I am not sure of where to place them and/or
how to use them with 'racoon.'
The confusion comes from not knowing what to do with the certs once they
are created ... where to point the server, where to copy the certs, etc.
Can anyone point me to a good tutorial on certs? Or, better yet, make
some suggestions about configuring and using 'racoon?'
Kernel 2.6.5-7
ipsec-tools 0.3.3
openssl 0.9.7d
Apache 2.0.49
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2004-09-01 13:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4135D59B.10600@netdirect.net \
--to=sankeny@netdirect.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.