similar to: OpenSSH 3.6 released (fwd)

Hello. I've got a question about encoding in sshd's log files. When I try to log in with a "?" username, which is a cyrillic "h" (U+0445), I get this message in a logfile: input_userauth_request: invalid user \\321\\205 [preauth]. I am struggling to understand: is that hex, is that octal? It doesn't map to any encoding that I know of.

Hi, Today I fiddled around a bit with my OpenSSH public key files, and I noticed that ssh-keygen prints most non-printable characters in the comment as-is when showing the fingerprint of a key. This can lead to confusing output on the terminal when the comment contains ANSI escape characters which are interpreted by the terminal. The attached public key file serves as an example, which, when

Hi When NetBSD added strnvis they swapped around the argument order. On OpenBSD: int strnvis(char *, const char *, size_t, int) On NetBSD: int strnvis(char *, size_t, const char *, int); Don't ask me why. On Thu, Jan 23, 2014 at 12:56:48PM +1100, Darren Tucker wrote: > On Thu, Jan 23, 2014 at 12:13 PM, Hisashi T Fujinaka <htodd at twofifty.com> wrote: > > #1

Hello, The banner message displayed on the screen contain octal values instead of korean chars. Prior to ssh 5.1 the banner message would display the charaters properly. I understand that starting from 5.1 the message is passed through strnvis() function. I looked into documentation on strnvis and found that it does not support multibyte chars and doesnt work well with international chars.

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

I was progressively upgrading this phone from 3.1.2 to 3.2.3, then to 4.0.0. v3.2.3 worked fine, but when I went to 4.0.0 (Even adding the more specific 2345-11500-040.bootrom.ld), it won't run, and just keeps rebooting. Now I've got a really nice doorstop unless someone knows how to get out of this predicament. Help! 0925003705|cfg |3|00|Beginning to provision phone 0925003705|dns

https://bugzilla.mindrot.org/show_bug.cgi?id=1496 Summary: ssh fails with xmalloc: zero size Classification: Unclassified Product: Portable OpenSSH Version: 5.1p1 Platform: Other OS/Version: Linux Status: NEW Keywords: patch Severity: normal Priority: P2 Component: ssh AssignedTo:

Hi, Sorry to bother you on this mailing list, however I tried everything else and I am desperate to get this running. Please send me any hints you can think of. I have installed openssh-3.7.1p2 on a ppc target and trying to connect to an sshd running on a redhat 9 with openssh-3.5p1. I keep getting the error "Disconnecting: Corrupted check bytes on input" no matter what I tried. I

Hi, According to IETF draft draft-ietf-secsh-transport-14.txt, different ciphers(encryption), MAC and compression can be used for one direction say server-to-client and a completely different cipher, MAC and compression for the other direction client-to-server of the same connection. Is this supported today in OpenSSH, and if not, are there plans to support it in any future releases of the code?

http://bugzilla.mindrot.org/show_bug.cgi?id=692 Summary: Can't make OpenSSH-3.7.1p1 on OpenBSD 3.0 Product: Portable OpenSSH Version: 3.7.1p1 Platform: ix86 OS/Version: OpenBSD Status: NEW Severity: critical Priority: P2 Component: Build system AssignedTo: openssh-bugs at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=692 Summary: Can't make OpenSSH-3.7.1p1 on OpenBSD 3.0 Product: Portable OpenSSH Version: 3.7.1p1 Platform: ix86 OS/Version: OpenBSD Status: NEW Severity: critical Priority: P2 Component: Build system AssignedTo: openssh-bugs at mindrot.org

Hello, I used the SecureShell windows client from ssh.com and it have a cool feature: Once I logged on a server with ssh, I was able to create more terminals without being asked for a password again. It seems that it use the 'same channel' created from the first ssh client. So, it's possible with openssh on linux/bsd? If yes, how? If not, can you add this feature? Why I ask taht?

Ok.. I'm starting official testing calls early this release. I'd like to have more feedback and more time for handling fixes. If people could test snapshots (http://www.openssh.org/portable.html, pick your favorate mirror and select snapshots directory) and report failures it would be useful. For those with pmake install there is regress/ which you can try out. It may help any platform

Hi, OpenSSH 7.4 is almost ready for release, so we would appreciate testing on as many platforms and systems as possible. This release contains some substantial new features and a number of bugfixes. Snapshot releases for portable OpenSSH are available from http://www.mindrot.org/openssh_snap/ The OpenBSD version is available in CVS HEAD: http://www.openbsd.org/anoncvs.html Portable OpenSSH is

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

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

Greetings. Attached is a patch that provides more logging information for example: Mar 19 08:34:54 secosr5 sshd[7667]: Accepted publickey of? vix at wormhole for root from 192.168.1.1 port 1256 ssh2 Mar 19 08:34:54 secosr5 sshd[7667]: executing command 'who' for? vix at wormhole as user root Mar 19 10:37:16 secosr5 sshd[7725]: Accepted publickey of? vix at wormhole for root from

IRIX 6.5 has the basename() function in libgen. SYNOPSIS cc [flag ...] file ... -lgen [library ...] #include <libgen.h> char *basename (char *path); -- ayamura

https://bugzilla.mindrot.org/show_bug.cgi?id=2058 Bug ID: 2058 Summary: SSH Banner message displays UTF-8 multibyte char incorrrectly Classification: Unclassified Product: Portable OpenSSH Version: 6.1p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5