Kastus wrote on Thu Jun 03 2004 - 19:44:15 CEST:
>
> On Wed, May 26, 2004 at 01:41:23PM +0200, Sebastian Krahmer wrote:
>>
>> 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.
>>
>
> This is about rsync-2.6.2-8.2, right?
>
> I've updated using YOU
> and now am not able to rsync large directories:
>
> rsync -av --delete /home/* /home.backup/
> building file list ... done
> rsync: connection unexpectedly closed (8 bytes read so far)
> rsync error: error in rsync protocol data stream (code 12)
> at io.c(342)
>
> The version shipped with 9.1 works just fine with the same directories.
>
> Was this update rushed in? Any fixes?
>
> Thanks, -Kastus
>
>--
Hi Kastus,
IIRC, both YOU and fou4s download the patch rpms
unless you tell them otherwise.
Have you tried the "unpatched" rsync-*.rpm
which is also available from the SuSE ftp servers ???
Might be worth a try.
Hope this helps,
Gar
--
__________________________________________________________________
Introducing the New Netscape Internet Service.
Only $9.95 a month -- Sign up today at http://isp.netscape.com/register
Netscape. Just the Net You Need.
New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp
On Friday 04 June 2004 11:58, Hans Halstrick wrote:
> I am out of office until 7-June (incl.) with limited access to my mail. In
> urgent matters please call me on my mobile
This is already the fifth auto-reply I get from this person today. People
using auto-replies on mailinglists should be shot (or do I need some coffee?)
> 0041 76 578 1560
>
> Regards,
> Hans
Please folks, this is exactly the reason why you should NOT send bounces in
reply to virusses. I'm very disappointed that SuSE is still not aware of the
implications of this annoying behaviour. To summarize, only send warnings to
authenticated senders otherwise you might be sending it to a spoofed sender
address.
At the same time it is a perfect example of the type of message (and the user)
I wrote about just over an hour ago. Obviously he is still connected to this
list, so I think it would be worthwile to run a scan who it is and to
unsubscribe him. As can be seen from the bounce message, the message
originated from pD951F606.dip.t-dialin.net [217.81.246.6] too. This system is
NOT supposed to send mail on behalf of the 'de-korte.org' domain. And I doubt
the HELO 'suse.com' is valid either.
As a side note, it is easy to drop this particular virus by using the Postfix
'smtpd_helo_restrictions' to drop all hosts claiming to be from within your
own domain, which you know, are not.
---------- Forwarded Message ----------
Subject: Undelivered Mail Returned to Sender
Date: Friday 04 June 2004 10:20
From: MAILER-DAEMON(a)suse.de (Mail Delivery System)
To: suse-security(a)de-korte.org
This is the Postfix program at host hermes.suse.de.
I'm sorry to have to inform you that the message returned
below could not be delivered to one or more destinations.
For further assistance, please send mail to <postmaster>
If you do so, please include this problem report. You can
delete your own text from the message returned below.
The Postfix program
<25866(a)suse.de>: unknown user: "25866"
-------------------------------------------------------
Encapsulated message
Received: from scanhost.suse.de (scanhost.suse.de [10.0.0.5])
by hermes.suse.de (Postfix) with ESMTP id 85C238C9D
for <25866(a)suse.de>; Fri, 4 Jun 2004 10:20:20 +0200 (CEST)
Received: by scanhost.suse.de (Postfix, from userid 0)
id 7B27951E5F; Fri, 4 Jun 2004 10:20:20 +0200 (CEST)
Delivered-To: virus-quarantine
X-Quarantine-id: <virus-20040604-101415-03775-17>
Received: from Cantor.suse.de (cantor.suse.de [195.135.220.2]) (using TLSv1
with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate
requested)
by hermes.suse.de (Postfix) with ESMTP id 953E669115
for <25866(a)suse.de>; Fri, 4 Jun 2004 10:13:46 +0200 (CEST)
Received: from suse.de (pD951F606.dip.t-dialin.net [217.81.246.6])
by Cantor.suse.de (Postfix) with ESMTP id 4B95668F3BE
for <25866(a)suse.de>; Fri, 4 Jun 2004 10:13:32 +0200 (CEST)
From: suse-security(a)de-korte.org
To: 25866(a)suse.de
Subject: Re: Your music
Date: Fri, 4 Jun 2004 10:26:56 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20040604081332.4B95668F3BE(a)Cantor.suse.de>
X-AMaViS-Alert: INFECTED, message contains virus: Worm.SomeFool.Gen-1
X-Converted-To-Plain-Text: from multipart/mixed by demime 1.1d
X-Converted-To-Plain-Text: Alternative section used was text/plain
Please have a look at the attached file.
[the SUSE virus scanner removed an attachment of type application/octet-stream
which had a name of mp3music.pif]
[if you need the message in its original form including all attachments,
please ask the SENDER for a version free of viruses]
End of encapsulated message
Can someone please unsubscribe the following address from the mailinglist? I
keep on getting this reply for every message posted here...
---------- Forwarded Message ----------
Subject: Re: Your Amazon.co.uk Inquiry
Date: Friday 04 June 2004 10:02
From: Amazon.co.uk <nobody(a)amazon.co.uk>
To: Arjen de Korte <suse-security(a)de-korte.org>
Greetings from Amazon.co.uk.
Please note: this is an automated response, but it contains
information that should help to answer your questions. Please do not
reply to this e-mail, as we are not able to respond personally to
messages sent to this address.
To better serve you, we've made it easy to find answers and make
changes quickly and efficiently through our Web site.
To view your account history, change the delivery address or payment
method, cancel an item or make other changes to undispatched orders or
to your account, visit:
http://www.amazon.co.uk/youraccount
To find answers to questions about our delivery rates, returns policy
and how to use any of our services, visit our online help desk at:
http://www.amazon.co.uk/helpdesk
If you have experienced difficulties in reading an HTML e-mail we have
sent to you, you may wish to set your communication preferences to
text-only, so that we will no longer send you e-mail in HTML
format. You may do this either by visiting "Your Account" at the top
of any page and selecting "Update your communication preferences" or
by simply clicking on the URL below:
http://www.amazon.co.uk/exec/obidos/account-access-login
We hope our online resources meet all your needs. If you've explored
the above links but still need to get in touch with us, you will find
all our contact details in the online help guide.
We appreciate your business and look forward to seeing you again soon
at Amazon.co.uk.
Warmest regards,
Amazon.co.uk Customer Services
http://www.amazon.co.uk/
**********************************************************************
The information contained in this e-mail message and any attachments
is intended for the addressee only and may be confidential. If you are
not the addressee, you must not read, use, pass on or copy this
message or any attachments or disclose its contents to anyone. If you
have received this e-mail in error, please notify us by returning the
e-mail and delete all copies of this message including any
attachments. E-mails cannot be guaranteed to be secure or error free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete or contain viruses. The sender does not
accept any liability for any errors or omissions in the contents of
this message, which arise as a result of e-mail transmission. If
verification is required please request a hard copy version. Please be
aware that the contents of any e-mails sent to Amazon.co.uk may be
monitored and reviewed in accordance with lawful business practice.
**********************************************************************
-------------------------------------------------------
-----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-----
It may not be a firewall rules problem. ipchains may not be enabled. It is
also possible that the echo responder is not enabled.
At 9:03 PM 6/3/04, Joerg Bruenner wrote:
>[...]
>Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target prot opt in out source
> destination
>
>Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target prot opt in out source
> destination
>
>Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target prot opt in out source
> destination
Looks like you don't have any rules, but it also doesn't make any sense
that if ipchains is working you then wouldn't have any packets.
>Ping from the firewall-box to box A will be answered.
>A ping from box A to the firewall reaches but will
>not be answered.
>
>What do I have to do ?
Make sure you've got the ping service enabled on the box you're trying to ping!
--
Fred Morris
fredm3047(a)inwa.net (I-ACK)
Hi,
my firewall looks like:
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Ping from the firewall-box to box A will be answered.
A ping from box A to the firewall reaches but will
not be answered.
What do I have to do ?
Thanks a lot for help
Joerg
Mit schönen Grüßen von Yahoo! Mail - http://mail.yahoo.de