similar to: opensshd 2.3.0 (oBSD 2.8) ignores ME!

mdb-bsd is a FreeBSD 4.2-STABLE box morpheus is a Red Hat Linux 6.2 box with openssl 0.9.6 on it. Attempts to use SSHv2 fail. Using SSHv1 succeeds. sshd from OpenSSH2.5.1p1 is getting a fatal: xfree: NULL pointer given as argument Full client and server interaction given below. -- Mark Script started on Mon Feb 19 10:47:01 2001 1:mdb at mdb-bsd$ ssh -v -v -v -2 -x morpheus date SSH Version

I set up winbind on one box successfully. Now a friend told me that it might be better to use ActiveDirectoriy (the PDC and all other servers are win2000). What is the difference in both approaches? which is 'better'? I feel that ldap is the more general and cleaner solution. Is that true? My windows-admins will get rid of wins soon. does winbind rely on wins? can libnss-ldap also create

Running "ls" on a large directory (/usr/bin) locks the term when using protocol 2.0. A tilde works to escape the session. Client: OpenSSH_2.9p2 on NetBSD Server: OpenSSH_2.3.0 on FreeBSD Output of ssh -v <FreeBSD host>: OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Seeding random number generator debug1: Rhosts Authentication disabled, originating port will

This is my system info: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.60-1-pve (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh

I have two samba servers (version 2.2.2-2, debian sid) with identical configuration. One stands in the server room and is part of the server subnet. the other is in the normal 'user' subnet. I added both server (several times!) to the win2000 domain. the procedure was identical. Both have secret.tbs files of 8192 bytes opposite to the 6xx bytes which they have when they are not joined to

I have two samba machines, one has the problem I describe in the earlier mail. The other works much better and also there I have the (same) smb.conf: egrep '^[^;]' /etc/samba/smb.conf [global] printing = cups printcap name = /etc/printcap load printers = yes guest account = nobody invalid users = root security = domain workgroup = TRITECH server string = %h

I use the samba-2.2.2-2 debian package and try to set up authentification via winbind. I have use this smb.conf: egrep '^[^;]' /etc/samba/smb.conf [global] printing = cups printcap name = /etc/printcap load printers = yes guest account = nobody invalid users = root security = domain workgroup = TRITECH server string = %h server (Samba %v) syslog only = no

I do get problems with name resolution accross subnet bounderies. I have a working and wins server and to demonstrate the problem I paste the debug output of mount /smbhome/ opts: uid=1000 opts: gid=1000 mount.smbfs started (version 2.2.2debian-2) added interface ip=192.168.6.2 bcast=192.168.6.255 nmask=255.255.255.0 resolve_lmhosts: Attempting lmhosts lookup for name Tri-st-s001<0x20>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:12 Security Advisory FreeBSD, Inc. Topic: OpenSSH buffer management error Category: core, ports Module: openssh, ports_openssh,

someone recommended that i should give br0 the same hardware address as eno2. I did that, and restarted the vm, and it still does not work. Here is my current host interface config: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:12 Security Advisory FreeBSD, Inc. Topic: OpenSSH buffer management error Category: core, ports Module: openssh, ports_openssh,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:12 Security Advisory FreeBSD, Inc. Topic: OpenSSH buffer management error Category: core, ports Module: openssh, ports_openssh,

Is it possible? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Dear all, is it possible to specify the default paths in the appropriate configuration of the Daemon ? If not, wouldn't it make sense to include that feature as the configuration files get parsed anyway ? What do you mean ? Kind regards, Lukas -- Lukas Ruf Swiss Federal Institute of Technology Office: ETZ-G61.2 Computer Engineering

I've had the wrong sshd daemon killed by "killing using alternate method" too many times. Would this cause anyone any grief? --- opensshd.in.old Sun Oct 21 16:42:02 2001 +++ opensshd.in Mon Jul 15 19:34:16 2002 @@ -3,11 +3,8 @@ # # Stripped PRNGd out of it for the time being. -AWK=/usr/bin/awk CAT=/usr/bin/cat KILL=/usr/bin/kill -PS=/usr/bin/ps -XARGS=/usr/bin/xargs

Hello, I have been playing with valgrind + openssh-3.5p1 as distributed in Red Hat 9. In the report, I get this: ==1059== Invalid read of size 4 ==1059== at 0x40170B7D: vgAllRoadsLeadToRome_select (vg_intercept.c:612) ==1059== by 0x40170DF2: __select (vg_intercept.c:681) ==1059== by 0x804E4C6: (within /usr/sbin/sshd) ==1059== by 0x403DC5CC: __libc_start_main (in /lib/libc-2.3.2.so)

I have just installed openssh on my Sun Cobalt Qube, running Linux. The shell interpreter for the rc script forces /sbin/sh. This is defined in opensshd.init.in. This shell does not exist on this implementation of Linux. I have written about this in (much more) detail at http://blogs.sun.com/roller/page/DaveLevy/20060104. NB This would seem to me to be a common problem but I havn't found

Hi. I''ve got here the following configuration: (turn on fixed pitch font to be able to see the scheme in a more accurately way) Client machines <-----> ADSL Router 1 <-----> INTERNET (192.168.0.0/24) (192.168.0.229) NAT Client machines <-----> ADSL Router 1 <-----> INTERNET (192.168.1.0/24) (192.168.1.229) NAT [if doesn''t really

We've been having trouble with OpenSSH 2.9p2, running on Solaris 8 (a domain of an E10k), with PAM authentication turned on. It intermittently crashes with signal 11 (seg fault) after the password is entered, after the MOTD is displayed, but before control is passed over to the login shell. I eventually managed to persuade sshd's child process to consistently crash, upon entry of an

I began with Samba 1.9.18.p10. on SunOs 5.6. I try backup PC(Windows95) with this: smbclient \\\\pcbig\\test .. .. smb:\> recurse smb:\> directory recursion is now on smb:\> tar c /dev/rmt/0 .... Until it is OK. But restore has error: smb:\> tar x /dev/rmt/0 smb:\> restore tar file \test1.txt of size 70 bytes smb:\> Updating creation date on \testfolder1\ smb:\> ERRDOS - 50