Hello,
iptables-1.4.5-1 just made it into rawhide. This new version supports
all new features of the 2.6.31 kernel and contains two additional fixes
for leaked file descriptors:
- new version 1.4.5 with support for all new features of 2.6.31
- libxt_NFQUEUE: add new v1 version with
Jud Craft wrote:
On Mon, Jun 15, 2009 at 4:52 AM, Thomas Woernertwoer...@redhat.com wrote:
The major problem with a /etc/iptables.d direcory with files provided by
packages are that you can not say in the end what your firewall will look
like: Is the firewall is open for a specific
Lennart Poettering wrote:
On Mon, 15.06.09 12:41, Thomas Woerner (twoer...@redhat.com) wrote:
So, what should happen here? Should we leave the firewall enabled in
these cases* by default and require admins to open them? If so, is
there any way that we can make this easier in some
Packagekit
Roberto Ragusa wrote:
Thomas Woerner wrote:
Please think of a scenario like this: Service A is adding
firewall rules for opening port 20 and 21 (ftp-data and ftp) for
everyone and service B is opening port 20 and 21 only for a specific
network segment. What do you want to have here? If you
Kevin Fenzi wrote:
On Sun, 14 Jun 2009 18:34:52 +0100
Matthew Garrett m...@redhat.com wrote:
On Sun, Jun 14, 2009 at 06:13:51PM +0200, Julian Aloofi wrote:
So, solving this is pretty easy, even for newbies. But I agree that
the error message will not help someone without advanced knowledge.
Lennart Poettering wrote:
On Sun, 14.06.09 18:34, Matthew Garrett (m...@redhat.com) wrote:
So, solving this is pretty easy, even for newbies. But I agree that the
error message will not help someone without advanced knowledge. Although
I think people running Samba generally will know where to
Matthew Garrett wrote:
On Sun, Jun 14, 2009 at 06:13:51PM +0200, Julian Aloofi wrote:
So, solving this is pretty easy, even for newbies. But I agree that the
error message will not help someone without advanced knowledge. Although
I think people running Samba generally will know where to look
Nathan Huang wrote:
Hi guys
who can help me with opening 80 port for apache in iptables, I want to
access my apache server from remote computer, but I failed in config
iptables with 80 port.
First step:
echo '-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport
80 -j ACCEPT'
Nathan Huang wrote:
Hi guys
who can help me with opening 80 port for apache in iptables, I want to
access my apache server from remote computer, but I failed in config
iptables with 80 port.
First step:
echo '-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport
80 -j ACCEPT'
.
-
* Wed Mar 22 2006 Thomas Woerner [EMAIL PROTECTED] 8.13.6-0.FC5.1
- new version 8.13.6 (fixes VU#834865)
- dropped libmilter-sigwait patch (fixed in 8.13.6)
-
This update can be downloaded from:
http
.
-
* Wed Mar 22 2006 Thomas Woerner [EMAIL PROTECTED] 8.13.6-0.FC4.1
- new version 8.13.6 (fixes VU#834865)
- dropped libmilter-sigwait patch (fixed in 8.13.6)
- fixed selinuxenabled path in initscript
- appended 'dnl' to cert tags in sendmail.mc
- fixed email address
with the SGI IRIX tool of the same name.
-
* Tue Dec 6 2005 Thomas Woerner [EMAIL PROTECTED] 2.4.24-1.FC4.1
- using Fedora Core devel package:
- spec file cleanup
- mark po files as lang specific
* Sun Nov 6 2005 Florian La Roche
: 1.FC4.2
Summary : Access control list utilities.
Description :
This package contains the getfacl and setfacl utilities needed for
manipulating access control lists.
-
* Tue Dec 6 2005 Thomas Woerner [EMAIL
.
-
* Fri Sep 2 2005 Thomas Woerner [EMAIL PROTECTED] 2.2.3-10.FC3.1
- fixed mrm initialization error in MrmOpenHierarchyPerDisplay (#167094)
Thanks to Arjan van de Ven for the patch
14 matches
Mail list logo
