Hi folks,
maybe someone could give me a hint...
I switched from:
fetchmail->sendmail->sendmail.milter->Amavis->.forward->procmail->spamc(SpamAssasin)->INBOX
which did global virus checking and per user spam checking with Bayes testing
to
fetchmail->postfix->amavisd-new->perl-spamassassin->cyrus-imapd
which does global virus and global spam checking BUT NO PER USER spam
checking, so without Bayes testing! :-(
So the rate of unreconised spam did increase.
I fiddled around with options in the /etc/mail/spamassassin/local.cf, but they
were ignored because amavisd-new calls spamassin via perl interface and takes
some SA parameters from the /etc/amavisd.conf (beginning with $sa_).
I tried calling a SUIDed cyrus deliver (without SUID deliver hasn't got the
right: deliver[3876]: connect(/var/lib/imap/socket/lmtp) failed: Permission
denied) to user cyrus via .forward and a .procmailrc. The log said that lmtpd
was called, but depending on the syntax of deliver in the .procmailrc the
mail was delivered to the INBOX-file in /var/spool/mail or just vanished!
One example for my .promailrc:
:0 fw
|/usr/bin/spamc -f
|/usr/lib/cyrus/bin/deliver -e -a david -m user.david
and the .forward:
"|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #user"
Could someone give me a hint using sieve or procmail for a per user
SpamAssassin check?
Thanks in advance.
--
Eat, sleep and go running,
David Huecking.
Encrypted eMail welcome!
GnuPG/ PGP-Key: 0x57809216. Fingerprint:
3DF2 CBE0 DFAA 4164 02C2 4E2A E005 8DF7 5780 9216
-----BEGIN PGP SIGNED MESSAGE-----
______________________________________________________________________________
SUSE Security Announcement
Package: kdelibs/kdelibs3
Announcement-ID: SuSE-SA:2003:014
Date: Wed May 26 12:00:00 MEST 2004
Affected products: 8.0, 8.1, 8.2, 9.0, 9.1
SuSE Linux Database Server,
SuSE Linux Enterprise Server 7, 8
SuSE Linux Firewall on CD 2
SuSE Linux Connectivity Server
SuSE Linux Office Server
SuSE Linux Desktop 1.0
Vulnerability Type: remote file creation
Severity (1-10): 6
SUSE default package: yes
Cross References: CAN-2004-0411
Content of this advisory:
1) security vulnerability resolved: URI file creation vulnerability
problem description, discussion, solution and upgrade information
2) pending vulnerabilities, solutions, workarounds:
- rsync
- film
- apache/mod_ssl
3) standard appendix (further information)
______________________________________________________________________________
1) problem description, brief discussion, solution, upgrade information
The kdelibs3 (kdelibs for SLES7 based products) package is a core package
for the K desktop environment (KDE). The URI handler of the kdelibs3
and kdelibs class library contains a flaw which allows remote
attackers to create arbitrary files as the user utilizing the
kdelibs3/kdelibs package.
Affected are applications which use the kdelibs3/kdelibs URI handler
such as Konqueror or Kmail.
The original KDE advisory can be found at
http://www.kde.org/info/security/advisory-20040517-1.txt
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.1:
ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kdelibs3-3.2.1-44.10.i…
3724021df2c50d25729c85ccbc1c6e0b
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kdelibs3-3.2.1-44.10.i…
eb07494e104d37c02430c8e8a451c8c0
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kdelibs3-3.2.1-44.10.sr…
bda5d53abd4c21ac641cf551a004f847
SuSE-9.0:
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/kdelibs3-3.1.4-51.i586…
15b6948b8331d58e069fef80165e34ec
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/kdelibs3-3.1.4-51.i586…
f523a907f1e3d5aaf9e77632be339b78
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/kdelibs3-3.1.4-51.src.r…
5fae5675cf3a8ba15e26a1467818de13
SuSE-8.2:
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/kdelibs3-3.1.1-139.i58…
5c0a195dd90018f2f2fdc26c0f3aa414
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/kdelibs3-3.1.1-139.i58…
1bd13baccb08418a86d1dd6a076d7a85
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/kdelibs3-3.1.1-139.src.…
2f281da09839e883fc3e7a173928accb
SuSE-8.1:
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/kdelibs3-3.0.5-54.i586…
7f65572c6011fcb9745a93df71661b74
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/kdelibs3-3.0.5-54.i586…
2a177303c21e7d109642450fd6b5a456
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/kdelibs3-3.0.5-54.src.r…
b717891fbabdf0fb6f01098f6ec4628c
SuSE-8.0:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/kde1/kdelibs3-3.0-120.i386.rpm
775562f135feac98e007d5f8e21bbbd7
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/kde1/kdelibs3-3.0-120.i386.patc…
91032e4cb6bc77263fc4156195f63e92
Opteron x86_64 Platform:
SuSE-9.1:
ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kdelibs3-3.2.1-44.…
19f3520ee5c742ad7994f3426a0ea7f3
patch rpm(s):
ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kdelibs3-3.2.1-44.…
c089127df66d98c1a9e1a561fb9c1f0b
source rpm(s):
ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kdelibs3-3.2.1-44.10.…
2b25abf3d206152711a0a5597d343f4a
SuSE-9.0:
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/kdelibs3-3.1.4-51.…
c136da67c2a288177ceb7bfe537ac248
patch rpm(s):
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/kdelibs3-3.1.4-51.…
b0886ca176fa3f54b42da642a26554d0
source rpm(s):
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/kdelibs3-3.1.4-51.src…
e0d10e3b23142eb6ee95cbb5afad71da
______________________________________________________________________________
2) Pending vulnerabilities in SUSE Distributions and Workarounds:
- rsync
rsync prior to version 2.6.1 does not properly sanitize paths
when running as read/write daemon without chroot. New update packages
are available on our ftp servers which fix this problem.
- film
The film program creates temporary files in an insecure way. New
update packages are available on our ftp servers.
- apache/mod_ssl
A buffer overflow in a uuencode function of mod_ssl has been fixed as
well as various minor bugs (CAN-2003-0987, CAN-2003-0020, CAN-2004-0174
and CAN-2003-0993). New packages are currently being tested and will
soon be available on our ftp servers.
______________________________________________________________________________
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)
iQEVAwUBQLR+S3ey5gA9JdPZAQHP3wgAl2dSWxc65GXtIoMy4b5qVYuO/7mBUtz0
eSCeiacCmTO4wO6kdBBz+GbgoUwoCMnaOivQ0cOt+tAN5KkxaDUe5Yf1fM7NSkmM
W+P4atOogDnOpioA2PQKmt4V0rrZ3QTvgfWydMSYIcKs4ZAmCYPQLzA0RJSf4MZl
FKp/S7SIBLZzdH1Qn5ScjoXEw9wq+g/ZypzY+e6kcKfdAK6muJRsaTpkbyU6TIho
Nl6zA/kio0x/jWbS3hp7lYfWD2hJH7U5HmtC3aQfwha8xwb4lckVIk2HeorYSzSW
AAyi7y85fFYvnJIiS6BG06QpR51dSZ6FxNaIVIPmEzzYHVc+y96ntQ==
=tid+
-----END PGP SIGNATURE-----
Starting around 3:45 am on May 28th, dozens of incoming UDP packets are being
dropped per hour on these two ports alone. Usually I woulnd't be alarmed by
this, but these packets have an unusual payload size of 777 bytes and both
ports are tried. It looks like they are trying to overflow a buffer
somewhere. Anyone know what this is?
Regards,
Arjen
Hi !
I have a problem with the recent kdelibs3 update on my SuSE 8.0
servers. The dependency checking gives me the following error message:
error: failed dependencies:
kdelibs3 = 3.0.5 is needed by kdelibs3-devel-3.0.5-28
kdelibs3 >= 3.0.3 is needed by kdebase3-3.0.4-76
Does anyone have the same problem ? What is going wrong there ?
The last ethereal patch also failed with the error message:
error: failed dependencies:
libethereal.0 is needed by ethereal-0.10.3-10
libwiretap.0 is needed by ethereal-0.10.3-10
Dear suse people, will this problem be fixed or do I have to live with
the older packages ?
Regards,
Armin
--
Am Hasenberg 26 office: Institut für Atmosphärenphysik
D-18209 Bad Doberan Schloss-Straße 6
Tel. ++49-(0)38203/42137 D-18225 Kühlungsborn / GERMANY
Email: schoech(a)iap-kborn.de Tel. +49-(0)38293-68-102
WWW: http://armins.cjb.net/ Fax. +49-(0)38293-68-50
Am Mittwoch, 26. Mai 2004 13:34 schrieb Sebastian Krahmer:
> _________________________________________________________________
>_____________
>
> SUSE Security Announcement
>
> Package: kdelibs/kdelibs3
> Announcement-ID: SuSE-SA:2003:014
> Date: Wed May 26 12:00:00 MEST 2004
> Affected products: 8.0, 8.1, 8.2, 9.0, 9.1
I use kdelibs3 3.2.2-2 17.04.2004 18:40:30 CEST. Does this version
include this security-problem too? I checked the ftp-server and
there is no newer version available.
Al
Hello,
I have received this alert
US-CERT Technical Cyber Security Alert TA04-147A -- CVS Heap Overflow
Vulnerability
Systems Affected
* Concurrent Versions System (CVS) versions prior to 1.11.16
* CVS Features versions prior to 1.12.8
I have this version on my system:
#cvs -v
Concurrent Versions System (CVS) 1.11.6 (client/server)
Copyright (c) 1989-2003 Brian Berliner, david d `zoo' zuhn,
Jeff Polk, and other authors
I suppose I have the problem that the CERT alerts, so where is the patch
or the version that solves this problem?
Thanks
--
Emiliano Sutil García
The recent SUSE Security Announcement: kdelibs (SuSE-SA:2004:014) has
only an update for version kdelibs3-3.0.5-54. and not the version
kdelibs3-3.0.3-68 that was initially installed under SUSE 8.1.
If the current patch update is attempted on SUSE 8.1, the following
message is displayed:
error: failed dependencies:
libstdc++.so.5(GLIBCPP_3.2.2) is needed by kdelibs3-3.0.5-54
When I attempt to install libstdc++-3.2.2-45.i586.rpm the following
message is displayed:
file /usr/lib/libstdc++.so.5 from install of libstdc++-3.2.2-45
conflicts with file from package libstdc++-3.2-36
If I attempt to un-install libstdc++-3.2-36 so that I can install
libstdc++-3.2.2-45, the following message is displayed:
error: removing these packages would break dependencies:
libstdc++ = 3.2-36 is needed by libstdc++-devel-3.2-36
libstdc++.so.5 is needed by unrar-3.00-42
libstdc++.so.5 is needed by xlock-5.03-207
libstdc++.so.5 is needed by yast2-packagemanager-2.6.26-0
libstdc++.so.5 is needed by htdig-3.1.6-49
and approx. 80 more programs are listed.
I could do an install/upgrade using the nodeps option, however I would
be fearful that I would break something.
How can I avoid the above problems and install a fix for kdelibs under
SUSE 8.1 that has currently kdelibs3-3.0.3-68 installed?
--
*******************************
John Whelan, Dublin City University,
*******************************
First thanks to all that have answered my questions.
The bad news is that I don´t know why this work and before doesn´t.
I´ll going to put my files if someone is interested.
In my PC-box I have a bat file with this
"c:\archivos de programa\openvpn\bin\openvpn.exe" --remote SERVERLINUX
--dev tunl --ifconfig 10.4.0.1 10.4.0.2 --secret "c:\archivos de
programa\openvpn\config\key.txt" --comp-lzo
In the lmhosts an hosts file I have this entry:
10.4.0.2 SERVERLINUX
On the linux side I have this bash file:
#!/bin/sh
/usr/local/sbin/openvpn --remote myPCIP --dev tun --ifconfig 10.4.0.2
10.4.0.1 --secret key.txt --comp-lzo --daemon
On the smb.conf file I have this:
# Global parameters
[global]
workgroup = GRUPODETRABAJO
netbios name = LINUXSERVER
server string = %h server (Samba %v)
interfaces = 192.168.1.40/24 10.4.0.2/24
encrypt passwords = Yes
printing = bsd
printcap name = /etc/printcap
load printers = yes
debug level = 3
deadtime = 1
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
os level = 65
preferred master = Yes
domain master = Yes
dns proxy = No
wins support = Yes
invalid users = root
nt acl support = No
Finally from the I have pressed "Start" -> "Run" and typed \\10.4.0.2 and
All the samba volumens appear
Thanks to all again,
Greetings from Spain, Im happy, things works and today is a Sunny day :-)
--
Emiliano Sutil García
Hello,
you can see, that the XP-Box use Port 445 for the connection to the SMB-Server.
Port 445 is in use of MS for File-Share since WIN2000
As far as i know, Samba only use 135, 137 ...
After a few seconds the XP-Box switch to this ports and trys to connect to the SMB-Server.
Have you restricted the interface for samba ??
Try this:
Change the IP in the lmhosts file to the 192.168.1.215..
CU
Robert
-----Ursprüngliche Nachricht-----
Von: Emiliano Sutil [mailto:emiliano@iranon.com]
Gesendet: Do 27.05.2004 10:27
An: suse-security(a)suse.com
Cc:
Betreff: Re: AW: AW: [suse-security] openvpn samba question (sshd keep alive cont..)
Rasp, Robert wrote:
>>>Try this:
>>>Change the IP in the lmhosts file to the 192.168.1.215..
>>>
>>>
>>>
>>>
>>>
>>This doesn´t work at all it trys to connect to my PC, and gives an error.
>>
>>
>
>I thought the 192.168.1.215 is the internal IP from your Server :-(
>Place the internal IP of your Server in the "lmhosts"
>
>
>
nothing, If I put the internal IP in the lmhosts I can´t reach by name
the server. Also all the services that works stop to work, because
this ip is interpreted as local to my subnet.
>The smb.conf seems to be ok.
>But i can see that you hava a WINS-Server.
>Have you confgured all your clients to use the LINUXSERVER as WINS-Server.
>With this option the networkbrowsing is much more faster....
>
>
>
No I haven´t configured that, in fact I don´t know how to configure that.
> -----Ursprüngliche Nachricht-----
> Von: Emiliano Sutil [mailto:emiliano@iranon.com]
> Gesendet: Do 27.05.2004 12:09
> An: Rasp, Robert
> Cc:
> Betreff: Re: AW: AW: AW: [suse-security] openvpn samba question (sshd keep alive cont..)
>
>
>
>
>
>
--
Emiliano Sutil García
ANÁLISIS Y DESARROLLO DE SOFTWARE S.L.
Urb. San Roque, 22
24540 Cacabelos (León)
España
email: emiliano(a)iranon.com
Telf. 902 100 103
Fax. 902 201 801