Displaying 20 results from an estimated 5000 matches similar to: "[Bug 2483] New: use AI_ADDRCONFIG flag for getaddrinfo() hints on Solaris"
2017 Jan 29
2
[PATCH tftpd-hpa] tftpd: don't use AI_CANONNAME and AI_ADDRCONFIG to resolve addresses for bind
AI_CANONNAME is only relevant when the resulting official name is used,
which is not the case in tftpd for the address to bind to. Also
AI_ADDRCONFIG isn't helpful. This flag is good for sockets used to
connect(2) somewhere. But for listening sockets it makes tftpd fail to
start when -a 0.0.0.0:69 is passed and no network device is up yet.
This addresses Debian bug
2017 Feb 02
2
Bug#771441: [PATCH tftpd-hpa] tftpd: don't use AI_CANONNAME and AI_ADDRCONFIG to resolve addresses for bind
Hello Ron,
On Thu, Feb 02, 2017 at 04:08:49PM +1030, Ron via Syslinux wrote:
> On Sun, Jan 29, 2017 at 12:09:43PM +0100, Uwe Kleine-K?nig wrote:
> > AI_CANONNAME is only relevant when the resulting official name is used,
> > which is not the case in tftpd for the address to bind to. Also
> > AI_ADDRCONFIG isn't helpful. This flag is good for sockets used to
> >
2017 Feb 05
2
tftpd: don't use AI_ADDRCONFIG to resolve addresses to bind(2)
Hello Ron,
On Sun, Feb 05, 2017 at 05:05:16PM +1030, Ron wrote:
> On Sat, Feb 04, 2017 at 11:28:08PM +0100, Uwe Kleine-K?nig wrote:
> > On Sat, Feb 04, 2017 at 03:46:46PM +1030, Ron wrote:
> > > > [...]
> > > That would seem to be a pretty good summation of how we're failing to
> > > converge here ...
> >
> > I mixed too many things that
2017 Feb 03
2
Bug#771441: [PATCH tftpd-hpa] tftpd: don't use AI_CANONNAME and AI_ADDRCONFIG to resolve addresses for bind
On Fri, Feb 03, 2017 at 03:40:32PM +1030, Ron wrote:
> On Thu, Feb 02, 2017 at 02:22:47PM +0100, Uwe Kleine-K?nig wrote:
> > On Thu, Feb 02, 2017 at 04:08:49PM +1030, Ron via Syslinux wrote:
> >
> > > The use of AI_PASSIVE here is a placebo. That flag has no effect unless
> > > address was NULL, and if that was true, neither of the hunks here would
> > >
2017 Feb 04
2
tftpd: don't use AI_ADDRCONFIG to resolve addresses to bind(2)
Hello Ron,
On Sat, Feb 04, 2017 at 03:46:46PM +1030, Ron wrote:
> > [...]
> That would seem to be a pretty good summation of how we're failing to
> converge here ...
I mixed too many things that IMHO improve the code but actually only
care about one of those. So I suggest we restart the discussion with
focusing on that one thing only. Let me try that:
Currently tftpd when
2017 Feb 02
0
Bug#771441: [PATCH tftpd-hpa] tftpd: don't use AI_CANONNAME and AI_ADDRCONFIG to resolve addresses for bind
On Sun, Jan 29, 2017 at 12:09:43PM +0100, Uwe Kleine-K?nig wrote:
> AI_CANONNAME is only relevant when the resulting official name is used,
> which is not the case in tftpd for the address to bind to. Also
> AI_ADDRCONFIG isn't helpful. This flag is good for sockets used to
> connect(2) somewhere. But for listening sockets it makes tftpd fail to
> start when -a 0.0.0.0:69 is
2017 Feb 14
0
tftpd: don't use AI_ADDRCONFIG to resolve addresses to bind(2)
Okay, let me chime in here.
AI_ADDRCONFIG seems to be the Wrong Thing[TM].
AI_PASSIVE seems to be the Right Thing[TM].
Part of the problem is that the fallback code for the case of
getaddrinfo() not being there is braindead, and of course the original
code used to use gethostbyname() directly. I already have a much better
fallback version of getaddrinfo() written which would let us make much
2017 Feb 03
0
Bug#771441: [PATCH tftpd-hpa] tftpd: don't use AI_CANONNAME and AI_ADDRCONFIG to resolve addresses for bind
On Thu, Feb 02, 2017 at 02:22:47PM +0100, Uwe Kleine-K?nig wrote:
> On Thu, Feb 02, 2017 at 04:08:49PM +1030, Ron via Syslinux wrote:
>
> > The use of AI_PASSIVE here is a placebo. That flag has no effect unless
> > address was NULL, and if that was true, neither of the hunks here would
> > actually be executed in the first place.
>
> Right. Today it only has an
2013 Jul 31
3
[Bug 2135] New: Solaris: race condition in channel forwarding when connect() returns EINPROGRESS
https://bugzilla.mindrot.org/show_bug.cgi?id=2135
Bug ID: 2135
Summary: Solaris: race condition in channel forwarding when
connect() returns EINPROGRESS
Product: Portable OpenSSH
Version: 6.0p1
Hardware: All
OS: Solaris
Status: NEW
Severity: normal
Priority: P5
2007 Jan 23
2
Re: [nut-commits] svn commit r731
Hi Arjen,
in server/upsd.c r731, you moved the call conf_load() from after
check_perms() (~ l.1020) to before setupsignals() (~ l.989).
The problem is that conf_load() needs to open the ups driver socket,
and it assumes that STATEPATH is the current working directory. The
directory is only set in l.1016. Therefore, the first attempt to open
a socket will always fail. From the user's point of
2017 Feb 05
0
tftpd: don't use AI_ADDRCONFIG to resolve addresses to bind(2)
On Sat, Feb 04, 2017 at 11:28:08PM +0100, Uwe Kleine-K?nig wrote:
> On Sat, Feb 04, 2017 at 03:46:46PM +1030, Ron wrote:
> > > [...]
> > That would seem to be a pretty good summation of how we're failing to
> > converge here ...
>
> I mixed too many things that IMHO improve the code but actually only
> care about one of those. So I suggest we restart the
2007 Jan 06
3
Re: [nut-commits] svn commit r708 - in trunk: . clients server
With the Ipv6 patch (r708), I get:
upsclient.c: In function `upscli_connect':
upsclient.c:469: `AI_ADDRCONFIG' undeclared (first use in this function)
upsclient.c:469: (Each undeclared identifier is reported only once
upsclient.c:469: for each function it appears in.)
Even if it doesn't break IPv4 support, it may break portability, as
IPv6 seems to require specific functions that are
2017 Feb 04
0
Bug#771441: tftpd: don't use AI_CANONNAME and AI_ADDRCONFIG to resolve addresses for bind
On Fri, Feb 03, 2017 at 10:19:06AM +0100, Uwe Kleine-K?nig wrote:
> On Fri, Feb 03, 2017 at 03:40:32PM +1030, Ron wrote:
> > On Thu, Feb 02, 2017 at 02:22:47PM +0100, Uwe Kleine-K?nig wrote:
> > > On Thu, Feb 02, 2017 at 04:08:49PM +1030, Ron via Syslinux wrote:
> > >
> > > > The use of AI_PASSIVE here is a placebo. That flag has no effect unless
> >
2004 May 02
2
[Bug 859] getaddrinfo(host, "0", &hints, &res) may take extra cycles
http://bugzilla.mindrot.org/show_bug.cgi?id=859
Summary: getaddrinfo(host, "0", &hints, &res) may take extra
cycles
Product: Portable OpenSSH
Version: 3.8p1
Platform: All
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Miscellaneous
2008 Jun 11
1
[Bug 859] getaddrinfo(host, "0", &hints, &res) may take extra cycles
https://bugzilla.mindrot.org/show_bug.cgi?id=859
Darren Tucker <dtucker at zip.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dtucker at zip.com.au
Blocks| |1452
--- Comment #4 from Darren Tucker
2005 Mar 07
1
[Bug 859] getaddrinfo(host, "0", &hints, &res) may take extra cycles
http://bugzilla.mindrot.org/show_bug.cgi?id=859
dtucker at zip.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO|914 |994
nThis| |
------- Additional Comments From dtucker at zip.com.au 2005-03-07 16:12
2016 Dec 13
0
remotetcp_chert
On Thu, Dec 08, 2016 at 10:08:40PM +0000, Eric Lindblad wrote:
> Dear Olly Betts,
>
> same 32 bit
>
> compiler version
> hardware
> OS
> OS version
>
> as here (where remotetcp_chert passed and skipped 3)
>
> xapian-core-1.2.21.tar.xz
>
> http://nurmi-labs.blogspot.com/2015/10/xapian.html
That's over a year old - are you really running the exact
2016 Dec 08
2
remotetcp_chert
Dear Olly Betts,
same 32 bit
compiler version
hardware
OS
OS version
as here (where remotetcp_chert passed and skipped 3)
xapian-core-1.2.21.tar.xz
http://nurmi-labs.blogspot.com/2015/10/xapian.html
./apitest backend remoteprog_brass: All 225 tests passed, 3 skipped.
./apitest backend remotetcp_brass: All 225 tests passed, 3 skipped.
./apitest backend remoteprog_chert: All 225 tests passed,
2016 Nov 09
7
[Bug 2636] New: Fix X11 forwarding, when ::1 is not configured
https://bugzilla.mindrot.org/show_bug.cgi?id=2636
Bug ID: 2636
Summary: Fix X11 forwarding, when ::1 is not configured
Product: Portable OpenSSH
Version: 7.3p1
Hardware: Sparc
OS: Solaris
Status: NEW
Severity: minor
Priority: P5
Component: sshd
Assignee: unassigned-bugs at
2014 Jul 08
2
[PATCH] Support for ASEM UPS on Linux/i2c
On 08/07/2014 01:02, Charles Lepple wrote:
>>> Sorry I did not test this sooner - this went to Gmane but not to my email.
>>> If you have time, could you please write up a quick man page for this driver?
>>>
>>> Also, there seem to be some missing symbols and include files:
>>>
>>>