Displaying 8 results from an estimated 8 matches for "wtnet".
Did you mean:
wnet
1999 Nov 22
1
tcp-wrappers not being used even w/ --with-tcp-wrappers
...figure.in. No luck so far.
I'll continue poking at the source to try to solve it, but in the
meantime, if someone comes up with the solution, please post it to
the list.
Thanks,
--
===============================================================================
csaia at wtower.com, WTnet IRC Administrator - http://www.wtower.com/~csaia/
GNU Privacy Guard Public Key information is available at the above URL.
===============================================================================
1999 Nov 23
0
status of Solaris build
...e seen packages that have included a "bsdinstall" command. That
may be necessary here.
Now, the adventure will be in RUNNING the daemon to see what happens. :)
Tally ho,
--
===============================================================================
csaia at wtower.com, WTnet IRC Administrator - http://www.wtower.com/~csaia/
GNU Privacy Guard Public Key information is available at the above URL.
===============================================================================
1999 Nov 23
1
[PATCH] AIX 4.3.2 compile fixes
Hi all.
It's nice to see that AIX support (unintentionally?) is getting better and
better. :)
Attached is a patch against pre14 that fixes AIX support. All that is left,
basically, is a replacement for the /dev/urandom way of getting entropy.
...
A completely different thing... how about DCE support? I was thinking of
adding some dce code to sshd that:
1. Attaches credentials based on
1999 Nov 25
0
suse/kde and the new ssh-add/ssh-askpass
...ll probably update the spec file and post it in my web tree so
that others can grab the file without waiting for a new prerelease.
See http://www.wtower.com/~csaia/openssh.spec.
Cheers,
--
===============================================================================
csaia at wtower.com, WTnet IRC Administrator - http://www.wtower.com/~csaia/
GNU Privacy Guard Public Key information is available at the above URL.
===============================================================================
1999 Dec 01
1
[Fwd: Serious Bug Report: OpenSSH]
Can anyone using PAM and rsa-rhosts authentication replicate this?
Damien
-------------- next part --------------
An embedded message was scrubbed...
From: Adrian Baugh <adrian at merlin.keble.ox.ac.uk>
Subject: Serious Bug Report: OpenSSH
Date: Wed, 1 Dec 1999 02:38:56 +0000 (GMT)
Size: 3926
Url:
1999 Dec 04
0
updated SuSE spec file
...a new host key if one already exists and we
aren't going to make one?) I've also marked manual pages as %doc.
Damien, I'll be sending you up the whole spec file intact as well.
--
===============================================================================
csaia at wtower.com, WTnet IRC Administrator - http://www.wtower.com/~csaia/
GNU Privacy Guard Public Key information is available at the above URL.
===============================================================================
-------------- next part --------------
A non-text attachment was scrubbed...
Name: file
Typ...
1999 Dec 09
2
OpenSSH-1.12pre17: PATCH: Red Hat PAM limits
With the sshd in recent releases of OpenSSH, some Red Hat Linux systems
complain about ulimit trying to raise a limit when logging in via ssh.
The problem is that packages/redhat/sshd.pam doesn't do limit checking
for an sshd session.
The attached patch adds the pam_limits module to the sshd session,
which checks for limits set in /etc/security/limits.conf.
This works on Red Hat Linux 5.2
1999 Dec 04
2
confusion over RSAref vul w/OpenSS[HL]
...ulous)
software patent, which expires in 10 months. However, I figure I
best pursue a legitimate [legal] solution first.
What's the deal?
Best,
"Burned in Boston"
--
===============================================================================
csaia at wtower.com, WTnet IRC Administrator - http://www.wtower.com/~csaia/
GNU Privacy Guard Public Key information is available at the above URL.
===============================================================================