similar to: OpenSSH compile problem on Solaris 8 & 9

Sunil-- Actually, you do not "see that openssl has some patent issues." You do see that OpenSSL implements many algorithms, some of which have been (at various times) been patented or encumbered in some countries. Without knowing what country you're in, none of us here can really give useful advice as to which software/algorithm patents could potentially apply. To the best of my

I hate following up to myself, but I thought a clarification of one point (specifically WRT RC5 which was mentioned in the original question) might be worthwhile...because what I should have said originally was that "To the best of my non-legally- admissible knowledge, however, none of the algorithms in the current *OpenSSH* implementation are currently encumbered by patents that would

Hello, In order to experiment with OpenCA, I have built an RPM for redhat 7.2 of a recent OpenSSL snapshot (the binary rpm on the OpenCA was built with the different target directories and libraries. Unfortunately these recent OpenSSL snapshots seems to break all OpenSSH tarballs and RPMs that I have been able to find. None of them seem to compile successfully, even the snapshots at

I'm testing both sunfreeware and official sun (sfw) samba on Solaris 10. For some reason since yesterday, the smbd process just "hangs" at the start. No log is generated on server side Where smbd is started, I can't find any open port on 139 or 145 My OS is Solaris 10 # uname -a SunOS labo2 5.10 Generic_142900-13 sun4v sparc SUNW,SPARC-Enterprise-T5120 #

Here is a little patch against 2.9p1 that performs the SNK (also known as TIS authserv) challenge-response automaticly instead of asking the user. hope you find it useful. --larry -------------- next part -------------- diff -NuBw openssh-2.9p1/Makefile.in openssh/Makefile.in --- openssh-2.9p1/Makefile.in Thu Apr 26 20:31:08 2001 +++ openssh/Makefile.in Wed Jun 6 16:15:56 2001 @@ -43,9 +43,9

Hello, I have tried to compile openssh-3.1p1 and then two later snapshots. It seems that I can not have support for KTH-Krb4, according to this errorlist from make: gcc -o ssh ssh.o sshconnect.o sshconnect1.o sshconnect2.o sshtty.o readconf.o clientloop.o -L. -Lopenbsd-compat/ -R/usr/local/ssl/lib -L/usr/local/ssl/lib -L/usr/local/lib -R/usr/local/lib -L/usr/athena/lib -R/usr/athena/lib -lssh

Hi guys, and here's a security related bug report. I think it's has been fixed in the 2.2.x-release of openssh, but I'm not sure. I tried to reproduce the problem with my 2.2.0p1 and could find any difference in the behaviour of ssh depending on wether PermitRootLogin was set to no. Could someone please confirm that this problem is not existing anymore? > When PermitRootLogin is

1) Thank you to whoever makes these available. 2) I have a problem with the SRPMS, they will not --rebuild on a RedHat 6.2 system. Can anyone help me to get this to build here? [root openssh]# rpm --rebuild openssh-3.0.1p1-1.src.rpm Installing openssh-3.0.1p1-1.src.rpm line 74: Unknown tag: 0.9.5a Some Info: [root openssh]# rpm -qa | grep rpm rpm-python-3.0.5-9.6x rpm-build-3.0.5-9.6x

I'm trying to compile Samba 3.0.4 with Active Directory support on OpenBSD 3.5, using the native Kerberos libraries (which happens to be Heimdal 0.6). Unfortunately, ./configure isn't working right. I think i'm missing a switch or something. If anyone can help me figure out what the problem is, i would really appreciate it. First a bit of info on OpenBSD's Kerberos path

I'm trying to compile Samba 3.0.4 with Active Directory support on OpenBSD 3.5, using the native Kerberos libraries (which happens to be Heimdal 0.6). Unfortunately, ./configure isn't working right. If anyone can help me figure out what the problem is, i would appreciate it. First a bit of info on OpenBSD's Kerberos path layout, in case it matters: /usr/libexec - daemons

-----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

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

This screen shot shows the full command and the Windows 98 boot : http://www.blastwave.org/dclarke/stuff/thin/qemu_082_sparcv8plus_win98_boot.png the disk is recognized as blank and a partition gets created fine then format http://www.blastwave.org/dclarke/stuff/thin/qemu_082_sparcv8plus_win98_fmtC.png there are minor graphics cludges during the install

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