similar to: Portable SSH SRPMS problem / RH 6.X

is there a way of specifying preferred key exchange methods on client end with OpenSSL 3.1 using ssh2? i'm trying to determine which key exchange method is actually being used for a connection but i'm i bit confused by the debug messages: ... debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex:

Hello, I successfully compiled and installed; libao-0.6.0-1 libao-devel-0.6.0-1 libogg-1.0beta4-1 libogg-devel-1.0beta4-1 libvorbis-1.0beta4-1 libvorbis-devel-1.0beta4-1 as RPM's using the spec files included in the sources. (the RPM's available for download are for RPM 4 users, I guess?) Anyway, now I'm trying to compile vorbis-tools using the spec file included and I got the

Hi Is there an option in the spec that i can say on remove do X - eg move a backup file back into place etc? eg %onremove mv foo bar thanks

The segfault logged below occurs on two different Red Hat 6.2 systems running OpenSSH installed from the 2.5.1p2 RPM. (Similar problems occured with the 2.5.1p1 RPM.) The most recent of the Red Hat 6.2 systems tested is stock except for an upgrade of rpm-3.0.5-9.6x.i386.rpm and the install of Red Hat's release of openssl-0.9.5a-3.i386.rpm, both necessary for the OpenSSH RPM install. The

Outside the known 'Hang-on-exit' bug and the Solaris 'PAM_TTY_KLUDGE' required. *WHAT* other issues *MUST* be address before 3.0 which is approaching fast? Those running NeXTStep I need conformation that it works under NeXT. My current Slab is packed in a storage unit due to a fire in my apartment complex (happened above me so I'm wrapping up dealing with that crap =). -

Sorry if this is the wrong place to post this... the OpenSSH Mailing Lists page is a little ambiguous. I've tried to compile OpenSSH 3.0.1p1 & 3.0.2p1 on two different Solaris platforms, one running Solaris 8 and the other Solaris 9 beta. It configures fine, but the make dies: gcc -I/opt/include -Wall -Wpointer-arith -Wno-uninitialized -I. -I. -I/opt/include -I/opt/include

Hi! Here is the patch to support tcp wrappers with x11-forwarded connections. The patch is for openssh-3.0.1p1 but it works fine with 2.9.9p2 too. I've understood that this will not be included in the official version because it adds complexity (?!) to openssh. Binding the forwarded port to localhost doesn't solve all problems. I've understood that you should also implement

Hello... I am a student at G?teborgs university who is the system adminstrator in one of the student clubs here. We run about 10 computers with one server. Mainly linux and all run openssh. We have closed telnet so only ssh-connections is allowed. Last night i got a mail from one of the system adminstrators at G?teborgs university saying that there was a possible root exploit in all openssh

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've noticed that when I use ProxyCommand commands to connect, the commands do not exit when ssh exits. This results in a bunch of commands piling up on the machine over time. I experimented with four machines: linux-2.2.19+patches, openssh-3.0.1p1 linux-2.2.14+patches, openssh-3.0.1p1 freebsd-4.5-stable, openssh-2.9 localisations 20020307

As has often been mentioned, Solaris (at least 7 and 8) gives a debug1 message on logout: Cannot delete credentials. This occurs when in auth-pam.c, function do_pam_cleanup_proc(), pam_setcred(__pamh, PAM_DELETE_CRED) is called under UID 0. I suggested a patch for this on Nov 22, 2001, based on openssh 2.9.9p2 through 3.0.1p1. [The attempt in my patch to reset to UID 0 by "if (!flag)

Hello, I came across an interoperability problem in OpenSSH 3.0p1 and 3.0.1p1 concerning the AFS token forwarding. That means that the new versions are not able to exchange AFS tokens (and Kerberos TGTs) with older OpenSSH releases (including 2.9p2) and with the old SSH 1.2.2x. In my opinion this problem already existed in Openssh 2.9.9p1, but I have never used this version (I only looked at the

Hello, I just upgraded from 2.9p2 to 3.0.1p1 and good news. I don't have to patch channels.c to get Remote Port Forwarding to work. That is fantastic. It appears, however, that -g still doesn't work. I checked the archives and it doesn't look like anyone has mentioned it yet. What does work is if I ssh to a machine I can telnet to localhost on the forwarded port, but connecting to

openssh password expiration problemPatrick, Indeed password aging does not work with OpenSSH 3.0.1p1 on Solaris 2.6. >From what I can tell something is different with Solaris 2.6 and Solaris 2.8. I know that password expiration doesn't cause a problem on Solaris8. I'm unclear as to whether the problem is with OpenSSH code or Solaris. All I know is that the latest PAM patches are not

Hello, openssh-3.0.1p1 appears to transmit and parse tty modes correctly, but later in the code it uses vhangup() to close all tty references and reset the tty to default modes. I don't think that vhangup() should be needed on Unix98 ptys, possibly not even on BSD ptys, and I am probably wrong, so please tell me where. Of course vhangup() clears all tty modes, so you need to save them

We are using OpenSSH (portable) version 3.0.1p1 on Linux 2.2.14-10 with RedHat's distribution of PAM 0.72-20.6.x for rsync'ing RRDTool data between two machines (among other things). When running 'rsync -essh -avz', everything works fine but the system log on the sshd side shows: PAM_pwdb[8021]: authentication failure; (uid=0) -> rrd for sshd service sshd[8021]: Accepted

The attached patch adds a new 'ConnectTimeout' option (man page updated in patch) to avoid wasting time when the target host is down. I needed that because I was using rsync/rdist over ssh for massive files update and the default connect() took too long for my purpose. The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX on Linux, Solaris and HP-UX without

NEW message w/ URL to zip archive containing debug output. Hi I'm having huge problems with OpenSSH 3.0.1p1, compiled with OpenSSL 0.9.6b 9 Jul 2001 and running with prngd_0.9.23, it disconnects unexpectedly during client session due to bad packet length and corruped MAC on input, according to debug anyway. What can cause this kinds of errors? I've verified that both se9104/server and

Hi list, I'm not sure whether this (see below) is a "bug" or a feature but as I cannot find any information on this neither in the INSTALL file nor via ./configure --help or somewhere else, I would like to ask you whether there is an answer to my question. Thanx a lot & kind regards - have a nice day, B. Courtin Question: --------- I lately updatet from OpenSSH 3.0.1p1 to

Hello, There is a small but annoying problem with linking libwrap in openssh. The library is added to LIBS which makes it be linked in to all binaries. This is unnecessary and leads to bogus dependencies if libwrap is a shared library. Following is a trivial fix that reserves a separate autoconf substitution variable LIBWRAP, which is only used for sshd. Please apply. Maciej -- +

http://bugzilla.mindrot.org/show_bug.cgi?id=141 Summary: openssh-3.1p1-1.src.rpm will not build on RedHat Linux 6.1 Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Build system AssignedTo: