similar to: Failed password

Hi, I must have missed something; it seems that all messages sent to the ssh list get forwarded to the openssh list. Thx Mate -- --- Mate Wierdl | Dept. of Math. Sciences | University of Memphis

On my solaris 2.6 box, I get ssh moni ld.so.1: ssh: fatal: libz.so: open failed: No such file or directory Killed while as root, I have no problem. Note that echo $LD_LIBRARY_PATH /space/local/lib:/usr/local/lib:/usr/openwin/lib:/usr/lib:/opt/x11r5/lib ls -l /space/local/lib/libz.* -rwxr-xr-x 1 wierdlm faculty 70488 Mar 10 17:26 /space/local/lib/libz.a -rwxr-xr-x 1 bin bin

OK, It works if I modify my make.conf to not build openss[lh] like it : #MAKE_KERBEROS5= yes # TEST NO_OPENSSH= true # do not build OpenSSH NO_OPENSSL= true # do not build OpenSSL (implies NO_OPENSSH) Maybe I install openss[hl] as ports after... But I'm not satisfied with this way... -- G?rard MILHAUD ?cole Sup?rieure d'Ing?nieurs de Luminy (ESIL) Luminy - Case 925 -

After upgrading to xen unstable packages I'm seeing the following problem: skx@itchy:~$ sudo /etc/init.d/xend restart Restarting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-3.0-unstable-1/bin/xend", line 40, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17,

Howdy, I am trying to setup a 10gR2 RAC on top of some nbd devices. OS is Centos4.1/i386, (2.6.9-11.0.0.10.3.EL, ocfs2-2.6.9-11.0.0.10.3.EL-1.0.4-1). ocfs2 setup went perfectly well, btw. (besides the fact that ocfs2console apparently ignores nbd disks) mount says /dev/nbd1 on /opt/oradata/data1 type ocfs2 (rw,_netdev) on both nodes ls says (after runInstaller was started, so the files were

On the box moni, I have rpm -q openssh openssh-1.2.1pre25-1us on the box karadi, I have rpm -q openssh openssh-1.2.3pre2-2 On moni, I do/get: scp "wierdlm at karadi:11Lecture/lecture.tex" . wierdlm at karadi.msci.memphis.edu's password: bash: scp: command not found What can be wrong? Do I have to specify the remote path to scp? (It is in $PATH for wierdlm at

Hi. I have a samba server with 3000 users. I want to install another little server with a printer and I want to give access only to a group of users from the main server. [ MAIN ] [SAMBA-SERVER] | | | [little]-printer a group of users from MAIN can print [server] to this server Someone can give me a hint of how can I achieve this easily ? What document should I read ?

Hi, I'm running windows 98 on my workstation and there're couple of unix boxes around, they're BSDI, SOLARIS which are all configured to run SAMBA. One strange thing is that everytime I try to get into my unix home dir under win98 workstation, I will be asked for a password, but no matter what password I put in, I won't be allow to go in. That didn't happen before under

Hello, Kenny Cho wrote: >I've been successful using v,1.9.18a but not 2.0.4b, I believe it's because I >ended up downloading the binaries that doesn't have the shadow password support. >So my other question is how do I know if the smb binaries that I download has >that support? This may come across more bitter than I intend it to be. So please take this with a grain

First, when I tried to start sshd, I got the message Starting sshd: ssh-keygen: no RSA support in libssl and libcrypto. See ssl(8). sshd: no RSA support in libssl and libcrypto -- exiting. See ssl(8) no RSA support in libssl and libcrypto -- exiting. See ssl(8) So I thought I have to recompile openssl with rsaref flag to config. When I did that, I got compilation error (this is version 0.9.5

We recently upgraded to openss 5.8p2 from a somewhat older version. This broke openssh login to ScreenOS devices. These devices don't support PTY allocation. Apparently, ssh now reacts to PTY allocation failure by failing the login. This is a change from the previous behavior. The simple workaround is ssh -T $device. I see in the ChangeLog that some device would hang with PTY allocation

Is it true that configure tests for the existence of librsaref.a, and if it finds it, it assumes that that rsaref is supposed to be used---*even if openssl was not built with rsaref support* ? Mate

Hello! I know that this is not samba related, but may be some one knows a quick answer: When using profiles, stored on a well running samba-2.0.0beta2 PDC, the NT PC's cache the profile during a user session. As this profile is not deleted on the PC and we have a lot of users with only few PC's we need a lot of diskspace for this old profiles. Is there a way (Registry Key, ..) that

I've been working on a package for openssh to include in the NetBSD package system (similar to the FreeBSD ports system). I'm being hindered in this by the fact that updates to these packages can be extremely slow (2-3 days minimum, more like 2 weeks including testing), too slow to compensate for the fact that the tarfiles for back-level versions of openssh-1.2pre* are going away. Given

Howdy, I'm installing openssh 2.2.0p1 on a number of SUNs running Solaris 2.6 but ran into a few problems: 1. whenever I run a remote X11 application and f.i. change the windowsize I get anoying debug messages like debug: client_check_window_change: changed This is a problem since I want to use openssh in a production environment. Is there any way to turn these messages off?

On Oct 11, 2008, at 11:06 AM, OvermindDL1 wrote: > I should apologize. I have been trying to keep from attacking the > current process that llvm uses for testing (although I do still agree > that the current testing framework is more for testing llvm-gcc and > not llvm), but I have not quite been so successful. Ideas and feedback are useful. However, one systematic problem that

I got itchy fingers over the weekend and decided to fix what wasn't broken and upgraded one of the older servers from Centos 5.2 to Centos 5.3. Following the recommended process of updating glibc and such before the rest, it appeared to work perfectly and rebooted without problem. However, MRTG 2.15.2 started complaining about unexpected values. I installed/updated both MRTG (2.16.2) and

On Sat, Oct 11, 2008 at 12:28 PM, Chris Lattner <clattner at apple.com> wrote: > Ideas and feedback are useful. However, one systematic problem that > the LLVM community has is that most of the regular contributors are on > unix systems. As you probably know, much open source software works > by having people 'scratch their itch'. You (and many other people on >

I've got a problem that I'm hoping the list can help with, otherwise ... Heres the problem, I've got OpenSSH 1.2.2p1 running on my Intel Linux box as the secure server. I can connect from another Intel Linux box using scp and it all seems to work fine. Another box tries to connect and it gets a warning about the host keysize not matching. I'm thinking this could be some byte

These are all in the port of 1.2.3pre2: - configure accepts --includedir, but doesn't seem to pass it on to the Makefile. You have to edit the Makefile manually if you have include files anywhere but /usr/include. Which is a problem because... - The Makefile doesn't include /usr/local/include by default, which is where zlib installs itself by default. Probably oughta be in there.