similar to: [Bug 440] Protocol 1 server key generated at start up even when P1 not used

https://bugzilla.mindrot.org/show_bug.cgi?id=440 Darren Tucker <dtucker at zip.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1429| |ok? Flag| | --- Comment #7 from Darren Tucker <dtucker at

http://bugzilla.mindrot.org/show_bug.cgi?id=440 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From djm at mindrot.org 2003-05-15 21:16

http://bugzilla.mindrot.org/show_bug.cgi?id=440 ------- Additional Comments From markus at openbsd.org 2002-11-21 20:21 ------- when does this happen? i don't see this with version 3.5 (or 2.5.1) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=440 Summary: Protocol 1 server key generated at start up even when P1 not used Product: Portable OpenSSH Version: older versions Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Build system

https://bugzilla.mindrot.org/show_bug.cgi?id=2044 Priority: P5 Bug ID: 2044 Assignee: unassigned-bugs at mindrot.org Summary: error message is printed for SSHv1 when ssh is forced to allocate a pseudo-tty even when it does not have a one Severity: minor Classification: Unclassified OS:

On Tue, 3 May 2016, Colin Watson wrote: > Debian takes the latter approach. Specifically, we have an > "openssh-client-ssh1" binary package that includes only scp1, ssh1, and > ssh-keygen1 binaries; we do not ship any server-side SSHv1 support. I > modelled this on Fedora's approach, which is basically the same aside > from a slightly different package name. >

Rsync Issue Solaris8 When performing a simple rsync between servers I was getting the following error: root:#> rsync -e ssh -va /export/home/a078479/bob smmk39:/export/home/a078479/ ksh: rsync: not found rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) root:#> I was thorghrough in setting up rsync to be

Hi, At this stage, we're most of the way towards fully deprecating SSH protocol 1 - this outlines our plans to complete this task. We've had this old protocol in various stages of deprecation for almost 10 years and it has been compile-time disabled for about a year. Downstream vendors, to their credit, have included this change in recent OS releases by shipping OpenSSH packages that

I'm getting "Protocol errors" when trying to scp files from my laptop to my desktop (only when trying to scp root at laptop:/path/file, not vis-vis). See screen dump's at end of e-mail for exact details. The most confusing thing about this problem (to me anyway), is that this is a one-way problem. I can log into the laptop and scp files down from the desktop no problems.

I want to set up RSYNC so it has root privilege on the remote server. I do not want to run rsync through inetd. I want to be able to limit who can use rsync when the remote end has root privilege. I prefer not to use rsync's internal user/secrets file. I do want to use SSH as the transport shell. With that in mind, here is what I tried. I wrapped the rsync single use daemon execution on the

On Thu, May 21, 2015 at 1:05 AM, Michael Stone <mstone at mathom.us> wrote: > On Wed, May 20, 2015 at 03:58:22PM +0200, Stephan von Krawczynski wrote: > >> Show me this as an example of your firewall skills and replace this >> hosts.allow entry: >> >> sshd: .... : spawn (echo -e "%u@%h[%a] on `/bin/date`" to %d connected >> me | >>

Hi, We are preparing to make the release of OpenSSH 4.8 soon, so we would greatly appreciate testing of snapshot releases in as many environments and on as many operating systems as possible. The highlights of this release are: * Added chroot(2) support for sshd(8), controlled by a new option "ChrootDirectory". Please refer to sshd_config(5) for details, and please use this

OpenSSH 4.9 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. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches,

OpenSSH 4.9 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. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches,

Hi, the following patch patches the files in contrib/cygwin. The changes are necessary to allow a better support of privilege separation. On NT machines the script asks now if it should create a user called "sshd" and all that. Additionally it creates the /etc/ssh_config and /etc/sshd_config files follows the latest versions. Would you mind to apply this to the official OpenSSH

[Note to R. Wolff -- thanks for the pointers and the program. As I understand its workings, it would run as root and bind a listen port to a particular program -- with a list being supplied in /etc/portadmin or other file. Basically, a listen wrapper. Hopefully this message will address your cleanup concerns in my previous message. Thanks. Also, you may want to provide a moderator''s

OpenSSH 7.7 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. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches, reported bugs, tested

https://bugzilla.mindrot.org/show_bug.cgi?id=2513 Bug ID: 2513 Summary: Do not mention rsa1 key type in ssh-keygen usage & in manual pages Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: Linux Status: NEW Keywords: patch Severity: enhancement

Hi all! I was scanning my servers with nmap, ( i have installed ssh), and the result gave me this: 22/tcp open ssh sshv1: Server Supports SSHv1 ssh-keyhost: 1024 ea:7e:77:b7:a1:78:18:70:6c:46:ee:a0:dd:08:0e:74 (RSA1) 1024 ba:d0:8a:44:16:fc:7c:7a:38:24:2e:72:06:fe:99:56 (DSA) 1024 ff:43:15:78:98:3c:75:f9:12:36:58:92:46:6c:1c:99 (RSA) could this be a threat for intruders? i know that sshv1

https://bugs.freedesktop.org/show_bug.cgi?id=87715 Bug ID: 87715 Summary: Changing resolution away from 1680x1050 results in scattered display Product: Mesa Version: 10.4 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium