This is the mail archive of the
mailing list for the Cygwin project.
Re: [ITP] tftp-hpa 5.0
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 15 Nov 2010 10:37:49 -0500
- Subject: Re: [ITP] tftp-hpa 5.0
- References: <4CA42DB5.email@example.com> <4CA4406D.firstname.lastname@example.org> <4CA5F18E.email@example.com> <4CA6029A.firstname.lastname@example.org> <4CA98F44.email@example.com> <4CA9F1B4.firstname.lastname@example.org> <4CA9FE05.email@example.com> <4CB4A904.firstname.lastname@example.org> <4CDD621C.email@example.com> <4CDE1676.firstname.lastname@example.org> <4CE1294A.email@example.com>
- Reply-to: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
On 11/15/2010 7:36 AM, Gernot Hillier wrote:
> It seems that XP64 really behaves like NTServer2003 in the sense that
> LocalSystem cannot change user: I can start the so-created service, but
> when trying to connect, it fails on fork as expected with "tftpd: PID
> xxxx: cannot drop privileges: Permission denied." in the Event log.
Thanks for verifying.
>> If it *doesn't* work, then...well, The Right Thing To Do is to fix
>> is_nt2003 as described above, and then change all the tests for "gee I
>> need a special privileged user" to
>> if is_nt2003 || is_xp64
>> but that would create a LOT of ripple: every client of csih (cron, exim,
>> openssh, inetutils, etc etc) is probably already using is_nt2003 for the
>> same reason and they'd all need to change. So...I think I'd just
>> declare victory, leave is_nt2003 alone (and wrong), but update the messages.
> Yes, this seems to be the way to go.
> Perhaps you could also add some additional comment in front of is_nt2003
> explaining the situation?
See my reply to Corinna in this thread.