Displaying 20 results from an estimated 3000 matches similar to: "Configure option '--with-ssh1' breaks openssh-7.3p1"
2016 Aug 03
2
Configure option '--with-ssh1' breaks openssh-7.3p1
On 08/03/16 02:12, Darren Tucker wrote:
> On Wed, Aug 3, 2016 at 7:42 AM, rl <rainer.laatsch at t-online.de> wrote:
> [...]
>> /Data/openssh-7.3p1/DESTDIR/usr/local/sbin/sshd -p 222 -f \n
>> DESTDIR/usr/local/etc/sshd_config
>
> It looks like you have an embedded newline in the config file name
> you're passing to sshd. If that's the case I'm
2016 Aug 03
2
Configure option '--with-ssh1' breaks openssh-7.3p1
On 08/03/16 03:19, Darren Tucker wrote:
>
> Yes. Debugging something on a system you can't interact with is hard
> enough without having information withheld.
>
I'll run again and add the relevant unedited texts as attachments.
There is nothing in /var/log/secure.
Also a diff between the config.h 's without and with --with-ssh1 is
attached.
I have a centos-6.7 under
2016 Aug 03
2
Configure option '--with-ssh1' breaks openssh-7.3p1
OK, with this additional information I can now reproduce it.
Based on some quick experiments it seems to be triggered when sshd is
built --with-ssh1 and the config does not *load* a Protocol 1 host
key.
Works:
Protocol=1,2 + Hostkey not specified
Protocol=1,2 + Hostkeys for both protocols specified.
Doesn't work:
Protocol=2 + Hostkey not specified.
Protocol=1,2 + Hostkeys specified only for
2016 Aug 26
2
krb5support missing in Makefile when configuring --with-krb5=<pathtokrb5> required by newer krb5 versions
See subject. Am I missing here something or is it a bug?
Best regards
Rainer
2012 Jan 28
1
PATCH: Support for encrypted host keys
Hello all,
I recently found myself wanting to run sshd with passphrase-protected host keys rather than the usual unencrypted format, and was somewhat surprised to discover that sshd did not support this. I'm not sure if there's any particular reason for that, but I've developed the below patch (relative to current CVS at time of writing) that implements this. It prompts for the
2008 May 27
6
Openssh + AFS
The native authentication methods of openssh are
(not counting insecure RhostsRSAAuthentication)
1) public key
2) password
For users with home dirs in AFS space, method 1) does not work.
Except with (non foolproof) fiddling on the access controls within
the home directory. This might lead to security issues when done
by inexperienced users.
Without some work, only 2) remains. Being forced to send
2017 Jan 06
0
[Bug 2583] ssh-keyscan: fatal error in conread() when scanning ssh1 keys without ssh1 support
https://bugzilla.mindrot.org/show_bug.cgi?id=2583
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Blocks| |2647
CC| |djm
2001 Jan 09
1
sshd: DES in SSH1 ?
I see that commercial SSH version it is possible to
run sshd in SSH1 using DES (i.e, accepting SSH-DES clients).
I understand from Damien Miller that
Cisco routers also run in only SSH1 DES mode.
Is it possible in openSSH to configure sshd (compile-time/runtime)
to run sshd in SSH1 or SSH2 mode and accept SSH1 or SSH2 DES clients ?
[I would like to be able to run sshd in SSH1/DES mode ]
Is
2011 Jan 31
1
Generate SSH1 host key by default?
Hi,
the OpenSSH installation script for Cygwin still creates a SSH1 host key
by default.
My question is, wouldn't it make more sense to drop all auto-generation
of SSH1 keys from the default installation procedure? I mean, nobody
should use SSH1 anymore, right? Or should the script stick to it for
some reason?
Corinna
--
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat
2003 Nov 06
3
SSH1 vs. SSH2 - compression level
Hello,
I was searching for this information virtually everywhere, but as I
couldn't find it - I'm asking here.
I was wondering, why setting the Compression Level was removed in SSH2,
and if on, is always set to 6.
In SSH1 it was possible to set the Compression Level from 1 to 9.
I have made some tests with Compression Levels using scp: SSH1,
compression 9 (highest available for
2010 Feb 09
0
[Bug 1712] New: partial server keep-alive implementation for SSH1
https://bugzilla.mindrot.org/show_bug.cgi?id=1712
Summary: partial server keep-alive implementation for SSH1
Product: Portable OpenSSH
Version: 5.3p1
Platform: Other
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: ssh
AssignedTo: unassigned-bugs at mindrot.org
2015 Mar 26
2
FYI: SSH1 now disabled at compile-time by default
On Thu, Mar 26, 2015 at 10:19:05 -0700, Dan Kaminsky wrote:
> Communication is a two way street. If OpenSSH wants to go down the route
> of single releases, like the browsers did, it can remove its minor numbers,
> like the browsers did.
>
There's no question of "going down the route." This has been the
practice with OpenSSH for many years -- if not from the beginning.
2015 Mar 26
2
FYI: SSH1 now disabled at compile-time by default
No, I just think 15 years or so is more than enough time to have
addressed the issue.
On Thu, Mar 26, 2015 at 14:05:08 -0700, Dan Kaminsky wrote:
> So, this isn't your problem and you don't respect the people's whose
> problem it is.
>
> On Thu, Mar 26, 2015 at 12:43 PM, Iain Morgan <imorgan at nas.nasa.gov> wrote:
>
> > On Thu, Mar 26, 2015 at 11:55:18
2003 Mar 31
1
resource leak in ssh1 challenge-response authentication
If an ssh1 client initiates challenge-response authentication but does
not submit a response to the challenge, and instead switches to some
other authentication method, verify_response() will never run, and the
kbdint device context will never be freed. In some cases (such as
when the FreeBSD PAM authentication code is being used) this may cause
a resource leak leading to a denial of service.
2001 Sep 08
1
force SSH1 and SSH2
This is small patch for scp. It allows to force SSH1 or SSH2.
P.S.: give me Cc: - I'm not subscribed...
--
---------------------------------
pozdr. Pawe? Go?aszewski
---------------------------------
R.I.P. - rest in pieces ...
-------------- next part --------------
--- ./scp.c.org Sat Sep 8 23:37:22 2001
+++ ./scp.c Sun Sep 9 00:07:36 2001
@@ -244,9 +244,11 @@
2015 Mar 22
5
[Bug 2369] New: `ssh-keygen -A` errors on RSA1 when building with SSH1 disabled
https://bugzilla.mindrot.org/show_bug.cgi?id=2369
Bug ID: 2369
Summary: `ssh-keygen -A` errors on RSA1 when building with SSH1
disabled
Product: Portable OpenSSH
Version: 6.9p1
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: ssh-keygen
2015 Mar 24
7
FYI: SSH1 now disabled at compile-time by default
Hi,
OpenSSH git master now disabled SSH protocol 1 at compile time by
default. If you want it back, then you'll need to pass --with-ssh1
to configure before you build.
We expect to ship this configuration for openssh-6.9 in a few
months.
-d
2003 Jun 07
1
openssh reading only SOME ssh1 hostkeys from ssh.com ssh
Hey folks, I've asked this on the security focus mailing list, but no
one seems to know...
I'm in the process of moving my company from old crufty ssh.com ssh1 to
openssh.
On most of our hosts, we've created rsa and dsa keys but managed to KEEP
the old rsa1 key...
However, on a few hosts, openssh has been unable to read the old rsa1
key and has claimed:
debug1: Unsupported
2001 Jun 11
1
Hanging SSH1 client (fwd)
installing openssh on irix is hard?
-------------- next part --------------
An embedded message was scrubbed...
From: Miguel Jardine <mcj2 at georgetown.edu>
Subject: Re: Hanging SSH1 client
Date: Mon, 11 Jun 2001 11:09:38 -0700
Size: 4832
Url: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20010611/c665c85d/attachment.mht
2002 Mar 14
0
[Bug 165] New: Problem with SSH1 Keys on RedHat7.2
http://bugzilla.mindrot.org/show_bug.cgi?id=165
Summary: Problem with SSH1 Keys on RedHat7.2
Product: Portable OpenSSH
Version: 3.1p1
Platform: ix86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo: openssh-unix-dev at mindrot.org
ReportedBy: mmahler at