public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] Inetutils 1.9.4
Date: Sat, 13 Feb 2016 17:16:00 -0000	[thread overview]
Message-ID: <20160213171623.GA8374@calimero.vinschen.de> (raw)
In-Reply-To: <56BED384.70607@boland.nl>

[-- Attachment #1: Type: text/plain, Size: 4246 bytes --]

Hi Daniel,

On Feb 13 07:56, D. Boland wrote:
> Hi Corinna,
> 
> Corinna Vinschen wrote:
> >On Feb  7 18:55, D. Boland wrote:
> >>Some programs in the inetutils suite are packaged already:
> >>
> >>* hostname
> >>* whois
> >>* tftp
> >>* tftp-server
> >>
> >>So I added these on the 'required' lines.
> >
> >They are not actually *required* to run inetd, right?  Does it really
> >make sense to add them as require packages then?
> 
> They belong to the package. A user expects them in there and would have
> to piece the package back together. Why does it make sense to leave them
> out?

These tools are provided separately in many Linux distros for quite
some time, and while those tools can be started by inetd, inetd
doesn't require them and they don't require inetd (xinetd is perfectly
capable of replacing inetd).

> >>Also, the following include files are needed:
> >>
> >>* /usr/include/netinet/icmp6.h
> >>* /usr/include/netinet/ip_var.h
> >>
> >>There has been discussion on including the icmp6.h file in Cygwin 2.3.0.
> >
> >Can you check if icmp6.h from FreeBSD
> >https://svnweb.freebsd.org/base/head/sys/netinet/icmp6.h?revision=279531&view=co
> >does the trick when copied to /usr/include/netinet?  If so, I add this file
> >to the repo.
> 
> If I use the FreeBSD version I get:
> 
> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I..  -I../lib -I../lib -I../libinetutils
> -I../libicmp    -O2 -pipe -Wimplicit-function-declaration -MT ping6.o -MD
> -MP -MF .deps/ping6.Tpo -c -o ping6.o ping6.c
> ping6.c: In function 'ping_init':
> ping6.c:844:37: error: 'ICMP6_FILTER' undeclared (first use in this
> function)
>      setsockopt (fd, IPPROTO_ICMPV6, ICMP6_FILTER, &filter, sizeof
> (filter));

That won't work.  Ever.  Using RAW sockets requires administrator
privileges.  Apart from that, WinSock setsockopt does not at all support
settings for the IPPROTO_ICMPV6 protocol family.  That's what the
32 bit ping package

I took a (not so) quick glance over the binary packages and there are
some problems:

- etc/defaults/etc/init.src.sh has 000 perms.

- etc/defaults/etc/shells collides with the already provided file from
  the base-files package.

- usr/bin/inetutils-server-config installs inetd and syslogd in one
  go.  That's a no no.  There should be two installation scripts since
  you can't expect that a user who wants one service also wants the
  other one.  Some people would probably like to stick to the Windows
  logging, or install syslog-ng.

- Apropos syslog-ng: syslogd potentially collides with syslog-ng.
  However, instead of reusing the existing /usr/bin/syslogd-config
  script, your new scripts don't check for an existing syslog-ng
  installation at all.

- You removed the etc/defaults/etc/xinetd.d files.

- You removed the /usr/bin/iu-config file, which was specificially
  created to allow running under the cyg_server account for the known
  reasons of being able to switch the user context(*).  Your scripts
  enforce file ownership and service start under the SYSTEM account.
  That's why the csih package exists for service installation scripts to
  use for stuff like that.  Please have a look into the old
  /usr/bin/iu-config file.

- usr/bin/ping collides with the ping package.

- sbin/ifconfig is mostly non-functional since Cygwin doesn't support
  most of the functionality.  Do you really want to maintain it?

- usr/bin/traceroute is non-functional:

    $ traceroute.exe www.wdr.de
    traceroute to e2636.g.akamaiedge.net (104.90.150.230), 64 hops max
    traceroute: socket: Operation not permitted

- What also irritates me is that almost none of the patches from the
  former package made it into your version.  Did you actually check the
  patches from the current 1.9.1 source package and made sure that they
  are really not required anymore, especially concerning O_BINARY/O_TEXT
  mode, authentication, exception handling, and, generally, backward
  compatibility?


Corinna

(*) https://cygwin.com/cygwin-ug-net/ntsec.html

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-02-13 17:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 18:01 D. Boland
2016-02-08 14:04 ` Corinna Vinschen
2016-02-08 19:16   ` Achim Gratz
2016-02-13  6:59   ` D. Boland
2016-02-13 17:16     ` Corinna Vinschen [this message]
2016-02-16 16:31       ` D. Boland
2016-02-16 18:34         ` Achim Gratz
2016-02-16 19:26           ` Daniel Boland
2016-02-17 17:33         ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2015-10-31 10:33 D. Boland
2015-10-31 12:29 ` Marco Atzeri
2015-10-31 23:04   ` D. Boland
2015-11-01  8:01     ` Marco Atzeri
2015-11-01 14:21       ` D. Boland
2015-11-01 14:45         ` Marco Atzeri
2015-11-02  7:04           ` D. Boland
2015-11-02  9:56             ` Corinna Vinschen
2015-11-02  9:58               ` Corinna Vinschen
2015-11-02 14:44                 ` Corinna Vinschen
2015-12-30  7:55                   ` D. Boland
2016-01-07 10:35                     ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160213171623.GA8374@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).