similar to: Work around Linux kernel bug provoked by nchan.c (fwd)

Hi, I just finished integrating CryptoCard support in OpenSSH. - Native X9.9 support. Should work with CryptoCard en Secure Computing tokens. This basically gives support for Challenge / Response - Licensed under BSD license I'll put the patch on http://www.jdimedia.nl/igmar/pam, but that wil shorty change to projects.jdimedia.nl. If desired I could also put in on the mail. Let me

Hi, Patch that makes CryptoCard word natively with OpenSSH is on http://www.jdimedia.nl/igmar/openssh Damien, please forward this to any list you thing is relevant. Regards, Igmar Palsenberg JDI Media Solutions -- Igmar Palsenberg JDI Media Solutions Jansplaats 11 6811 GB Arnhem The Netherlands mailto: i.palsenberg at jdimedia.nl

Hi, I usually stay away from issues like this, basically because I'm not a lawyer (and don't want to be one), and I don't have a real interest in these issues. Quoting Tatu : > We also have a trademark pending on the Secure Shell mark This seriously undermines the IETF standard draft. It's the same as registering 'milk' as a trademark. Both Secure and Shell are

Some reactions on the thread : Integrating SmartCard in PAM is no problem. Problem I'm facing with for example CryptoCard and SecureID tokens is that those manufacturers refuse to give out any form of information about the internal operation of those tokens. That prevents me from implementing event synchronous mode. The best way to handle this with SSH is probably the way for example Apache

Hi, OpenSSH doesn't comply to the PAM spec, and always assume that a password is asked. This prevents for example pam-cryptocard from operating. I'll post a patch this week to make things work.... (and will also change the pam-cryptocard name. It's to confusing :) Regards, Igmar -- -- Igmar Palsenberg JDI Media Solutions Jansplaats 11 6811 GB Arnhem The Netherlands

Hi, I've got a system with a 3com 590 NIC (Boomerang / Vortex), and instructed it to boot using PXE. System load the initrd and the kernel image from the FTP server, boots the image and starts the install routine. So far so good. The strange part is that after the PXE boot completes the kernel doesn't detec the NIC. It's not a driver issue, the same kernel on a floppy does

Hi, I had a contractor write a patch to allow CryptoCard support in OpenSSH. It works with portable openssh-2.1.1p4, and it was posted to the SSH mailing lists, but I see that it hasn't been included in the openssh-2.2.0p1 release. Would it be possible to include this patch in the official release? The reason why I ask is because it will not be difficult to do that, it will support the

The Linux implementation of TCP sockets has a bug which causes shutdown(sock, SHUT_RD) to fail spuriously (ENOTCONN) if the write side of the socket has already been shut down. If you are using SSH port forwarding to tunnel HTTP through a firewall, nchan.c will tickle this bug once for every HTTP exchange. You will therefore get lots of useless, annoying error messages: channel 2:

https://bugs.freedesktop.org/show_bug.cgi?id=108043 Bug ID: 108043 Summary: Nouveau reports timeout on MX150 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau at

Attached is the patch I've been using to fix the error message seen in the subject line. It seems (!) to have caused no problems with the previous openssh snapshot version openssh-SNAP-20001016, 2.3.0p1 and the latest snapshot (openssh-SNAP-20001114). The patch adds 3 lines to nchan.c in a switch stmt (line 100). It simply caters for the cases where the input channel state is

I have just tarred up a snapshot and uploaded it to: http://www.mindrot.org/misc/openssh/openssh-SNAP-20000823.tar.gz The snapshot incorporates the last month's fixes and enhancements from the openssh-unix-dev mailing list and from the OpenBSD developers. In particular: - ssh-agent and ssh-add now handle DSA keys. NB. this does not interop with ssh.com's ssh-agent. (Markus Friedl)

Hello , I have bought a cryptocard and i want to make it work openssh, now I need to initialize my token, install the cryptocard patch ( http://projects.jdimedia.nl/files/openssh-cryptocard.patch). The patch reads it's data from a file I've heard that some users made a conversion script from the CryptoADMIN server export to a crypto users file that the patch want. Is there anybody who can

This problem is with R 1.7.0 (as released) on Linux and Solaris. Details below are from Linux, Mandrake 9.1. The problem also happened with R 1.6.2 and on Mandrake 9.0. Vignettes often (for me) provokes problems with the misleading error message: * creating vignettes ... ERROR Error in sub(pattern, replacement, x, ignore.case, extended) : invalid argument Error in buildVignettes(dir =

I have been using OpenSSH for a while, and I would like to thank you for the great package. Here is a report of mysterious warning message lines, I get while I use OpenSSH. They don't seem to be serious, but annoying nevertheless. version: openssh-1.2.1pre27 OS Linux standard 2.2.14 #18 SMP Thu Jan 6 06:07:45 JST 2000 i586 unknown (compiled with gcc 2.95.2) Compiler gcc -v Reading

Hi, I've just installed libao-1.1.0 on a new Debian install. I also have alsa 1.0.27.1 installed. Debian is running under VirtualBox 4.2.12 under OSX 10.6.8, on a MacBookPro. libao does not work in stereo for the sampling rate of 44100, but it does for 8000, 11025, 22050and 48000. When I send it two channel output at a sampling rate of 44100, the result includes what sounds like skips,

I am running OpenSSH 2.9p1 on SunOS 5.7 w/4-24-2001 patch cluster. Like many other users I am seeing the hanging session on logout with background processes. This is a huge problem for me as I centrally manage 50+ machines with rdist across ssh. Instead of just complaining about the problem I thought I would put my CS degree to use and try to track down the problem myself. For starters,

The command "ssh ls -l /doesnotexist" gives various responses: Running from a 200 MHz PentiumPro with dsa key added to ssh-agent: Mistakes worst to fast machine: To a faster 600 MHz dual processor i686 600 MHz machine: ls: /doesnotexist: No such file or directory -- correct nothing at all -- wrong ls: select: Bad file descriptor -- wrong

The 4.6p1 sshd is logging this error during remote commands or file transfers: error: channel 0: chan_read_failed for istate 3 Platform is Solaris 8, 4.6p1 + OpenSSL 0.9.8d. The commands and transfers work correctly, so the error message appears to be spurious. The error message does not appear when processing logins. Otherwise 4.6p1 is running without any apparent problems. This error

In the changelog, there is an entry: 20001129 - (djm) Back out all the serverloop.c hacks. sshd will now hang again if there are background children with open fds. Does this mean that this is regarded as expected (and correct) behavior, that should not change in the future, or does it mean that this behavior is a known problem that someone will eventually fix? --Adam -- Adam McKenna

http://bugzilla.mindrot.org/show_bug.cgi?id=1306 Summary: Spurious : "chan_read_failed for istate 3" errors from sshd Product: Portable OpenSSH Version: 4.6p1 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: