search for: ipv64_normalise_map

Displaying 5 results from an estimated 5 matches for "ipv64_normalise_map".

2010 Sep 23
4
[Bug 1825] New: ipv64_normalise_mapped()'s memset should use a4, not addr, for clarity
https://bugzilla.mindrot.org/show_bug.cgi?id=1825 Summary: ipv64_normalise_mapped()'s memset should use a4, not addr, for clarity Product: Portable OpenSSH Version: 5.6p1 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P2 Component: Miscellaneous...
2005 Nov 21
1
[PATCH] 64 bit clean compilation patches
....c: In function `lastlog_get_entry': loginrec.c:1592: warning: int format, different type arg (arg 4) loginrec.c: In function `record_failed_login': loginrec.c:1655: warning: passing arg 3 of `getpeername' from incompatible pointer typescp.c: loginrec.c:1656: warning: passing arg 2 of `ipv64_normalise_mapped' from incompatible pointer type In function `source': scp.c:566: warning: long long int format, __off_t arg (arg 5) scp.c:566: warning: long long int format, __off_t arg (arg 5) These patches were tested on a 32-bit GNU/Linux machine with inttypes.h, 32-bit FreeBSD without inttypes.h,...
2008 Aug 21
2
IP options
I'm seeing something similar to bug 1179 (https://bugzilla.mindrot.org/show_bug.cgi?id=1179), even with the reordered IP options check. For some reason, getsockopt is returning an IP options of length 2, value 00 00. Would Mark Weindling's original patch (https://bugzilla.mindrot.org/attachment.cgi?id=1105) break anything if I incorporated it? Platform: HP NonStop S7000 series
2015 Feb 26
4
Call for testing: OpenSSH 6.8
On Thu, 26 Feb 2015, Darren Tucker wrote: > I noticed this error log spam on the tinderbox when looking at one of the > failures. It happens with Unix domain socket forwarding is requested: > > debug1: channel 1: new [forwarded-streamlocal at openssh.com] > get_socket_address: getnameinfo 1 failed: ai_family not supported > get_sock_port: getnameinfo NI_NUMERICSERV failed:
2005 Nov 17
2
AllowUsers not working under certain conditions
Hello, I've trawled archives looking for changes in the "AllowUsers" option, manuals, changes log, reported bugs and to my surprise I can't find anything or anyone that has reported the issues that I am experiencing. I am using the default installation sshd_config file as supplied by Redhat and the only options I have changed are: ListenAddress AllowUsers The first problem