similar to: Different ciphers, MAC, compression for inbound and outbound .

SSH.COM says their SSH2 is not vulnerable to the ZLIB problem even though they use the library (details below). Can OpenSSH say the same thing? In either case, it seems like there ought to be an openssh-unix-announce message about what the situation is. I may have missed it, but I don't believe there was one. Yes, openssh doesn't have its own copy of zlib source but it would still be

Le Jeudi 11 Avril 2002 21:09, m.ibarra at cdcixis-na.com a ?crit : > I was curious to know if you had any luck in getting openssh's sftp > server properly configured to allow chrooted sftp logins? I have had > no success and need something quickly. Dear Mike, Unfortunately, I did not succeed to have it work. I got in contact with James Dennis <jdennis at law.harvard.edu>, who

Hi, Do you any good SIEVE resources for a poor beginnner ? I'd to translate some of my current procmail rules into SIEVE. I have, for example, a "generic" rule that is able to sort almost any message from/to a mailing-list into a dedicated folder -i.e one rule for almost all my lists. Any recomendation ? Thank you

Hello everybody, I have a problem specifying identities with the -i option. For easier ssh invocations, I have setup my ssh_config files with entries like the following: Host *.domain.name Port 23457 StrictHostKeyChecking yes UserKnownHostsFile /dev/null GlobalKnownHostsFile /etc/ssh/known-hosts/domain.name IdentityFile ~/.ssh/%h-dsa IdentityFile ~/.ssh/%h-rsa IdentityFile

i have a problem, i am installing openssh-3.6.1, in digital unix version 4.0d, and no can,t install for this error, configure: error: *** Can't find recent OpenSSL libcrypto (see config.log for detail) please helpme Horacio Mari?a

-------------- next part -------------- An embedded message was scrubbed... From: Marc-Christian Petersen <m.c.p at gmx.net> Subject: Re: OpenSSH 3.6 released Date: Mon, 31 Mar 2003 18:50:18 +0200 Size: 3785 Url: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20030331/7da804d0/attachment.mht

http://bugzilla.mindrot.org/show_bug.cgi?id=1051 Summary: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Product: Portable OpenSSH Version: 4.1p1 Platform: ix86 URL: http://www.tietoenator.de OS/Version: Linux Status: NEW Severity: critical Priority: P4

-------------- next part -------------- An embedded message was scrubbed... From: John Horne <J.Horne at plymouth.ac.uk> Subject: Openssh still logs in while passwd is locked Date: Wed, 22 May 2002 15:20:08 +0100 (BST) Size: 2486 Url: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20020522/8eef78dd/attachment.mht

Hi, Is there a way to restrict port forwarding on the server? I want only port 8080 on the server to be available to clients. Example when i give this command clients should be able to connect: ssh -L 30300:localhost:8080 .... When i give this for example clients should not be able to connect: ssh -L 30300:localhost:4040 .... I tried this option in config file of server: PermitOpen

Can anybody help me with this : ? I first generated rsa key with this : ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key then I went on to generate the DSA key too....(just incase my SSHD does not like RSA). ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key and then I ran root at 00_00_09_PECA_NP1:/usr/bin# sshd -d -d -d -d -d -d -d -d -d debug3: RNG is ready, skipping seeding debug2:

No answers on secureshell at securityfocus.com I must be doing something wrong or the server seems to ignore my bind request. Port forwarding is working it just bind to all ips and ignores my bind request. I've also tried this with an rfc1918 address opposed to a loopback and had the same results. Google and the archive haven't helped. Thanks in advance for your time and consideration.

http://bugzilla.mindrot.org/show_bug.cgi?id=1272 ------- Comment #9 from dtucker at zip.com.au 2007-02-19 23:22 ------- Another thought: do you have multiple instances of libgcc? Perhaps one in /usr/local/lib and one elsewhere? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

OpenSSH 3.1 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 version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. We would like to thank the OpenSSH community for their continued support and encouragement. Important Changes: ================== - /etc/ssh/ now default

OpenSSH 3.1 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 version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. We would like to thank the OpenSSH community for their continued support and encouragement. Important Changes: ================== - /etc/ssh/ now default

I've installed Sun's SUNWski package on Solaris 8 (32-bit) that provides a /dev/random interface. It appears to as cat'ing it gives me a bunch of well, random data. However, when I ran my configure, it gives me the WARNING.RND message to the effect that I'm using the built-in. I've seen allusions on this list to building openssl with to get random support, so I rebuilt it

Now that ssh-rand-helper has been segregated into a separate program, I'd like to revisit an old question about its entropy gathering. - would it be desirable to make it possible for ssh-rand-helper to fall back to external commands if PRNGD cannot be reached, instead of choosing one or the other at compile time? - When using PRNGD, the program gets 48 bytes of entropy from PRNGD,

I'm trying to update an ssh 1.2.27 to OpenSSH 3.0.2p1 and am running into a problem. I've successfully built zlib 1.1.4, OpenSSL 0.9.6c, and tcp_wrappers , but when I attempt to run configure, I get the error about the missing posix regex. So I attempted to download and use pcre (the Perl hack to expose perl regex to posix. But I can't build that since it calls strtoul() (string to

maybe this is a silly question ;-) But why is it possible to login on a machine with a locked account (passwd -l ) via pubkey-authentication (authorized_keys) ? I use OpenSSH3.01p1on Solaris8 with PAM support so I thought this should not happen. If this is the normal behaviour and built in intentionally what would be the easiest way to lock an account without deleting the users authorized_keys ?

Here is a patch to add the missing scp -1 and -2 options to eliminate confusion for users familiar with the commercial version of SSH. This patch and others are maintained on the secure nfs (SNFS) web page: http://www.math.ualberta.ca/imaging/snfs/ -- John Bowman University of Alberta diff -ur openssh-3.0.2p1/scp.c openssh-3.0.2p1J2/scp.c --- openssh-3.0.2p1/scp.c Sun Oct 21 18:53:59 2001 +++

Since there never was an answer on the secureshell at securityfocus.com list to this question, I thought I'd ask you guys on your own list and maybe I'll even get an answer. If the answer involves PAM in any way, then the most obvious question becomes "what about IRIX, Tru64, or any other platforms whose login procedure does not have PAM?". ----- Forwarded message from Atro