<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: RE: newbie in trouble with pkcipe on linux
From: "Mark Smith" <mark.smith,AT,avcosystems,DOT,co,DOT,uk>
Date: Thu, 12 Sep 2002 13:20:51 +0200
In-reply-to: <Pine.GSO.4.44.0209121405240.20707-100000@cs.uku.fi>

The .info  file distributed with cipe details the pkcipe config file.  All
of the options go in one file.  Here's mine, as an example:

--- snip ---
-----BEGIN PUBLIC KEY-----
<your public key from the other end's public key file>
-----END PUBLIC KEY-----
ipaddr 10.0.0.12
ptpaddr 192.168.0.1
ping 10
dynip
--- end ---

--
Mark Smith - Avco Systems Ltd
email: mark.smith,AT,avcosystems,DOT,co,DOT,uk
Tel: +44 (0)1784 430996 Fax: +44 (0)1784 431078

> -----Original Message-----
> From: Mikko Pasanen [mailto:miapasan,AT,cs,DOT,uku,DOT,fi
> Sent: 12 September 2002 12:09
> To: Mark Smith
> Cc: Cipe list (E-mail)
> Subject: RE: newbie in trouble with pkcipe on linux
>
>
>
>       so is it like /etc/cipe/pk/hostName includes the hosts
> public key,
> and /etc/cipe/pk/options.hostName would be the options file
> specific for
> the host. The thing is that everything seemst to start
> running correctly
> but the data doesn't transfer, but with plain ciped-cb it
> runs perfectly.
> i run the pkcipe as pkcipe -E -c host:port, and it tells me
> that it starts
> the ciped.
>
> On Thu, 12 Sep 2002, Mark Smith wrote:
>
>
> > The config files for pkcipe are stored in
> /etc/cipe/pk/<host> - the file you
> > mention is the default daemon options;  pkcipe uses a
> template you specify
> > to create a dynamic daemon options file, so that it can
> handle address
> > translation and secret key generation automatically - all
> you have to do is
> > connect the two pkcipe processes together.
> >
> > --
> > Mark Smith - Avco Systems Ltd
> > email: mark.smith,AT,avcosystems,DOT,co,DOT,uk
> > Tel: +44 (0)1784 430996 Fax: +44 (0)1784 431078
> >
> >
>
>





<< | Thread Index | >> ]    [ << | Date Index | >> ]