search for: brettnach

...packets suggests that my X clients aren't even > trying to send a cookie, despite the fact that the XAUTHORITY > variable is correctly set. Ssh 2.0.13 used to work just fine... I am having the same problem on FreeBSD. I haven't got any clue, unfortunately. -- Dominik - http://www.brettnacher.org/users/dominik/

On Wed, 2 Feb 2000, Harald at iki.fi wrote: > How come I can't get scp to work properly. It just complains like this: > > scp foo host: > bash: scp: command not found > lost connection Maybe you should check for the path on the remote machine: it seems like the remote shell can't find scp in its $PATH. -- Dominik - http://www.saargate.de/~domi/

Hi there, there is a problem (which as far as i know) is already known with rsync on FreeBSD: it is not possible to rsync neither fifos nor unix domain sockets (note that you have to be root there): # mkfifo test # file test test: fifo (named pipe) # rsync -a test test2 mknod test2 : Invalid argument rsync error: some files could not be transferred (code 23) at main.c(620) # file /var/run/log

...not found in libc. Fix for old Solaris from Andre Lucas <andre.lucas at dial.pipex.com> - Check for libwrap if --with-tcp-wrappers option specified. Suggestion Mate Wierdl <mw at moni.msci.memphis.edu> 20000303 - Added "make host-key" target, Suggestion from Dominik Brettnacher <domi at saargate.de> - Don't permanently fail on bind() if getaddrinfo has more choices left for us. Needed to work around messy IPv6 on Linux. Patch from Arkadiusz Miskiewicz <misiek at pld.org.pl> - DEC Unix compile fix from David Del Piero <David.DelPiero at qed.q...

Hi all, I am trying to get OpenSSH working on an i386 BSD 3.1 box we have. Everything compiles OK, installs, and I can launch SSHD. Here is a sample session of sshd with the debug switch: <BEGIN SSHD OUTPUT, NAMES CHANGED TO PROTECT THE INNOCENT :)> computer# /usr/local/sbin/sshd -d debug: sshd version OpenSSH-1.2.3 debug: Bind to port 22 on 0.0.0.0. Server listening on 0.0.0.0 port 22.

Hello, I have the following problem: I have installed openssh-1.2.2 on FreeBSD 3.4-RELEASE. I intentionally did not took the FreeBSD port because it does not support PAM. My aim is to make sshd authenticate against a TACACS+ server using the pam_tacplus.so module shipped with FreeBSD. That works perfectly with this line in my /etc/pam.conf: login auth sufficient pam_tacplus.so

Hi there, I already asked the list about the problems with sockets on FreeBSD (see here: http://www.mail-archive.com/rsync@lists.samba.org/msg08121.html). I adopted Andrew Flury's patch to the recent CVS version of rsync: Index: rsync.h =================================================================== RCS file: /cvsroot/rsync/rsync.h,v retrieving revision 1.155 diff -r1.155 rsync.h