Bug#376236: gFTP bookmarks
Package: gFTP Version: 2.0.18 gFTP supports connections over SSH2, but the connection type will not be stored in bookmarks. When you store a connection as a bookmark, the connection type will be allways FTP. And there is no way to change the connection type before connecting to the server by using bookmarks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360448: iptables damages mac rules with kernel-image-2.4.27-3-k7
It is the same bug report, because I didn't kow the exact package for the report. I had never the same problem with iptables before too. I am using the same packet filter script since a couple of years. But now there is a new computer with a new mac adress, and everything goes down. Could it be a buffer overflow or a wrong handled pointer? C is very known for errors like this. Best regards, Hansgeorg Schwibbe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360449: iptables damages mac rules with kernel-image-2.4.27-3-k7
Package: iptables Version: 1.2.11 Severity: grave I am using my own iptables script where I execute the following iptables commands on startup: iptables -A INPUT -m mac --mac-source 00:20:ED:39:91:E7 -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:20:ED:39:91:E7 -p udp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:12:3F:D6:89:8A -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:12:3F:D6:89:8A -p udp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:13:D3:FD:20:FA -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:13:D3:FD:20:FA -p udp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:14:38:00:AB:A6 -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:14:38:00:AB:A6 -p udp --dport 3128:3130 -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:20:ED:39:91:E7 -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:12:3F:D6:89:8A -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:13:D3:FD:20:FA -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:14:38:00:AB:A6 -j ACCEPT When the server is up, the mac rules are correct like this: debian:~# iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT tcp -- anywhere anywhereMAC 00:20:ED:39:91:E7 tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:20:ED:39:91:E7 udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:12:3F:D6:89:8A tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:12:3F:D6:89:8A udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:13:D3:FD:20:FA tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:13:D3:FD:20:FA udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:14:38:00:AB:A6 tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:14:38:00:AB:A6 udp dpts:3128:icpv2 Chain FORWARD (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhereMAC 00:20:ED:39:91:E7 ACCEPT all -- anywhere anywhereMAC 00:12:3F:D6:89:8A ACCEPT all -- anywhere anywhereMAC 00:13:D3:FD:20:FA ACCEPT all -- anywhere anywhereMAC 00:14:38:00:AB:A6 But after some up time the mac rules are morphing like this: debian:~# iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT tcp -- anywhere anywhereMAC 00:20:ED:39:91:E7 tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:20:ED:39:91:E7 udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:05:5D:F5:E8:FF tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:05:5D:F5:E8:FF udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:05:5D:F6:10:BD tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:05:5D:F6:10:BD tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:12:3F:D6:89:8A tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:12:3F:D6:89:8A tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:14:38:00:AB:A6 tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:14:38:00:AB:A6 tcp dpts:3128:icpv2 Chain FORWARD (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhereMAC 00:20:ED:39:91:E7 ACCEPT all -- anywhere anywhereMAC 00:05:5D:F5:E8:FF ACCEPT all -- anywhere anywhereMAC 00:05:5D:F6:10:BD ACCEPT all -- anywhere anywhereMAC 00:12:3F:D6:89:8A ACCEPT all -- anywhere anywhereMAC 00:14:38:00:AB:A6 Now is the computer with the mac address 00:13:D3:FD:20:FA unable to access the squid proxy server on port 3128 because the mac adress is completly missing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360448: iptables damages mac rules with kernel-image-2.4.27-3-k7
Package: kernel-image-2.4.27-3-k7 Version: 2.4 Severity: grave I am using my own iptables script where I execute the following iptables commands on startup: iptables -A INPUT -m mac --mac-source 00:20:ED:39:91:E7 -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:20:ED:39:91:E7 -p udp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:12:3F:D6:89:8A -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:12:3F:D6:89:8A -p udp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:13:D3:FD:20:FA -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:13:D3:FD:20:FA -p udp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:14:38:00:AB:A6 -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:14:38:00:AB:A6 -p udp --dport 3128:3130 -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:20:ED:39:91:E7 -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:12:3F:D6:89:8A -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:13:D3:FD:20:FA -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:14:38:00:AB:A6 -j ACCEPT When the server is up, the mac rules are correct like this: debian:~# iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT tcp -- anywhere anywhereMAC 00:20:ED:39:91:E7 tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:20:ED:39:91:E7 udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:12:3F:D6:89:8A tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:12:3F:D6:89:8A udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:13:D3:FD:20:FA tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:13:D3:FD:20:FA udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:14:38:00:AB:A6 tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:14:38:00:AB:A6 udp dpts:3128:icpv2 Chain FORWARD (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhereMAC 00:20:ED:39:91:E7 ACCEPT all -- anywhere anywhereMAC 00:12:3F:D6:89:8A ACCEPT all -- anywhere anywhereMAC 00:13:D3:FD:20:FA ACCEPT all -- anywhere anywhereMAC 00:14:38:00:AB:A6 But after some up time the mac rules are morphing like this: debian:~# iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT tcp -- anywhere anywhereMAC 00:20:ED:39:91:E7 tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:20:ED:39:91:E7 udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:05:5D:F5:E8:FF tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:05:5D:F5:E8:FF udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:05:5D:F6:10:BD tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:05:5D:F6:10:BD tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:12:3F:D6:89:8A tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:12:3F:D6:89:8A tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:14:38:00:AB:A6 tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:14:38:00:AB:A6 tcp dpts:3128:icpv2 Chain FORWARD (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhereMAC 00:20:ED:39:91:E7 ACCEPT all -- anywhere anywhereMAC 00:05:5D:F5:E8:FF ACCEPT all -- anywhere anywhereMAC 00:05:5D:F6:10:BD ACCEPT all -- anywhere anywhereMAC 00:12:3F:D6:89:8A ACCEPT all -- anywhere anywhereMAC 00:14:38:00:AB:A6 Now is the computer with the mac address 00:13:D3:FD:20:FA unable to access the squid proxy server on port 3128 because the mac adress is completly missing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360447: iptables damages mac rules with kernel-image-2.4.27-3-k7
Package: kernel-image-2.4.27-3-k7 Version: 2.4 Severity: |grave |I am using my own iptables script where I execute the following iptables commands on startup: iptables -A INPUT -m mac --mac-source 00:20:ED:39:91:E7 -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:20:ED:39:91:E7 -p udp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:12:3F:D6:89:8A -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:12:3F:D6:89:8A -p udp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:13:D3:FD:20:FA -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:13:D3:FD:20:FA -p udp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:14:38:00:AB:A6 -p tcp --dport 3128:3130 -j ACCEPT iptables -A INPUT -m mac --mac-source 00:14:38:00:AB:A6 -p udp --dport 3128:3130 -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:20:ED:39:91:E7 -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:12:3F:D6:89:8A -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:13:D3:FD:20:FA -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:14:38:00:AB:A6 -j ACCEPT When the server is up, the mac rules are correct like this: debian:~# iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT tcp -- anywhere anywhereMAC 00:20:ED:39:91:E7 tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:20:ED:39:91:E7 udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:12:3F:D6:89:8A tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:12:3F:D6:89:8A udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:13:D3:FD:20:FA tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:13:D3:FD:20:FA udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:14:38:00:AB:A6 tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:14:38:00:AB:A6 udp dpts:3128:icpv2 Chain FORWARD (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhereMAC 00:20:ED:39:91:E7 ACCEPT all -- anywhere anywhereMAC 00:12:3F:D6:89:8A ACCEPT all -- anywhere anywhereMAC 00:13:D3:FD:20:FA ACCEPT all -- anywhere anywhereMAC 00:14:38:00:AB:A6 But after some up time the mac rules are morphing like this: debian:~# iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT tcp -- anywhere anywhereMAC 00:20:ED:39:91:E7 tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:20:ED:39:91:E7 udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:05:5D:F5:E8:FF tcp dpts:3128:icpv2 ACCEPT udp -- anywhereanywhereMAC 00:05:5D:F5:E8:FF udp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:05:5D:F6:10:BD tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:05:5D:F6:10:BD tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:12:3F:D6:89:8A tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:12:3F:D6:89:8A tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:14:38:00:AB:A6 tcp dpts:3128:icpv2 ACCEPT tcp -- anywhere anywhereMAC 00:14:38:00:AB:A6 tcp dpts:3128:icpv2 Chain FORWARD (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhereMAC 00:20:ED:39:91:E7 ACCEPT all -- anywhere anywhereMAC 00:05:5D:F5:E8:FF ACCEPT all -- anywhere anywhereMAC 00:05:5D:F6:10:BD ACCEPT all -- anywhere anywhereMAC 00:12:3F:D6:89:8A ACCEPT all -- anywhere anywhereMAC 00:14:38:00:AB:A6 Now is the computer with the mac address 00:13:D3:FD:20:FA unable to access the squid proxy server on port 3128 because the mac adress is completly missing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#355285: iptables changes mac adresses during runtime (corrected version)
Hello, I am using the PPPOE to open a connection to the internet at boot time too. Best regards, Hansgeorg Schwibbe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#355285: iptables changes mac adresses during runtime (corrected version)
Package: iptables Version: v1.2.11 Severity: grave After some up time the mac adresses of my iptables filter are changing. I am using Debian GNU/Linux 3.1, kernel 2.4.27-2-k7 /// // I am using my my own iptables script which will be started on startup. The script is defined as follows: // // debian:/home/hgsch# cat /etc/init.d/filter_masq #! /bin/sh # PacketFilterScript case "$1" in start) echo -n "Turning on packet filtering:" echo 1 > /proc/sys/net/ipv4/ip_forward echo "." iptables -X iptables -F iptables -t nat -F # POLICY START iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT DROP # POLICY STOP # RULES START #---INPUT iptables -A INPUT -s 127.0.0.1/8 -p icmp -j ACCEPT iptables -A INPUT -s 127.0.0.1/8 -p tcp --dport 53:3306 -j ACCEPT # domain:mysql iptables -A INPUT -s 127.0.0.1/8 -p udp --dport 53:3306 -j ACCEPT # domain:mysql iptables -A INPUT -s 192.168.0.0/24 -p icmp -j ACCEPT iptables -A INPUT -s 192.168.0.0/24 -p tcp --dport 53:2049 -j ACCEPT# domain:nfs iptables -A INPUT -s 192.168.0.0/24 -p udp --dport 53:2049 -j ACCEPT# domain:nfs iptables -A INPUT -m mac --mac-source 00:20:ED:39:91:E7 -p tcp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) shodan.localnet iptables -A INPUT -m mac --mac-source 00:20:ED:39:91:E7 -p udp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) shodan.localnet iptables -A INPUT -m mac --mac-source 00:12:3F:D6:89:8A -p tcp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) osiris.localnet iptables -A INPUT -m mac --mac-source 00:12:3F:D6:89:8A -p udp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) osiris.localnet iptables -A INPUT -m mac --mac-source 00:13:D3:FD:20:FA -p tcp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) hhosch.localnet iptables -A INPUT -m mac --mac-source 00:13:D3:FD:20:FA -p udp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) hhosch.localnet iptables -A INPUT -m mac --mac-source 00:14:38:00:AB:A6 -p tcp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) finn-power iptables -A INPUT -m mac --mac-source 00:14:38:00:AB:A6 -p udp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) finn-power iptables -A INPUT -p tcp --dport 20:21 -j ACCEPT# ftp-data:ftp iptables -A INPUT -p tcp --dport 22 -j ACCEPT # ssh iptables -A INPUT -p udp --dport 22 -j ACCEPT # ssh iptables -A INPUT -p tcp --dport 53 -j ACCEPT # domain iptables -A INPUT -p udp --dport 53 -j ACCEPT # domain iptables -A INPUT -p tcp --dport 80 -j ACCEPT # http iptables -A INPUT -p udp --dport 80 -j ACCEPT # http iptables -A INPUT -p tcp --dport 123 -j ACCEPT # ntp iptables -A INPUT -p udp --dport 123 -j ACCEPT # ntp iptables -A INPUT -p tcp --dport 443 -j ACCEPT # https iptables -A INPUT -p udp --dport 443 -j ACCEPT # https iptables -A INPUT -p tcp --dport 3306 -j ACCEPT # mysql iptables -A INPUT -p udp --dport 3306 -j ACCEPT # mysql iptables -A INPUT -p tcp --dport 32768:65535 -j ACCEPT # 32768:65535 iptables -A INPUT -p udp --dport 32768:65535 -j ACCEPT # 32768:65535 #---FORWARD-- iptables -A FORWARD -d 192.168.0.0/24 -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:20:ED:39:91:E7 -j ACCEPT # shodan.localnet iptables -A FORWARD -m mac --mac-source 00:12:3F:D6:89:8A -j ACCEPT # osir
Bug#355282: iptables changes mac adresses during runtime
Package: iptables Version: v1.2.11 Severity: grave |After some up time the mac adresses of my iptables filter are changing. |I am using Debian GNU/Linux 3.1, kernel 2.4.27-2-k7| |// I am using my my own iptables script which will be started on startup. The script is defined as follows: // debian:/home/hgsch# cat /etc/init.d/filter_masq #! /bin/sh # PacketFilterScript case "$1" in start) echo -n "Turning on packet filtering:" echo 1 > /proc/sys/net/ipv4/ip_forward echo "." iptables -X iptables -F iptables -t nat -F # POLICY START iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT DROP # POLICY STOP # RULES START #---INPUT iptables -A INPUT -s 127.0.0.1/8 -p icmp -j ACCEPT iptables -A INPUT -s 127.0.0.1/8 -p tcp --dport 53:3306 -j ACCEPT # domain:mysql iptables -A INPUT -s 127.0.0.1/8 -p udp --dport 53:3306 -j ACCEPT # domain:mysql iptables -A INPUT -s 192.168.0.0/24 -p icmp -j ACCEPT iptables -A INPUT -s 192.168.0.0/24 -p tcp --dport 53:2049 -j ACCEPT# domain:nfs iptables -A INPUT -s 192.168.0.0/24 -p udp --dport 53:2049 -j ACCEPT# domain:nfs iptables -A INPUT -m mac --mac-source 00:20:ED:39:91:E7 -p tcp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) shodan.localnet iptables -A INPUT -m mac --mac-source 00:20:ED:39:91:E7 -p udp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) shodan.localnet iptables -A INPUT -m mac --mac-source 00:12:3F:D6:89:8A -p tcp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) osiris.localnet iptables -A INPUT -m mac --mac-source 00:12:3F:D6:89:8A -p udp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) osiris.localnet iptables -A INPUT -m mac --mac-source 00:13:D3:FD:20:FA -p tcp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) hhosch.localnet iptables -A INPUT -m mac --mac-source 00:13:D3:FD:20:FA -p udp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) hhosch.localnet iptables -A INPUT -m mac --mac-source 00:14:38:00:AB:A6 -p tcp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) finn-power iptables -A INPUT -m mac --mac-source 00:14:38:00:AB:A6 -p udp --dport 3128:3130 -j ACCEPT # 3128:icpv2 (squid) finn-power iptables -A INPUT -p tcp --dport 20:21 -j ACCEPT# ftp-data:ftp iptables -A INPUT -p tcp --dport 22 -j ACCEPT # ssh iptables -A INPUT -p udp --dport 22 -j ACCEPT # ssh iptables -A INPUT -p tcp --dport 53 -j ACCEPT # domain iptables -A INPUT -p udp --dport 53 -j ACCEPT # domain iptables -A INPUT -p tcp --dport 80 -j ACCEPT # http iptables -A INPUT -p udp --dport 80 -j ACCEPT # http iptables -A INPUT -p tcp --dport 123 -j ACCEPT # ntp iptables -A INPUT -p udp --dport 123 -j ACCEPT # ntp iptables -A INPUT -p tcp --dport 443 -j ACCEPT # https iptables -A INPUT -p udp --dport 443 -j ACCEPT # https iptables -A INPUT -p tcp --dport 3306 -j ACCEPT # mysql iptables -A INPUT -p udp --dport 3306 -j ACCEPT # mysql iptables -A INPUT -p tcp --dport 32768:65535 -j ACCEPT # 32768:65535 iptables -A INPUT -p udp --dport 32768:65535 -j ACCEPT # 32768:65535 #---FORWARD-- iptables -A FORWARD -d 192.168.0.0/24 -j ACCEPT iptables -A FORWARD -m mac --mac-source 00:20:ED:39:91:E7 -j ACCEPT # shodan.localnet
Bug#345458: fsck 1.37
Package: fsck Version: 1.37 Severity: |grave Tags: sarge | After a couple of weeks of server uptime I got the following error during the boot process and the boot process stops with the given login prompt: Checking root file system... fsck 1.37 (21-Mar-2005) [Filesystem check] Filesystem is clean Filsystem seems to have fatal corruptions. Running with --rebuild-tree is required. fsck failed. Please repair manually and reboot. Please note that the root file system is currently mounted read-only. To remount it read-write: # mount -n -o remount,rw / CONTROL-D will exit from this shell and REBOOOT the system. Give root password for maintenance (or typer Control-D to continue): To solve this problem I have done the following steps without any effect: - Executing Memtest-86 V3.2 with all tests and without any errors - Changing the bus cable - Changing the harddisk - Changing the filesystem from Ext3 to Reiserfs I am using Debian GNU/Linux 3.1, kernel 2.4.27-2-686 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345456: fsck 1.37
Package: fsck Version: 1.37 After a couple of weeks of server uptime I got the following error during the boot process and the boot process stops with the given login prompt: Checking root file system... fsck 1.37 (21-Mar-2005) [Filesystem check] Filesystem is clean Filsystem seems to have fatal corruptions. Running with --rebuild-tree is required. fsck failed. Please repair manually and reboot. Please note that the root file system is currently mounted read-only. To remount it read-write: # mount -n -o remount,rw / CONTROL-D will exit from this shell and REBOOOT the system. Give root password for maintenance (or typer Control-D to continue): To solve this problem I have done the following steps without any effect: - Executing Memtest-86 V3.2 with all tests and without any errors - Changing the bus cable - Changing the harddisk - Changing the filesystem from Ext3 to Reiserfs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318743: grub-md5-crypt creates wrong md5 keys
Package: grub Version: 0.95 "grub-md5-crypt" creates different MD5 keys of the same password. The encrypted passwords are not working with the "password --md5 MD5-PASSWORD" option in the "/boot/grub/menu.1st" file. I am using Debian GNU/Linux 3.1, kernel 2.4.27-2-686 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
