Hi,
after weeks of reading FAQ's, guides and everything I found about firewalls
and FreeS/WAN I still have a big problem.
But first I describe what is working and my network setup:
roadwarrior
(a.b.c.d)
|
internet
|
(d.e.f.g, static ip, ext. device, eth1, ipsec0)
gateway with SuSE 8.2 and FreeS/WAN
(10.10.11.3, int. device, eth0)
|
(10.10.11.0/24, int. network)
LAN
IPSec connection between roadwarrior and gateway external device works
without any problem.
But no matter what I try, if I try to ping the gateway's internal device
(10.10.11.3) or the internal network I always get
SuSE-FW-ILLEGAL-TARGET IN=ipsec0 OUT=
MAC=xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx SRC=xxx.xxx.xxx.x
DST=10.10.11.3 LEN=60 TOS=0x00 PREC=0x00 TTL=128 ID=3540 PROTO=ICMP TYPE=8
CODE=0 ID=1280 SEQ=256
*SRC=xxx.xxx.xxx.x is the adress of my roadwarrior
I did set up the Firewall as described in
/usr/share/doc/packages/SuSEfirewall2/EXAMPLES Scenario4:
FW_DEV_EXT="eth1 ipsec0"
FW_DEV_INT="eth0"
FW_ROUTE="yes"
FW_MASQUERADE="yes"
FW_MASQ_NETS="10.10.11.0/24"
FW_SERVICES_EXT_UDP="500"
FW_SERVICES_EXT_IP="50 51"
FW_FORWARD="a.b.c.d,10.10.11.0/24 10.10.11.0/24,a.b.c.d"
a.b.c.d is the adress of my roadwarrior
I left all other options default for testing the IPSec connections.
Even without routing and masquerading I still get the error above and the
above settings for routing
forwarding and masquerading did not change anything.
I also tried to make a custon updown script to be executed when ipsec0 comes
up, that didn't change
anything too.
If the firewall is disabled I can ping the gateway's internal device
(10.10.11.3) from an external IPSec connection.
With the firewall enabled I can only access the external device of the
gateway - I cannot ping to the internal network.
Any suggestions what I am doing wrong here?
I guess I have to use a custom updown script that allows traffic between the
roadwarrior and the internal network and
is executed each time an IPSec connection comes up.
I tried this script but still had the SuSE-FW-ILLEGAL-TARGET error:
up-client:)
iptables -I FORWARD 1 -s $PLUTO_MY_CLIENT_NET/$PLUTO_MY_CLIENT_MASK \
-d $PLUTO_PEER_CLIENT -j ACCEPT
iptables -I FORWARD 1 -d $PLUTO_MY_CLIENT_NET/$PLUTO_MY_CLIENT_MASK \
-s $PLUTO_PEER_CLIENT -j ACCEPT
;;
down-client:)
iptables -D FORWARD -s $PLUTO_MY_CLIENT_NET/$PLUTO_MY_CLIENT_MASK \
-d $PLUTO_PEER_CLIENT -j ACCEPT
iptables -D FORWARD -d $PLUTO_MY_CLIENT_NET/$PLUTO_MY_CLIENT_MASK \
-s $PLUTO_PEER_CLIENT -j ACCEPT
;;
I checked the Pluto variables at execution time of the script and
ip-adresses represented by
those were correct.
I appreciate any suggestions, thanks in advance,
R. Peters
Hello,
i have the following setup on my server:
Suse 8.2 Professional as operating system and RSBAC and Pax as security enhancements. As server programs I have apache, mysql and samba installed and RSBAC configured accordingly. So far the system works fine.
In order to prevent that some bad guy - who has somehow acquired root privileges - from changing the password of the RSBAC "security-officer", logging in as him and deactivating RSBAC, I wanted to "move" the right of changing password to a seperate user, creating a "password officer". For that I created a seperate "RC_FD" (filetype definition in the role based access model) for /etc/passwd and /etc/shadow, so I can define, which user shall have read-write access on them. Up to that point I have got it working.
The problem is now, that passwd only allows root to change passwords from other users. With the tools of RSBAC I could persuade passwd to accept an other user as system administrator, as substitute for root.
Is there a way, to get passwd accepting an other user as entitled to changing other users passwords ?
Thank you very much in advance.
With best regards.
Patrique Wolfrum
-----BEGIN PGP SIGNED MESSAGE-----
______________________________________________________________________________
SUSE Security Announcement
Package: thttpd
Announcement-ID: SuSE-SA:2003:044
Date: Friday, Oct 31st 2003 13:04 MEST
Affected products: 7.3, 8.0, 8.1, 8.2, 9.0
Vulnerability Type: remote privilege escalation/
information leak
Severity (1-10): 5
SUSE default package: no
Cross References: CAN-2003-0899
CAN-2002-1562
Content of this advisory:
1) security vulnerability resolved:
- buffer overflow
- information leak (virtual hosting)
problem description, discussion, solution and upgrade information
2) pending vulnerabilities, solutions, workarounds:
- libnids
- KDE
- postgresql
- frox
- sane
- ircd
- fileutils
- mc
- apache1/2
3) standard appendix (further information)
______________________________________________________________________________
1) problem description, brief discussion, solution, upgrade information
Two vulnerabilities were found in the "tiny" web-server thttpd.
The first bug is a buffer overflow that can be exploited remotely
to overwrite the EBP register of the stack. Due to memory-alignment of
the stack done by gcc 3.x this bug can not be exploited. All thttpd
versions mentioned in this advisory are compiled with gcc 3.x and are
therefore not exploitable.
The other bug occurs in the virtual-hosting code of thttpd. A remote
attacker can bypass the virtual-hosting mechanism to read arbitrary
files.
Please download the update package for your distribution and verify its
integrity by the methods listed in section 3) of this announcement.
Then, install the package using the command "rpm -Fhv file.rpm" to apply
the update.
Our maintenance customers are being notified individually. The packages
are being offered to install from the maintenance web.
Intel i386 Platform:
SuSE-9.0:
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/thttpd-2.23beta1-165.i…
e33f3897cac1e1fe117eff8ca252ec0f
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/thttpd-2.23beta1-165.i…
cd5c2aeb6d31d6a6781f392af17a4989
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/thttpd-2.23beta1-165.sr…
c6e2446bc94c8c00d35b7741b67df678
SuSE-8.2:
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/thttpd-2.23beta1-164.i…
a491b55f562fa0f3b1679ee819140c72
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/thttpd-2.23beta1-164.i…
bbb3dd624b19d8683223049a070d4cf2
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/thttpd-2.23beta1-164.sr…
2710751ff1ee8fbab3c2934c5cb09f3d
SuSE-8.1:
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/thttpd-2.23beta1-163.i…
428db4fb2eccebb5ed16cb28161ba2a5
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/thttpd-2.23beta1-163.i…
b32fb0a87d8d7de3ed1953e64da89bc8
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/thttpd-2.23beta1-163.sr…
e64bc1488747a414f6bd60735f82385f
SuSE-8.0:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/thttpd-2.20c-98.i386.rpm
952dcca179b647afdeea02b987e3daf8
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/thttpd-2.20c-98.i386.patch.r…
e596221f34a73ba6fdd29abcecb6e211
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/thttpd-2.20c-98.src.rpm
8500be9c635d1c5c9618ecca2a09a5e7
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/thttpd-2.20b-175.i386.rpm
16ffc5238c1f57b8a1e6e02989524e82
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/thttpd-2.20b-175.src.rpm
b5c4b9c65182fcd2a326e3edad7b2dfb
PPC Power PC Platform:
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/thttpd-2.20b-112.ppc.rpm
e7aaff82bd90c459849dd78b1cc47515
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/thttpd-2.20b-112.src.rpm
8ac31eb38063a891e37ed327a5ddbc0c
______________________________________________________________________________
2) Pending vulnerabilities in SUSE Distributions and Workarounds:
- libnids
New libnids packages were released to stop remote command execution
due to a memory corruption in the TCP reassembly code. (CAN-2003-0850)
Please download them from our FTP servers.
- KDE
New KDE packages are currently being tested. These packages fixes
several vulnerabilities:
+ remote root compromise (CAN-2003-0690)
+ weak cookies (CAN-2003-0692)
+ SSL man-in-the-middle attack
+ information leak through HTML-referrer (CAN-2003-0459)
The packages will be release as soon as testing is finished.
- postgresql
Several buffer overflow problems were fixed in the pg_to_asci()
function of postgresql server.
New packages are available on our FTP servers.
- frox
A denial-of-service attack in frox can be trigger remotely.
The packages are currently tested and will be release as soon as
possible.
- sane
The scanner service sane of SuSE Linux 7.3-8.1 is vulnerable to
a remote denial-of-service attack. This attack can even be triggered
if the attackers host is not listed in the saned.conf file.
The packages are currently tested and will be release as soon as
possible.
- ircd
The Internet Relay Chat daemon is vulnerable to a remote denial-of-
service attack. The attack can be triggered by irc clients directly
connected to the daemon.
The packages are currently tested and will be release as soon as
possible.
- fileutils
A local denial-of-service attack can be triggered by abusing the -w
option of ls(1). This attack can be turned into a remote denial-of-
service by using network services, like wuftpd, that rely on the
ls(1) command installed on the system.
The packages are currently tested and will be release as soon as
possible.
- mc
By using a special combination of links in archive-files it is possible
to execute arbitrary commands while mc tries to open it in its VFS.
The packages are currently tested and will be release as soon as
possible.
- apache1/2
The widely used HTTP server apache has several security vulnerabilities:
- locally exploitable buffer overflow in the regular expression code.
The attacker must be able to modify .htaccess or httpd.conf.
(affects: mod_alias and mod_rewrite)
- under some circumstances mod_cgid will output its data to the
wrong client (affects: apache2)
______________________________________________________________________________
3) standard appendix: authenticity verification, additional information
- Package authenticity verification:
SUSE update packages are available on many mirror ftp servers all over
the world. While this service is being considered valuable and important
to the free and open source software community, many users wish to be
sure about the origin of the package and its content before installing
the package. There are two verification methods that can be used
independently from each other to prove the authenticity of a downloaded
file or rpm package:
1) md5sums as provided in the (cryptographically signed) announcement.
2) using the internal gpg signatures of the rpm package.
1) execute the command
md5sum <name-of-the-file.rpm>
after you downloaded the file from a SUSE ftp server or its mirrors.
Then, compare the resulting md5sum with the one that is listed in the
announcement. Since the announcement containing the checksums is
cryptographically signed (usually using the key security(a)suse.de),
the checksums show proof of the authenticity of the package.
We disrecommend to subscribe to security lists which cause the
email message containing the announcement to be modified so that
the signature does not match after transport through the mailing
list software.
Downsides: You must be able to verify the authenticity of the
announcement in the first place. If RPM packages are being rebuilt
and a new version of a package is published on the ftp server, all
md5 sums for the files are useless.
2) rpm package signatures provide an easy way to verify the authenticity
of an rpm package. Use the command
rpm -v --checksig <file.rpm>
to verify the signature of the package, where <file.rpm> is the
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an un-installed rpm
package file.
Prerequisites:
a) gpg is installed
b) The package is signed using a certain key. The public part of this
key must be installed by the gpg program in the directory
~/.gnupg/ under the user's home directory who performs the
signature verification (usually root). You can import the key
that is used by SUSE in rpm packages for SUSE Linux by saving
this announcement to a file ("announcement.txt") and
running the command (do "su -" to be root):
gpg --batch; gpg < announcement.txt | gpg --import
SUSE Linux distributions version 7.1 and thereafter install the
key "build(a)suse.de" upon installation or upgrade, provided that
the package gpg is installed. The file containing the public key
is placed at the top-level directory of the first CD (pubring.gpg)
and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .
- SUSE runs two security mailing lists to which any interested party may
subscribe:
suse-security(a)suse.com
- general/linux/SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an email to
<suse-security-subscribe(a)suse.com>.
suse-security-announce(a)suse.com
- SUSE's announce-only mailing list.
Only SUSE's security announcements are sent to this list.
To subscribe, send an email to
<suse-security-announce-subscribe(a)suse.com>.
For general information or the frequently asked questions (faq)
send mail to:
<suse-security-info(a)suse.com> or
<suse-security-faq(a)suse.com> respectively.
=====================================================================
SUSE's security contact is <security(a)suse.com> or <security(a)suse.de>.
The <security(a)suse.de> public key is listed below.
=====================================================================
______________________________________________________________________________
The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular,
it is desired that the clear-text signature shows proof of the
authenticity of the text.
SUSE Linux AG makes no warranties of any kind whatsoever with respect
to the information contained in this security advisory.
Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de>
- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff
4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d
M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO
QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK
XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE
D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd
G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM
CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE
myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr
YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD
wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d
NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe
QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe
LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t
XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU
D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3
0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot
1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW
cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E
ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f
AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E
Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/
HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h
t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT
tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM
523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q
2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8
QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw
JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ
1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH
ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1
wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY
EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol
0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK
CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co
SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo
omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt
A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J
/LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE
GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf
ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT
ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8
RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ
8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb
B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X
11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA
8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj
qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p
WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL
hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG
BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+
AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi
RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0
zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM
/3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7
whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl
D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz
dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI
RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI
DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE=
=LRKC
- -----END PGP PUBLIC KEY BLOCK-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iQEVAwUBP6JW93ey5gA9JdPZAQE7AAf+LMQ45cIOD3iSCFZ8g/RuWVI5yiY2CkE2
0KpivccK5qehDInv+spLFAZBOlFXjmkmPcyBZbaFkuTdo6PpnGicJ6gHdPvYzVZ1
+0I0T9u8dZUlAoeGnTVNtzcN8yEA9xcp1mjEXORoclR5zwwVFXRcp8rktde768yD
kBvur0ZY9g4OyJEwb/UzdiKxKuKiFlq3llVz5ID8qDMIDQfORygVqjxI4pFDwff/
Pm9qxit7J2Q1tB3VZXBkUb+ba+Y6bLBFkhk64hHr+q3jtMZlrK6z2WMJsF/a5gqp
JDaTp1BxChMeJ6Q5YTq8ZCUzKKu7Dg4d42+php7QiR9UIifk4ch2gQ==
=6u83
-----END PGP SIGNATURE-----
Bye,
Thomas
--
Thomas Biege <thomas(a)suse.de>, SuSE Linux AG, Security Support & Auditing
"lynx -source http://www.suse.de/~thomas/contact/thomas.asc | pgp -fka"
Key fingerprint = 51 AD B9 C7 34 FC F2 54 01 4A 1C D4 66 64 09 83
--
... stay with me, save and ignorant, go back to sleep...
- Maynard James Keenan
Greetings All,
I am having a problem with YOU that I hope someone here can help me with. Essentially, whenever I run YOU I get the error:
Initialization failed. Try again.
If failure continues, choose
another SuSE FTP/HTTP server.
I tried to get help from SuSE (we have support) some time ago, and they told me that I have UnitedLinux installed and not SLES. Silly me, I thought they were one and the same. Anyway, I can see the request going through our proxy server and the response is a 404 error:
1067289521.691 390 10.10.10.200 TCP_MISS/200 217 GET http://sdb.suse.de//youfix/ - DIRECT/195.135.220.8 text/html
1067289522.167 423 10.10.10.200 TCP_MISS/404 561 GET http://sdb.suse.de//youfix/i386/update/UnitedLinux/1.0/patches/directory.3 - DIRECT/195.135.220.8 text/html
I have downloaded and installed the newest (I think) version of YOU: yast2-online-update-2.6.16-0
Any ideas / suggestions / pointers / advise is greatly appreciated.
Thanks,
Grant
This electronic message transmission is a PRIVATE communication which contains
information which may be confidential or privileged. The information is intended
to be for the use of the individual or entity named above. If you are not the
intended recipient, please be aware that any disclosure, copying, distribution
or use of the contents of this information is prohibited. Please notify the
sender of the delivery error by replying to this message, or notify us by
telephone (877-633-2436, ext. 0), and then delete it from your system.
Hello List,
I'm searching for a possiblity to cache a realaudio, mp3 and/or a
windowsmedia audio stream.
The intension, is to reduce the traffic in the lan, because many guys hear
the same stream (radiostation) in our house. Now it would be nice, if a
proxy, or any other chaching instance would load the stream, and store it in
a cache. So the guys could connect to the local streamingserver to hear the
cached stream.
Sorry for the post in the security list, but I think it is be best list for
such questions.
best regards,
Hans
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
A new version of the installing's script for qmail are released.
All feedback are welcome for this final 1.3.6 :)
http://www.linuxpourtous.com/download/qmail/install_qmail-1.3.6.tar.gzhttp://www.linuxpourtous.com/download/qmail/READMEhttp://www.linuxpourtous.com/download/qmail/CHANGELOG
Changelog since 1.3.6-rc6 :
* Testing installation script on Debian testing without error.
* Added values.suse and values.debian for both installation.
* This script works fine on SuSE Linux and Debian testing.
* Added apt-debian.sh for installing all needed softwares on Debian.
* Minor bug fix
Best regards
- --
Franck
http://www.linuxpourtous.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/n8Im1zwfep5k9qERAuWsAJ4tWfX7u49mmKRFsxIFvXpCzsEtPwCeN0OX
urulkBBpGKP7kCNU4/rL658=
=DW0v
-----END PGP SIGNATURE-----
Hi List,
I have an problem with my SuSe 8.2 installation with all current security patches applied.
If I enter /bin/false as login shell in the /etc/passwd the user can still login and gets shell
access. After rebooting the system the shell entry in the /etc/passwd is processed correct
and a login attempt is closed as you would expect. Other entries like home dir in the passwd
are parsed correct.
Any ideas?
Thanks and regards
Daniel
I seem to have strange problems that are related to the ipv6 module
being enabled. Behaviour seems (so far at least) to differ between
kernel versions: k_deflt-2.4.19-74 and k_deflt-2.4.19-340.
The problem is seen as slow startup of certain networked
Java applications using JBoss services. I traced the issue
to failing DNS replies, i.e. timeouts but the problem was that
there was DNS AAAA queries (IPv6 related) going on. And
the server was unable to answer these - as it is serving IPv4.
Having found that out using ethereal I checked from web and
found out that disabling the IPv6 module via
/etc/modules.conf drops off IPv6 stuff and might help - actually
did help.
However, I checked with an older version of the kernel - and
probably some other stuff as well - and the whole thing seems
to work OK there, with IPv6 module.
Is there some explanation I have missed? Is this behaviour
correct now, or was it earlier? Does this affect performance
and possibly security due extra delays with DNS timeouts?
Is the correct solution to disable the module via:
# alias net-pf-10 ipv6 (in /etc/modules.conf)
or is there better ways of dealing with this? It has quite a
big hit on the application since the "normal" startup time
is in the range of 0.7 seconds and these DNS timeouted
AAAA queries push it somewhere between 15 and 20 seconds!
br,
timo
Hello suse-security,
I have installed the following version on SuSE8.2:
# rpm -q squid
squid-2.5.STABLE1-63
Now, I don´t see any Updates to this package offered by YOU, but when
I look at
ftp.suse.de:/pub/suse/i386/8.2/i586/squid-2.5.STABLE1-73.i586.rpm
There is a new package with version number -73 ?
Does the ftp-distribution use different version-numbers than the CD
distribution in general? Or am I missing something?
The reason I was searching for squid in the first place was that I
wanted to use NT/Samba User Groups for Authentication, but didn´t find
a wb_group.sh or wb_group.pl or wbinfo_group.pl on my system.
What is recommended to get this workingon SuSE8.2?
I found a perl script at
http://www.squid-cache.org/cgi-bin/cvsweb.cgi/squid/helpers/external_acl/wb…
and added the following line to squid.conf:
external_acl_type nt_group %LOGIN /usr/local/libexec/wbinfo_group.pl
That does the job, but I am not sure if this is the best way?
--
Mit freundlichen Grüßen,
André Sänger mailto:Andre.Saenger@gmx.de
Landratsamt Coburg
I am fairly new to linux and suse but I am trying to set up 8.2 pro as a
mail server. I have recieved all of the updates. and found this in the
documentation to create forward listeners
ssl -L 25:myserver:25 myserver
ssl -L 110:myserver:110 myserver
I had to shudown my pop3 server to get the 110 port to allow that and I
started it back up. I get the following mesage in outlook from a pc
internal to the network
The connection to the server has failed.
Account: 'redmail.redoakhealthcare.com',
Server: 'redmail.redoakhealthcare.com', Protocol: POP3, Port: 110, Secure
(SSL): No, Socket Error: 10061, Error Number: 0x800CCC0E
Etherreal from both machines shows 3 queries and acks
In the mail log I get
command stream end of file while user=??? host=thehostIamrunningoutlook on
and its ip address.
I would appreciate any help
--
Absolute Internet Services (http://www.aiserve.net)
