Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. INN and docker default hostnames (Richard Kettlewell)
2. Re: [#6D2-CD8-83E2A] INN and docker default hostnames
(Richard Kettlewell)
3. Re: INN and docker default hostnames (Grant Taylor)
4. Re: [#6D2-CD8-83E2A] INN and docker default hostnames
(Grant Taylor)
----------------------------------------------------------------------
Message: 1
Date: Sat, 4 Apr 2020 17:24:54 +0100
From: Richard Kettlewell <[email protected]>
To: [email protected]
Subject: INN and docker default hostnames
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
In a Docker container, the hostname starts off as a random string like this:
root@e5f1e5a358ac:/# uname -n
e5f1e5a358ac
This is a perfectly cromulent hostname for the container:
root@e5f1e5a358ac:/# ping -c1 e5f1e5a358ac
PING e5f1e5a358ac (172.18.0.2) 56(84) bytes of data.
64 bytes from e5f1e5a358ac (172.18.0.2): icmp_seq=1 ttl=64 time=0.014 ms
--- e5f1e5a358ac ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.014/0.014/0.014/0.000 ms
However, INN hates it, and refuses to even install:
root@3bee77b13506:/# apt install inn2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
libgd-perl
The following NEW packages will be installed:
inn2
0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
Need to get 1200 kB of archives.
After this operation, 3443 kB of additional disk space will be used.
Get:1 https://mirror.anjou.terraraq.uk/debian buster/main amd64 inn2
amd64 2.6.3-1+deb10u2 [1200 kB]
Fetched 1200 kB in 0s (12.4 MB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package inn2.
(Reading database ... 10753 files and directories currently installed.)
Preparing to unpack .../inn2_2.6.3-1+deb10u2_amd64.deb ...
Unpacking inn2 (2.6.3-1+deb10u2) ...
Setting up inn2 (2.6.3-1+deb10u2) ...
innconfval: hostname does not resolve or domain not set in inn.conf
dpkg: error processing package inn2 (--configure):
installed inn2 package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
inn2
E: Sub-process /usr/bin/dpkg returned an error code (1)
In many contexts this can be fixed in inn.conf, but not for the specific
case of package installation, since a suitable inn.conf doesn't exist yet.
I think this is a bug in INN. The relevant code is inn_getfqdn(), which
asks getaddrinfo() to canonicalize the hostname but then for some reason
not only refuses to believe the answer, but also refuses to run even
basic tools like innconfval.
My suggestion is that INN should believe getaddrinfo(), i.e. remove the
strchr() check for '.'.
ttfn/rjk
------------------------------
Message: 2
Date: Sat, 4 Apr 2020 17:31:02 +0100
From: Richard Kettlewell <[email protected]>
To: Suporte - Portal da Queixa <[email protected]>,
[email protected]
Subject: Re: [#6D2-CD8-83E2A] INN and docker default hostnames
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
I think someone has subscribed some organization's support address to
inn-workers?
ttfn/rjk
On 04/04/2020 17:25, Suporte - Portal da Queixa wrote:
> Ol? Richard Kettlewell,
>
> Esta ? uma resposta autom?tica a confirmar a recep??o do seu pedido.
> Entraremos em contacto consigo assim que poss?vel. Quando responder, por
> favor confirme que o ID do Pedido se mant?m no assunto da mensagem para
> garantir que o seu pedido de ajuda ? devidamente registado no nosso sistema.
>
> Informamos que os dados pessoais recolhidos atrav?s do formul?rio de apoio ao
> utilizador destinam-se exclusivamente ao tratamento das quest?es colocadas,
> podendo ser necess?ria a partilha de dados pessoais com terceiros, com a
> concord?ncia do titular dos dados, caso a natureza do tratamento assim o
> exija. De acordo com o Regulamento Geral de Protec??o de Dados, poder?
> solicitar a rectifica??o e/ou elimina??o, limita??o do tratamento,
> portabilidade, ou ainda opor-se ao tratamento dos seus dados pessoais,
> atrav?s do endere?o privacidade @ portaldaqueixa.com, com direito de
> reclama??o na Comiss?o Nacional de Protec??o dos Dados. O consentimento
> prestado poder? ser retirado a qualquer momento, n?o invalidando o tratamento
> entretanto realizado.
>
> Detalhes Pedido
> -------------------------------------------
> ID Pedido: 6D2-CD8-83E2A
> Assunto: INN and docker default hostnames
> Departamento: Suporte - Portal da Queixa
> Estado: Aberto
>
> Equipa de suporte
> Centro de Ajuda | Portal da Queixa
>
------------------------------
Message: 3
Date: Sat, 4 Apr 2020 11:07:01 -0600
From: Grant Taylor <[email protected]>
To: [email protected]
Subject: Re: INN and docker default hostnames
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 4/4/20 10:24 AM, Richard Kettlewell wrote:
> In a Docker container, the hostname starts off as a random string like
> this:
>
> ? root@e5f1e5a358ac:/# uname -n
> ? e5f1e5a358ac
>
> This is a perfectly cromulent hostname for the container:
I agree with your statement, but I dislike the unqualified hostname as
is. The lack of qualification will end up causing problems, possibly
like you're experiencing now.
> However, INN hates it, and refuses to even install:
I seriously question if the failure is in INN itself or the Debian
package manager.
I bet that innconfval is working exactly like it should and that
something is not liking what innconfval is returning.
> In many contexts this can be fixed in inn.conf, but not for the specific
> case of package installation, since a suitable inn.conf doesn't exist yet.
Yet another reason to suspect the package manager vs INN itself.
> I think this is a bug in INN.
I'm not convinced that this is a bug in INN. In fact, I think this is a
bug in the installer / script that it's using.
> The relevant code is inn_getfqdn(), which asks getaddrinfo() to
> canonicalize the hostname but then for some reason not only refuses
> to believe the answer, but also refuses to run even basic tools
> like innconfval.
I suspect it's something outside of INN that's not liking what it's seeing.
> My suggestion is that INN should believe getaddrinfo(), i.e. remove the
> strchr() check for '.'.
Names without a period in them are unqualified (in the DNS world).
INN "SHOULD" (in the RFC sense of the word) have a FQDN to work with.
Much like email servers SHOULD have an FQDN.
I question if you would have any problems installing INN from source vs
the Debian package.
I also suspect that you could tweak (read: correct the qualification) of
the container's hostname and that INN would install perfectly fine.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20200404/88192b45/attachment-0001.bin>
------------------------------
Message: 4
Date: Sat, 4 Apr 2020 11:22:52 -0600
From: Grant Taylor <[email protected]>
To: [email protected]
Cc: [email protected],
[email protected]
Subject: Re: [#6D2-CD8-83E2A] INN and docker default hostnames
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 4/4/20 10:31 AM, Richard Kettlewell wrote:
> I think someone has subscribed some organization's support address to
> inn-workers?
I too got such a response.
Google Translate detected Portuguese.
"This is an automatic response to confirm receipt of your order." ?
"automatic" and "order" bother me.
"General Data Protection Regulation" ~> GDPR ? Ugh. I wonder how
effective it would be for me to try to use the GDPR, seeing as how I'm
in the U.S.A.
Perhaps a message to inn-workers moderator and the Portal da Queixa
abuse and / or postmaster addresses is in order.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20200404/7242c203/attachment.bin>
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 118, Issue 1
*******************************************
