similar to: OpenSSH 2.9

Hello all, scp does not preserve links (neither soft neither hard) It is a problem with recursive option (-r) when you met some links like Openssh -> . In 2.3.0p1 it failled because of too long argument. Also I upgrade (my client an HPUX-11.0 and my server an redhat-6,2 x86) openssh to the last release 2.9p2. But this release create in a loop (i presume until fs full) subdirectories

Hello, I'm new to the list, and I've been having a very weird problem with the IRIX version of portable openssh that I think may be a bug in this platform... I've looked through the FAQs and the man pages and can't find why this might not be working. The ssh binary is setuid-root, both ssh and sshd are told that Rhosts and RhostsRSA auth is OK in their config files, etc. I

Hi. Does anyone use UsePrivilegedPort or have ssh(1) setuid, and if so for what use case? ssh(1) has had code in it to support installing setuid root since approximately forever, however OpenBSD has not shipped it in that configuration since 2002 (and I suspect these days no vendor does). As far as I can tell, all of the reasons for this no longer apply: - setuid root was needed to bind to a

$ ps -ef | grep sshd root 285 1 0 Nov 15 ? 0:03 /usr/local/sbin/sshd root 23740 285 0 16:13:18 ? 0:00 /usr/local/sbin/sshd root 23875 285 0 16:28:14 ? 0:00 /usr/local/sbin/sshd user 23905 23899 0 16:28:31 pts/3 0:00 grep sshd $ ls /usr/local/sbin /usr/local/sbin: No such file or directory $ date Wed Mar 21 16:28:50 PST 2001 $ telnet 127.0.0.1

Greetings; I've been reading the OpenSSH source code and have a question about the des_ssh1_setiv function in cipher.c. (cut-n-pasted here from cipher.c v1.47) : static void des_ssh1_setiv(CipherContext *cc, const u_char *iv, u_int ivlen) { memset(cc->u.des.iv, 0, sizeof(cc->u.des.iv)); } This doesn't use the *iv parameter. Compare with: static void

http://bugzilla.mindrot.org/show_bug.cgi?id=642 Summary: Can't build build OpenSSH 3.7 on OpenBSD 3.0 Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: OpenBSD Status: NEW Severity: critical Priority: P2 Component: Build system AssignedTo: openssh-bugs at mindrot.org

pausmith at nortelnetworks.com (Paul D. Smith) had a problem where his 2.1.1p1 wouldn't connect if it was running set-UID root, unless "-P" was given. Gert Doering <gert at greenie.muc.de> suggested a firewall problem. Damien Miller <djm at mindrot.org> tried to help too. Now I've got the same problem: my 2.1.1p1, 1.2.2, and 1.2.3 clients won't connect to

On 2020-02-06 at 13:28 +1100, Darren Tucker wrote: > Like this. > --- a/sshd_config.5 > +++ b/sshd_config.5 The ssh_config.5 also has a copy of this and presumably needs the same change, unless I've misunderstood. -Phil

Is there any plan to add socks 4 or socks 5 support to openssh like the original ssh developed in finland?? Michael Michael at bizsystems.com

'ello Markus/folks@, I downloaded 3.0.2 today and went and looked at openbsd.html and found some errors. Patch attached. Patch for http://www.openssh.com/openbsd.html Hope that helps, Rgds -- Kevin Sindhu <kevin at tgivan dot com> Systems Engineer TGI Technologies Inc. 107 E 3rd Avenue Tel: (604) 872-6676 Ext 321 Vancouver V5T 1C7 Fax: (604)

I'd like to see a feature of the commercial ssh in openssh: AllowHosts xxx.yyy.xxx.yyy *.domain.net DenyHosts xxx.yyy.xxx.* name.domain.net This allows or denies connects from certain machines (including wildcard matching). Is there any chance for this feature to be included? No, we don't want to use tcp-wrapper for this. Bye.

Darren Tucker <dtucker at zip.com.au> writes: > On Tue, Nov 8, 2016 at 3:30 PM, Harry Putnam <reader at newsguy.com> wrote: > [...] >> After having 7.3p1 & 6.8p1 fail with same wording... I tried 6.7p1 and >> find it fails with what looks like the same problem but has slightly >> different wording. > > I set up the same versions (server:OpenSSH_6.6p1,

Hi all. I was getting something working over socks5 and was trying to figure out why it kept using socks4. It wasn't, it was just a misleading debug message.... Patch applies to either OpenBSD or Portable. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience

I love SSH's ability to dynamically forward ports using SOCKS (either -D or DynamicForward) (ie "ssh -D 1081 private.mine.net"). But the thing that has caused me some pain, is that only SOCKS4 is supported. The SOCKS4 proxy specification does not permit hostnames, but only IP addresses. This isn't much of a problem if the target host is a public Internet host or otherwise DNS

On 2020-02-05 at 20:39 -0500, Phil Pennock wrote: > On 2020-02-06 at 10:29 +1100, Damien Miller wrote: > > OpenSSH 8.2p1 is almost ready for release, so we would appreciate testing > > on as many platforms and systems as possible. This is a feature release. > > > * The RFC8332 RSA SHA-2 signature algorithms rsa-sha2-256/512. These > This actually affects me:

This provides SOCKS4A support, which allows a SOCKS4 client to provide a host name instead of an IP address. It indicates that it's doing so by using a known-invalid IP address 0.0.0.x (where x != 0), and then appending the NUL-terminated hostname to the connection request. Although we check for the terminating NUL manually and the 'fatal(len %d > have %d)' should never happen, the

$ ssh -Q HostKeyAlgorithms Unsupported query "HostKeyAlgorithms" $ ssh -V OpenSSH_7.4p1, OpenSSL 1.0.2u 20 Dec 2019 On Mon, Mar 2, 2020 at 2:24 PM Christian Hesse <list at eworm.de> wrote: > Luveh Keraph <1.41421 at gmail.com> on Mon, 2020/03/02 14:07: > > When I do ssh -Q key, where ssh is the OpenSSH 7.4p1 client, I get the > > following output: > >

OpenSSH 7.0 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. OpenSSH also includes transitional support for the legacy SSH 1.3 and 1.5 protocols that may be enabled at compile-time. Once again, we would like to thank the OpenSSH community

> Winton-- > > Excellent! Absolutely wonderful. > > I'm wondering which apps/encapsulators support 4A? This gets me > around > the DNS leakage problem quite nicely. > > Incidentally, we do need SOCKS5 support -- if for no other > reason, the > fact that there's *operating system* level support in OSX for SOCKS5 > redirection. So

http://home.t-online.de/home/Andreas.Steinmetz/windows/socks.html An utter pain to make functional under XP, but this is pretty significant for users of Dynamic Forwarding. More good stuff coming soon (as I always say). --Dan