On Fri, Jan 02, 2004 at 12:26:10AM +0200, Antti-Juhani Kaijanaho wrote:
Hi,
(...)
My plan of action is to add support for file names that are passed to
/bin/sh as commands, whose standard output stream becomes the default
input. Now, since this will involve allowing execution of arbitrary
On Fri, Jan 02, 2004 at 12:47:58AM +, Antony Gelberg wrote:
leftprotoport=17/0
Try with leftprotoport=17/1701. This depends on what version of
Windows you're using.
If there is any more log info that would be useful, please let me know
what to post.
Key loading is working
On 20040102T110521+0100, Javier Fernández-Sanguino Peña wrote:
commands it might be worthwhile to check their permissions and ownership
before making use of them (i.e. ensuring they are not world-writable and
that they belong to the current runing user).
... or to root, obviously.
Yes, I
Strange that the subject Distinguished Name (DN) of your mailhost
certificate seems to be identical to the DN of the CA.
Could you enable debugging by setting
klipsdebug=none
plutodebug=all
in ipsec.conf and then after you tried to start up the connection
generate a barf:
ipsec barf
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Fri, Jan 02, 2004 at 12:47:58AM +, Antony Gelberg wrote:
leftprotoport=17/0
Try with leftprotoport=17/1701. This depends on what version of
Windows you're using.
If there is any more log info that would be useful, please let me know
what to post.
Key loading is working
On 20040102T110521+0100, Javier Fernández-Sanguino Peña wrote:
commands it might be worthwhile to check their permissions and ownership
before making use of them (i.e. ensuring they are not world-writable and
that they belong to the current runing user).
... or to root, obviously.
Yes, I
--
Savio M. Ramos - Arquiteto
Rio de Janeiro ICQ174972645
Não à pirataria! GNU/Linux
Debian-br #705 unstable-SID
http://www.debian.org
Strange that the subject Distinguished Name (DN) of your mailhost
certificate seems to be identical to the DN of the CA.
Could you enable debugging by setting
klipsdebug=none
plutodebug=all
in ipsec.conf and then after you tried to start up the connection
generate a barf:
ipsec barf
Don't pipe to /dev/null just yet -- I've had five false positives since
implementing it this morning!
I can provide procmail log entries (although not the actual emails -- I
/dev/null-ed prematurely) if you'd like. I'm going to leave the filter
in place, but pipe them to a folder instead so
I'd be grateful if someone could please try to deconfuse me about what
the current stable kernel 2.4.18 source package is ..
DSA 403-1 (http://www.debian.org/security/2003/dsa-403) states that
the do_brk security hole was fixed in vanilla kernel 2.4.23, and that
For Debian it has been fixed in
12 matches
Mail list logo
