similar to: big packets?

Hi Alexander, Not sure if this of any help, but we had a similar problem with runaway SMBDs and what seemed to be oplocks. We are running RH6.2 with 0.7.26 ACLs. After much messing around and hassling Jeremy, I eventually changed the kernel from 2.2.19 to 2.2.20 and recompiled everything from scratch. Since then we have not had one of these rogue processes. I think Jeremy was right when he

Secure FTP through SecureFX 1.8B3: issues (Using OpenSSH 2.1.1p2) I downloaded the latest SecureFX because it now claims support for OpenSSH. I'm like cool, now I'll finally be able to secure my ftp on my gateway. First off, I really like the new configure. Everything went ok, I could ssh into the box just fine. Unfortunately ftp didn't work work through SecureFX. I would get

Jeff Van Dyke's "Public Key Assistant subsystem" was previously discussed here: (end of a short thread) http://marc.theaimsgroup.com/?l=openssh-unix-dev&m=103436908422003&w=2 I do see a few comments that seem to point out his arrogance and some disgust about OpenBSD's RCSID, but has anybody found it to be unsecure or if it was bug ridden. The subject sorta dies right

Howdy, I'm sorry if this is a FAQ but I couldn't reach the openssh.com website so I can't check. Is it possible to use F-Secure SSH FTP 4.1 (client) with the openssh2.2.0p1 server? In the documentation I read that sftp is still on the todo list but "SecureFX (secure ftp)" is supported. Apparently this means there are different ways to do ftp with ssh? In that case which

Hi all, Jeremy, after trying to add kernel oplocks = no I got the same errors as describes in my last post. (samba working, but some folders not accessible, even not from commandline unix, can't kill smbd processes......) This is what happens in the log file: any ideas ? [2001/11/29 16:13:00, 1] smbd/service.c:make_connection(610) pc08ust (10.21.1.8) connect to service exchangejg99 as

Hi, I do tech support for Van Dyke Technologies, and I've run into an interesting problem with the sftp-server under some redhat linux boxes. Two separate customers reported that they were having problems using sftp with SecureFX and OpenSSH. Upon further investigation, the sshd_config file on the redhat box had an incorrect path for the sftp-server in it. The problem is that if the path

Below is a patch against the current OpenBSD OpenSSH CVS to workaround a behavior I have observed when converting from SSH 1.2.27 to OpenSSH while using the same old RSA1 host key for protocol 1. In several cases I saw that old SSH sshd reported a host key size of 1024 bits when OpenSSH saw it as 1023 bits. Without the patch, when OpenSSH's ssh client connects to an old SSH sshd it warns

https://bugzilla.mindrot.org/show_bug.cgi?id=3664 Bug ID: 3664 Summary: sftp Product: Portable OpenSSH Version: 9.4p1 Hardware: amd64 OS: Mac OS X Status: NEW Severity: minor Priority: P5 Component: scp Assignee: unassigned-bugs at mindrot.org Reporter: rossmck at

Hello all, I have made SecurID authentication for OpenSSH 3.6.1p2. This patch was totaly rewritten, so please test it before use. Kbd-int authentication is now integrated into challenge response auth. Privsep is now fully suported. PS: What do you think of selective access to the individual authentications, similar to AllowGroups/DenyGroups or maybe AllowUsers/DenyUsers ? Vaclav Tomec

I have a FTP server behind my firewall. Thanks to Tom it works. Next I would like protect the username and password. With out a firewall. I would just create a SSH user on the firewall and connect. I think the easiest way is to do this is to forward port 22 to my ftp server. Is there a way to have the firewall handle the ssh session and forward the rest of the packet to the ftp server. This

Markus Friedl wrote: > > ?'m not sure where the 'bug' is and whether this is 'really' a bug. > > try to talk to the openssh-unix-dev list, i'm too busy right now :( > > -m > > On Thu, Aug 16, 2001 at 03:51:19PM +0100, Mark Reardon wrote: > > Hello Markus, > > > > I recently posted you with a mention of the 2.9p2 possible problem

When I SSH using protocol 1 from a Debian box running OpenSSH 2.9p2-4 to a sparc.sunos5 box running vanilla OpenSSH 2.9.1, after a little while (of inactivity?) I get the following message on the client terminal: Disconnecting: protocol error: rcvd type 98 Looking further, this message is actually caused by the SSH daemon. However, I'm at a loss to determine why sshd is doing this. I attach

I'm wondering if I'm seeing a regression of 5616 with 3.4.8. I'm trying to set-up pptpd with winbind, which I'm doing on two machines on Debian lenny, and I'm trying on Debian Squeeze now. The Windows client is saying "Error 778: It was not possible to verify the identity of the server." The logs say that everything is ok, and that the client is hanging up the

Hi, When do the sftp to remote server with file system full, sftp connection get "ID mismatch" and connection closed. Is it supposed to get the "sftp>" prompt back? I try with V3.7.1p2 and V3.8.1p1 and have the same result. Please help. rdsosl.sef_cdf-831# sftp -v edosuser at rdsosl Connecting to rdsosl... OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004 debug1: Reading

Beyond any more general questions of whether pam sessions *should* be run as root, is there an immediate security concern with moving the pam_open_session (and pam_setcred) stuff to the parent (root) process? (E.g., via the patch below.) -- Mike Stone diff -u -r1.4 auth-pam.c --- auth-pam.c 25 Jun 2002 00:45:33 -0000 1.4 +++ auth-pam.c 25 Jun 2002 20:33:41 -0000 @@ -286,6 +286,8 @@

https://bugzilla.mindrot.org/show_bug.cgi?id=1383 Summary: Tons of "rcvd too much data win" messages since upgrading to 4.7p1 Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2

I compiled OpenSSH 3.6.1p1 on NCR MP-RAS v4.3 (or at least "uname -a"'s output of 4.0.3.0 suggests v4.3, I'm not positive). I was able to compile zlib (1.1.4) and openssl (0.9.7a) with little trouble. OpenSSH took hand-hacking the includes.h file as follows: diff -cr openssh-3.6.1p1/includes.h openssh-3.6.1p1-customized/includes.h *** openssh-3.6.1p1/includes.h Sun Oct 20

We installed openssh 3.1p1 on our Solaris 2.8 machine using gcc 2.95.2. During the installation, we modified ssh_config and sshd_config to enable X11 and agent forwarding. In sshd_config, we changed the following line to read: X11Forwarding yes In ssh_config, we changed the following two lines to read: ForwardAgent yes ForwardX11 yes Both files are set to permission readable

On 10/12/15 10:54, Rowland penny wrote: > On 10/12/15 10:44, L.P.H. van Belle wrote: >> Hai, >> >> Ah, ok, wel, yeah, i was missing the NS on the SOA. >> >> This is imo a bug, i dont know it this is by design for samba, >> so maybe a samba dev can answere this since every joined DC should >> have a NS record on the SOA as far as i know, but thats my

can someone confirm this? it does not happen on openbsd. -------------- next part -------------- An embedded message was scrubbed... From: Florian Wunderlich <fwunderlich at devbrain.de> Subject: Re: fds closed after SIGCHLD bug still in newest version Date: Wed, 22 Nov 2000 14:44:17 +0100 Size: 3926 Url: