Displaying 6 results from an estimated 6 matches for "vis_oct".
Did you mean:
vis_octal
2003 Sep 19
2
[Bug 692] Can't make OpenSSH-3.7.1p1 on OpenBSD 3.0
...with message:
log.c: In function `do_log':
log.c:393: warning: implicit declaration of function `strnvis'
log.c:393: `VIS_SAFE' undeclared (first use in this function)
log.c:393: (Each undeclared identifier is reported only once
log.c:393: for each function it appears in.)
log.c:393: `VIS_OCTAL' undeclared (first use in this function)
*** Error code 1
I found both "VIS_SAFE" and "VIS_OCTAL" in /usr/include:
cd /usr/include
grep VIS_SAFE *.h
vis.h:#define VIS_SAFE 0x20 /* only encode "unsafe" characters */
grep VIS_OCTAL *.h
vis.h:#define...
2003 Sep 19
2
[Bug 692] Can't make OpenSSH-3.7.1p1 on OpenBSD 3.0
...with message:
log.c: In function `do_log':
log.c:393: warning: implicit declaration of function `strnvis'
log.c:393: `VIS_SAFE' undeclared (first use in this function)
log.c:393: (Each undeclared identifier is reported only once
log.c:393: for each function it appears in.)
log.c:393: `VIS_OCTAL' undeclared (first use in this function)
*** Error code 1
I found both "VIS_SAFE" and "VIS_OCTAL" in /usr/include:
cd /usr/include
grep VIS_SAFE *.h
vis.h:#define VIS_SAFE 0x20 /* only encode "unsafe" characters */
grep VIS_OCTAL *.h
vis.h:#define...
2017 Feb 13
3
Logfile encoding question
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.
2003 Mar 31
1
OpenSSH 3.6 released (fwd)
-------------- 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
2016 Jan 02
3
ssh-keygen: sanitize ANSI escape sequences in key comment
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
2003 Oct 08
4
OS/390 openssh
...nst char *ipaddr, int port)
+{
+ char buf[1024];
+ char cmd[1024];
+ bs2cmd_rc rc;
+ int flags = BS2CMD_FLAG_STRIP;
+
+ snprintf(buf, sizeof buf, "/TYPE %% OPENSSH %s '%s' FROM '[%s]:%d'",
+ reason, user, ipaddr, port);
+ strnvis(cmd, buf, sizeof(buf), VIS_SAFE|VIS_OCTAL);
+ (void) bs2cmd(cmd, &rc, BS2CMD_DEFAULT, flags);
+}
+#endif
diff -bur openssh-3.7.1p2.orig/auth-passwd.c openssh-3.7.1p2/auth-passwd.c
--- openssh-3.7.1p2.orig/auth-passwd.c Thu Sep 18 10:26:48 2003
+++ openssh-3.7.1p2/auth-passwd.c Tue Oct 7 08:21:59 2003
@@ -50,6 +50,18 @@
extern Se...