[opensuse-factory] libwrap still broken over 2 years later...
Just rebooted (it had been 60 days since last reboot), and it picked up the new tcpd/libwrap0 files from 13.1 (am pretty sure it's not fixed in factory, given it hasn't been fixed in over 2 years)... This is still a problem: http://lists.opensuse.org/opensuse/2011-10/msg00351.html Thought it was reported as I have a patch file... making sure it is reported here: https://bugzilla.novell.com/show_bug.cgi?id=861989 (had problems w/attachment, so am including it here as well..).
On Monday 03 February 2014 19.37:03 Linda Walsh wrote:
Just rebooted (it had been 60 days since last reboot), and it picked up the new tcpd/libwrap0 files from 13.1 (am pretty sure it's not fixed in factory, given it hasn't been fixed in over 2 years)...
This is still a problem:
http://lists.opensuse.org/opensuse/2011-10/msg00351.html
Thought it was reported as I have a patch file... making sure it is reported here:
https://bugzilla.novell.com/show_bug.cgi?id=861989
(had problems w/attachment, so am including it here as well..).
Linda what about branching this one on obs, fix it, and then submit it back ? -- Bruno Friedmann openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bruno Friedmann wrote:
On Monday 03 February 2014 19.37:03 Linda Walsh wrote:
Just rebooted (it had been 60 days since last reboot), and it picked up the new tcpd/libwrap0 files from 13.1 (am pretty sure it's not fixed in factory, given it hasn't been fixed in over 2 years)...
This is still a problem:
http://lists.opensuse.org/opensuse/2011-10/msg00351.html
Thought it was reported as I have a patch file... making sure it is reported here:
https://bugzilla.novell.com/show_bug.cgi?id=861989
(had problems w/attachment, so am including it here as well..).
Linda what about branching this one on obs, fix it, and then submit it back ?
I wasn't able to login on obs last time I tried. I mentioned it several times and no one was able to fix it. At the time, I had done my initial attempt at using OBS via 'ssh' instead of initializing it through the website. The process of initializing it through ssh hadn't been well tested and was broken (it was expected one would sign up through the website first). Supposedly the initialization process was fixed, but I was never able to login -- I think because my space had been corrupted by the broken process and no one was inclined to fix it. Needless to say, more than once since then opportunities have arisen for me to submit some fix or another and this suggestion has been made, -- but no one seems to know or those who know are not inclined to fix it... (Just saw this response today -- as it was just sent to the list and I was not in the "To or Cc list, so it didn't flag'ed as directed to me and went into the list email box). Note the opensuse kernel list will actually reject your email if you don't put it in the To or the Cc list. I don't reflect them as they get stored in the list email, but w/o some indication it was directed to me, I may not see it. Sad to say, but this is exactly whey the standard said to send it to both the poster and the list. But some people know better and have jumped all over people who follow the standards resulting in missed email. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On March 30, 2014 11:52:44 PM EDT, Linda Walsh <suse@tlinx.org> wrote:
Bruno Friedmann wrote:
On Monday 03 February 2014 19.37:03 Linda Walsh wrote:
Linda what about branching this one on obs, fix it, and then submit it back ?
I wasn't able to login on obs last time I tried.
I mentioned it several times and no one was able to fix it.
At the time, I had done my initial attempt at using OBS via 'ssh' instead of initializing it through the website.
Linda, if you have a broken home project, why don't you post to the opensuse-buildservice list and ask to have it deleted. Then it should 're-create for you fine via your first web login. The key thing is -factory is not a support list for OBS. OBS is the foundation of opensuse these days, so not having a working OBS home project restricts you. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 06/02/14 04:44, Bruno Friedmann escribió:
On Monday 03 February 2014 19.37:03 Linda Walsh wrote:
Just rebooted (it had been 60 days since last reboot), and it picked up the new tcpd/libwrap0 files from 13.1 (am pretty sure it's not fixed in factory, given it hasn't been fixed in over 2 years)...
This is still a problem:
http://lists.opensuse.org/opensuse/2011-10/msg00351.html
Thought it was reported as I have a patch file... making sure it is reported here:
https://bugzilla.novell.com/show_bug.cgi?id=861989
(had problems w/attachment, so am including it here as well..).
Linda what about branching this one on obs, fix it, and then submit it back ?
This whole thing has to be dropped from the distribution anyway as it is unmaintained. (arch did years ago, fedora will do soon as well) In the current century we have this cool things called firewalls, which are the proper place where you should determine if connections to a tcp service are accepted or not, then it is enforced by the kernel, the only place where it should be. Also several daemons by now have some form of builtin access control, use that too. For now I managed to get tcpwrapper support dropped from systemd upstream, as using with this ancient ruin in systemd was crazy. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Bruno Friedmann
-
Cristian Rodríguez
-
Greg Freemyer
-
Linda Walsh