similar to: Socket options not properly set for ssh and sshd.

Displaying 20 results from an estimated 1000 matches similar to: "Socket options not properly set for ssh and sshd."

2001 Jan 12
0
Socket options not properly set for ssh and sshd.
I mentioned this problem in a previous post (in November). This time I'm including a patch. Version: OpenSSH_2.3.0p1 Keywords: setsockopt keepalive hang masquerade interactive Symptom: For protocol 2, socket options (especially keepalive) are not being properly set for OpenSSH_2.3.0p1, even when request in the config files. Furthermore (for either protocol), keepalive is only set for
2002 Sep 06
0
use of setsockopt(SO_LINGER)
I would like to remove setsockopt(SO_LINGER), as there does not seem to be a reason for its use. If you know of specific reasons we should keep any of these let me know, or run this patch in local test trees where possible. This is against OpenBSD, but should apply to portable with some fuzz. Index: channels.c =================================================================== RCS file:
2001 Feb 01
0
warnings on aix325
Hi, I'm trying to compile openssh2.3.0p1 on aix3.2.5. Can I ignore this list of warning messages? bsd-bindresvport.c: In function `bindresvport_af': bsd-bindresvport.c:94: warning: implicit declaration of function `bind' bsd-rresvport.c: In function `rresvport_af': bsd-rresvport.c:64: warning: implicit declaration of function `bzero' bsd-rresvport.c:82: warning: implicit
2015 Jul 29
2
[PATCH] ssh: Add option to present certificates on command line
Allow users to specify certificates to be used for authentication on the command line with the '-z' argument when running ssh. For successful authentication, the key pair associated with the certificate must also be presented during the ssh. Certificates may also be specified in ssh_config as a CertificateFile. This option is meant the address the issue mentioned in the following
1999 Dec 28
0
Patches to report rsaref build and to call pam_setcred
I've attached two patches. The first just changes the output of "ssh -V" to print that it was built against rsaref if libRSAglue (which is built as part of openssl only when it is built against rsaref) is present at build-time. The second adds appropriate calls to pam_setcred() in sshd. Without them, our systems can't access AFS because the PAM modules only get tokens at a
2003 Apr 09
1
[Bug 541] packet_set_interactive typo
http://bugzilla.mindrot.org/show_bug.cgi?id=541 Summary: packet_set_interactive typo Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: furrier at
2000 Sep 18
3
OpenSSH 2.2.0p1 + Redhat 6.2 - Problem with scp
Hi, Chances are this is me stuffing something up, but in cases its not, this is my problem. I've just installed the latest port of OpenSSH on a few Redhat 6.2 machines. That is version 2.2.0p1. Everything compiles ok, and using the supplied init and pam files I got openssh working without to much difficulty. In fact it was easier than the commerical versions. I can use ssh to login to remote
2003 Apr 23
1
[Bug 545] openssh-3.6.1p1 does not build on SunOS: IP_TOS not defined
http://bugzilla.mindrot.org/show_bug.cgi?id=545 Summary: openssh-3.6.1p1 does not build on SunOS: IP_TOS not defined Product: Portable OpenSSH Version: 3.6p1 Platform: All OS/Version: SunOS Status: NEW Severity: trivial Priority: P3 Component: Build system AssignedTo:
2003 May 10
1
OpenSSH_3.6.1p2 getsockopt TCP_NODELAY bogus message on Solaris 8
I ran into the following problem the first time I used OpenSSH_3.6.1p2 on Solaris 8 (sparc, 32-bit): $ ssh kiwi Enter passphrase for RSA key '/net/sic/export/ford/home/eggert/.ssh/identity': getsockopt TCP_NODELAY: Socket operation on non-socket Last login: Sat May 10 14:27:01 2003 from ip-66-80-53-59.d Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
2000 Sep 14
2
openssh 2.2.0p1 fails with openssl 0.9.6-beta1
On Wed, Sep 13, 2000 at 09:13:26AM +0000, Graham Murray wrote: > On upgrading to openssl 0.9.6-beta1, I find that openssh 2.2.0p1 fails > to connect. I did some more experiments and also saw the problems. They occur when using a 0.9.6-beta client to connect to 0.9.5a and 0.9.6-beta servers. They also occur when using a 0.9.5a client connecting to a 0.9.6-beta server. Connections fail with
2000 Oct 20
0
openssh problem on SGI 6.5 platform
We are in the process of converting over to openssh at UNC. I've built openssh 2.20p1 for all supported platforms at UNC: AIX 4.3 AIX 4.2 Linux 2.2 Solaris 2.7 Solaris 2.6 SGI 6.5 We been running for about a month now and have only one reported problem--which came up today: When running ssh on a machine running SGI 6.5 you get the following error: %ssh overlord rsa_public_encrypt()
2000 Oct 12
1
openssh on solaris x86
Hi, we're using SSH-1.5-OpenSSH-1.2.2 and SSH-1.5-OpenSSH-2.2.0p1 on solaris for x86 (Solaris 2.8). Both Versions seem to have a problem in forwarding ports that may concern htonl/ntohl: SSH Version OpenSSH_2.2.0p1, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). debug: Seeding random number generator debug: ssh_connect: getuid 0 geteuid 0 anon 1 debug: Connecting to 6.0.1.1
2001 Oct 08
1
Hanging ssh session...
Hi All, I am not sure if this is the same thing as the hang on exit bug, so sorry if this is a duplication of previous stuff. Essetntially I am experiencing ssh hangs with about .5% - 1% of my connections. I am running 2.9p2, on Solaris 7. I actually have empirical data on the hangings, as I wrote a script to create these connections in an endless loop, setting an alarm so I could recover
1999 Sep 30
1
A little utility for checking socket settings
I've been in discussion with a colleague who had to reduce (!) SO_SNDBUF to get decent performance, and so wrote this little tool. It tells you the system default for most of the settable socket options. It can't do linger, as the value is a struct instead of an int, but that's probably uninteresting to Samba folks. Run this to see what you'd have if you didn't set any
2000 Oct 30
2
SSH not responding.
SSH doesn't seem to be responding to me. The machine I am connecting to is running Linux, and I could connect to it fine from windows running the SSH client. But now I can no longer connect. From Linux, this is the output: pc078:~$ ssh -v 208.240.199.51 SSH Version OpenSSH_2.2.0p1, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). debug: Reading configuration data
2000 Oct 30
2
RhostsAuthentication + nondefault port doesn't work?
Hello all, It seems that RhostsAuthentication does not work on non-default port no matter what when connecting from OpenSSH (2.1.1, 2.2.0 tried) either with protocol 1 or protocol 2 (shouldn't work either..). _However_ when connecting with SSH.COM Ltd's ssh, RhostsAuthentication works just fine! Checking the port number of ssh client you can see that OpenSSH doesn't assign
2000 Sep 14
5
ListenAddress option.
How do I compile OpenSSH so that I can use: ListenAddress 0.0.0.0 in my sshd_config file ? Currently I get: [root at dark openssh-2.2.0p1]# sshd -d debug: sshd version OpenSSH_2.2.0p1 debug: Seeding random number generator debug: read DSA private key done debug: Seeding random number generator error: getnameinfo failed fatal: Cannot bind any address. if I try to use "ListenAddress
2000 Apr 07
3
DG/UX R4.20MU03
Has anyone had any experience with ssh and DG/UX? I tried the ./configure and it could not determine the hosttype. After that problem was worked-arounded I get a LOT of warnings about declaring functions multiple times and then the compile fails with: packet.c: In function `packet_set_interactive': packet.c:803: `IPTOS_LOWDELAY' undeclared (first use this function) packet.c:803: (Each
2005 Jul 25
1
ssh -f won't detach properly when run from cron.
Hi, In file ssh.c, in function "ssh_session2", this piece of code: /* If requested, let ssh continue in the background. */ if (fork_after_authentication_flag) if (daemon(1, 1) < 0) fatal("daemon() failed: %.200s", strerror(errno)); implements the "-f" option, but when run from cron, it does not detach properly because of the second parameter
2000 Sep 13
2
Can't connect to server using protocol v2?
Is this really caused by a buggy server, or is this an interoperability problem? It seems to work ok when I specify -o "protocol 1" on the command line. Thanks, Greg [gleblanc at grego1 gleblanc]$ ssh -v login.metalab.unc.edu SSH Version OpenSSH_2.2.0p1, protocol versions 1.5/2.0. Compiled with SSL (0x0090581f). debug: Reading configuration data /etc/ssh/ssh_config debug: Applying