Bug 1069029 - lighttpd default configuration generates scary warnings
Summary: lighttpd default configuration generates scary warnings
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lighttpd
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-24 01:35 UTC by Michal Jaegermann
Modified: 2020-05-13 05:12 UTC (History)
3 users (show)

Fixed In Version: lighttpd-1.4.55-2.fc31 lighttpd-1.4.55-2.fc32 lighttpd-1.4.55-2.fc30 lighttpd-1.4.55-2.el8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-06 03:07:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michal Jaegermann 2014-02-24 01:35:49 UTC
Description of problem:

After starting lighttpd one can see something like that when checking status:

(network.c.285) warning: please use server.use-ipv6 only for hostnames, not without server.bind / empty address; your config will break if the kernel default for IPV6_V6ONLY changes

This warning is also repeated at http://redmine.lighttpd.net/projects/lighttpd/wiki/Server_use-ipv6Details

Actually currently this works but in case some kernel update would change a default in question it would silently break.  Setting server.bind without other changes results in a server which listens on IPv6 addresses only (and that is expected- see below).

Version-Release number of selected component (if applicable):
lighttpd-1.4.34-3.fc20

Additional info:

As a matter of fact "Recommended IPv6 setup" at given at http://redmine.lighttpd.net/projects/lighttpd/wiki/IPv6-Config#Changes-in-1427 is quite a bit different and that listens both on IPv4 and IPv6.

Comment 1 Fedora End Of Life 2015-05-29 11:02:01 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 19:03:21 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Conrad Meyer 2018-06-07 22:02:30 UTC
It seems kernel ipv6-v6only default has changed since Fedora 20, and now the server.use-ipv6="enable" lighttpd default config has resulted in an httpd that only listens on v6 by default.

Comment 4 Ben Cotton 2018-11-27 15:13:19 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2018-11-30 21:57:44 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 teppot 2020-04-27 15:33:02 UTC
Still occurs on Fedora 32. Please reopen.

Comment 7 Fedora Update System 2020-04-27 16:25:16 UTC
FEDORA-2020-62cfcd6cdc has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-62cfcd6cdc

Comment 8 Fedora Update System 2020-04-27 16:25:18 UTC
FEDORA-2020-d87da37c73 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-d87da37c73

Comment 9 Fedora Update System 2020-04-27 16:25:19 UTC
FEDORA-2020-eff20fe230 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-eff20fe230

Comment 10 Fedora Update System 2020-04-27 16:25:19 UTC
FEDORA-EPEL-2020-9b5022962c has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-9b5022962c

Comment 11 Fedora Update System 2020-04-28 03:23:58 UTC
FEDORA-2020-eff20fe230 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-eff20fe230`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-eff20fe230

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2020-04-28 03:46:07 UTC
FEDORA-2020-62cfcd6cdc has been pushed to the Fedora 30 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-62cfcd6cdc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-62cfcd6cdc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2020-04-28 03:52:11 UTC
FEDORA-2020-d87da37c73 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-d87da37c73`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d87da37c73

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2020-04-28 06:20:46 UTC
FEDORA-EPEL-2020-9b5022962c has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-9b5022962c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 15 Fedora Update System 2020-05-06 03:07:37 UTC
FEDORA-2020-d87da37c73 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2020-05-06 04:29:49 UTC
FEDORA-2020-eff20fe230 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2020-05-06 05:07:40 UTC
FEDORA-2020-62cfcd6cdc has been pushed to the Fedora 30 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 18 Fedora Update System 2020-05-13 05:12:38 UTC
FEDORA-EPEL-2020-9b5022962c has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.