June 2001 - openSUSE Security - openSUSE Mailing Lists

SSH Authentication
by Joao Reis 18 Nov '02

18 Nov '02

Hi! I implemented a ssh conection from the outside to my intranet. This ssh requires a username and a password. In terms of security what is more secure: require authentication (username and password) or having the public key of each user that connects to our intranet in the authorized public key lists (in this case there is no need for username and password)? In the second case there is no need of authentication and only the users wich have the public keys in the list are allowed to enter in my intranet. This second solution is a good solution or that brings other security problems ? Thanks. -- Farewell. "Keep your friends close, but your enemies closer." "Do or do not. There is no try" - Yoda João Reis -------------------------------------------------------

2 1

PGP keyserv
by jochen mader 18 Jul '01

18 Jul '01

Hey, I've been playing around with GPG for some time now and I'd like to install a keyserver on our server to allow people to exchange their keys easily. Which servers would you suggest to use?

2 1

RE: [suse-security] IPSec system design questions (slightly OT)
by Ed 11 Jul '01

11 Jul '01

I would appreciate comments on some IPSec design issues. A transportation manufacture recently requested proposals for a Linux based system to put Internet and email services on their vehicles. This system would let passengers plug a laptop into the on board network. A number of protocols were specified including IPSec. They also specified Linux kernel 2.4.x. It seemed to me that they intended IPSec to be used from transportation vehicle to satellite to fixed server. The VP of Technology here has recently discussed using IPSec on board vehicle from web server, email server and file server to passenger seats - typically many hundreds of passengers. The transportation manufacture specified: "The file server will not preclude a user from initiating and completing a supported VPN connection from their user device through the transportation manufacturer network using the IPSec and PPTP protocol, as a minimum. The system should allow the user to switch between IPSec VPN and non-VPN without need of rebooting the laptop. The system will only pass IP based protocols between the laptop passenger interface and the file server. Passenger laptops will be assigned default gateway address via DHCP. The default gateway should reside in the server. The system will by default, route user outbound packets to a configurable gateway." Is it feasible to support IPSec from a passenger's laptop when implementations of IPSec vary and either ESP or AH modes might be used? If feasible what performance hit would be involved? I have heard estimates of 40% when encryption is used (mileage may vary I suppose based on CPU speed and resources). I assumed that a "default gateway at the server" implied that the IPSec pipe started or ended there. Since the transportation manufacturer called out other security requirements to the passenger seat, I assumed that IPSec to the seat was not required. Examples of requested security: "Multiple passengers will not be connected to shared physical media. Laptop users will not be permitted to view packets from another user's network session. Each passenger's laptop's user interface will be isolated to its own link layer subnetwork. The passenger laptop will not be able to access unauthorized IP address. The system will be immune to DoS attacks. The server will ensure that passenger laptop's can only pass packets with that user's assigned IP address." My main question are, 1) "Does the transportation manufacturer really want IPSec extended directly to the passenger's laptop?" 2) "Would it even be feasible to automate re configuration of IPSec software running on a passenger laptop to avoid compatibility issues?" 3) "What would the performance cost be of running ESP or AH IPSec on a laptop that might also be viewing an MPEG2 movie, web browsing or playing a game?" I would appreciate any opinions you care to offer. The job you save may be my own. <s> Thanks, Ed

5 6

setting up firewall in 7.1
by twowitchesinthelight＠btinternet.com 03 Jul '01

03 Jul '01

Hi All, Another newbie question. I edited my inetd.conf and commented out ftp, telnet, shell, login, pop3, finger and swat and rebooted. Everything seems to work ok. nmap -sT -v my ip shows these 22 ssh 37 time 111 sunrpc 515 printer 1024 kdm 6000 X11 nmap -sU my ip shows these 37 time 111 sunrpc 517 talk 518 ntalk Questions are these. First, is what I commented out ok? secondly, is it safe to comment out talk, ntalk, and time in inetd.conf as well? Secondly...how about ssh,sunrpc,printer and X11? Is it safe and where do I shut them down at? If you could just give me a site that would explain this to me I would be very grateful. As I said, I am new and just don't want to make any mistakes configuring or to take an unsecured machine out on the net. Thanks in advance, Dallam

3 2

AW: [suse-security] Ipsec + firewall
by Schulz, Wolfgang 03 Jul '01

03 Jul '01

Hi! The problem with the firewall + IPsec is still not solved. To split the setup problems I have tried to configure different test environment: a) Only 2 IPsec gateways b) 2 IPsec gateways with the firewall script - no masquerading c) 2 IPsec gateways with the firewall script with maquerading Setup a) is working but with setup b) I have already problems: The tunnel is established but I still cannot ping to the net on the other side. I checked the firewall.log for denied packets but couldn't find any entry. Also another strange phenomenon: If I boot the machine with the firewall script and stop afterwards the firewall script by hand the ipsec connection doesn't work too. What could be the problem with my setup. Thanks for your help Wolfgang > -----Ursprüngliche Nachricht----- > Von: Tobias Gewinner [mailto:crt@tmt.de] > Gesendet: Dienstag, 19. Juni 2001 23:32 > An: suse-security(a)suse.com > Betreff: Re: [suse-security] Ipsec + firewall > > > On Tue, Jun 19, 2001 at 05:55:09PM +0200, Schulz, Wolfgang wrote: > > Hi list! > > > > As soon as we start the firewall script (Version 4.1) ipsec > doesn't work > > anymore. > > I remember having the same problem in the past. AFAIK the > firewalls must > accept incoming requests from the outside on port 500/UDP. Also the > firewall doesn't know the net behind his partner, so any input from > these IPs to the internal net is denied. > > I remember that I set the following ipchains rules (or something like > that) manually on both machines: > > On firewall A this (may have) looked like > > ipchains -I forward -b -s [local net B] -d [local net A] -j ACCEPT > ipchains -I input -b -s [local net B] -d [local net A] -j ACCEPT > ipchains -I output -b -s [local net B] -d [local net A] -j ACCEPT > > and on firewall B you must swap the networks, of course ;-) > > After that it worked fine for me. I think you can set these rules > in /etc/rc.config.de/firewall-custom.rc.config > > Greetings! > -- > ----------------------------------------------------------------- > Tobias Gewinner <gewinner(a)tmt.de> > Fachinformatiker i.A. TMT InterNETworks GmbH > Phone: +49921560716-0 Maxstrasse 4 > Fax: +49921560716-18 D-95444 Bayreuth > ----------------------------------------------------------------- > > -- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com >

2 1

Re: [suse-security] iptables and squid
by Stefan_Walther＠gehag-dsk.de 01 Jul '01

01 Jul '01

DIRK WROTE: Helo Stefan, helo folks, I tried that one but it`s the same thing. Realy curious is, when the firewall script starts I get an error message with reference to "Bad argument squid" even I had declared in /etc/services. The same one, when I use the port nummer."Bad argument 3128" Any idea??? Thanks and regards Dirk Hello Dirk, hello folks, I don't know if it works but you can try this, maybe you can send me your log and the full error listed at you monitor: #SQUID internal lan iptables -A INPUT -i $IF_LAN -p tcp --dport 3128 -j ACCEPT iptables -A OUTPUT -i $IF_LAN -p tcp --sport 3128 -j ACCEPT #HTTP iptables -A INPUT -i $IF_WAN -p tcp --dport 80 -j ACCEPT iptables -A OUTPUT -i $IF_WAN -p tcp --sport 80 -j ACCEPT #DNS iptables -A INPUT -i $IF_WAN -p udp --sport 1024:65535 --dport 53 -j ACCEPT iptables -A OUTPUT -o $IF_WAN -p udp --dport 53 --sport 1024:65535 -j ACCEPT iptables -A INPUT -i $IF_WAN -p tcp --sport 1024:65535 --dport 53 -j ACCEPT iptables -A OUTPUT -o $IF_WAN -p tcp --dport 53 --sport 1024:65535 -j ACCEPT just try this (use the portnumbers not names in /etc/services). if this doesn't work, you should try to install proxy and firewall at to different machines. MfG. Stefan Walther stefan_walther(a)gehag-dsk.de dienst.: +4930/89786448 Funk: +49172/3943961

2 1

How to shut down firewall
by Steve Collins 30 Jun '01

30 Jun '01

I have a standard install running SUSE 7.1 on PC hardware. It uses a 56k modem to talk to Earthlink via ppp. I believe it has firewall running since (1) I can see a couple of messages about "personal-firewall" go by during the boot sequence and (2) if I try to telnet or ssh into the box from the internet, I see messages in /var/log/messages about the connect being rejected. I would like to temporarily disable enough of the protection to allow incoming ssh, telnet, and ftp connections. I tried modifying settings in /etc/rc.config.d/firewall.rc.config to allow the desired services, but to no apparent effect. I then tried to disable the firewall completely but found that my rc.config already had the line START_FW ="no" and yet some firewall clearly is running. Any pointers to definitive docs on the SUSE 7.1 firewall setup? I don't seem to be able to figure out what I need from the printed manuals. Haben Sie viel Spa� Steve Collins __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/

3 2

Re: [suse-security] SuSEfirewall 2.1 and NetMeeting 3.01
by michael.ryan＠storm.ie 29 Jun '01

29 Jun '01

Ok, I have added the ip_masq_h323.o module and re-started masquerading to load the module. SuSEfirewall is still in place as before. I can now use NetMeeting 3.01 on a PC to connect to a hosted meeting outside the firewall. My question now is how do I allow external NetMeeting clients connect to a NetMeeting host on our internal/private network. Any help much appreciated :) MR Torsten Mueller To: michael.ryan(a)storm.ie <torsten@arch cc: suse-security(a)suse.com esoft.de> Subject: Re: [suse-security] SuSEfirewall 2.1 and NetMeeting 3.01 06/29/2001 12:41 PM Hey, i use a setup with a netmeeting kernel module and portforwarding. Look at the masquearding howto, there's the lnk to the module. Greetings Torsten michael.ryan(a)storm.ie schrieb: > > Trying to allow external sources connect to a machine on our private > network which is acting as a NetMeeting host. > Gateway is a SuSE 6.4 box, ip masquerading up and running SuSE firewall 2.1 > Anyone done this before? any advice on how this can be done securely? > > tnx in advance, > > MR > > -- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com

2 1

NFS problem
by Selcuk Ozturk 29 Jun '01

29 Jun '01

Hi, I just upgraded my Suse 7.0 2.2.16 kernel server to 2.2.19 kernel. Everything seems to be working fine except an NFS quirk. When I try to mount the nfs shares on this machine from my Sun Solaris 7 server with the automounter, I am getting a "Permission denied" error and fail. Looking at the log on the Sun server I see: automountd[5391]: poseidon server not responding: RPC: Pro gram/version mismatch on the Linux log: Jun 28 09:54:33 poseidon mountd[419]: export request from x.x.x.x When I use the mount command like "mount poseidon:/ /mnt/tmp" then it works. But, I see in the Linux servers log: Jun 28 09:58:14 poseidon kernel: svc: unknown program 100227 (me 100003) I am using knfsd. Anybody know any fix? TIA Selcuk

2 3

SuSE Security Announcement: xinetd
by Sebastian Krahmer 29 Jun '01

29 Jun '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: xinetd Announcement-ID: SuSE-SA:2001:022 Date: Friday, June 29th 2001, 13:26:55 CEST Affected SuSE versions: (6.0, 6.1, 6.2), 6.3, 6.4, 7.0, 7.1, 7.2 Vulnerability Type: remote code execution Severity (1-10): 7 SuSE default package: yes Other affected systems: All systems using xinetd Content of this advisory: 1) security vulnerability resolved: xinetd buffer-overflows problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Zen-parse has reported a bug to Bugtraq which allows remote attackers to overflow a buffer in the logging routine of xinetd. During investigation we found that more problems exist within xinetd. Xinetd provides its own string-handling (snprintf()-like functions) routines and fails to handle length arguments of 0 properly. Instead of an immediate return it assumes 'no limit' for writing characters to the target-buffer. This can lead to overflows and arbitrary remote code-execution. Additionally xinetd now sets the correct umask before starting other deamons. Please update the packages immediately, kill the old deamon and start the new xinetd deamon with the /etc/rc.d/xinetd start command again if you need it running. Regardless of the bugs in xinetd, please make sure you only run as many services as needed. i386 Intel Platform: SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/xinetd-2.1.8.8p3-139.i386.rpm a8122710a857e49a356b0786c8aad9eb source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/xinetd-2.1.8.8p3-139.src.rpm 90187bd35f931f07ba72b54c16c1549c SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/xinetd-2.1.8.8p3-140.i386.rpm 346868fe76e17d17d87dadbac4c032bb source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/xinetd-2.1.8.8p3-140.src.rpm 6656be9789888da5b1b37dc1aa9c69a9 SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/xinetd-2.1.8.8p3-140.i386.rpm ff001b856db620213608dac1c88ebfbe source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/xinetd-2.1.8.8p3-140.src.rpm 627d2f09d9d4607f31e1902eee4e0cb5 SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/xinetd-2.1.8.8p3-139.i386.rpm ef4697d57a6ceb5e6a55bde51268b92a source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/xinetd-2.1.8.8p3-139.src.rpm 1384b48ed19204324d4a8c2f75d3ea20 SuSE-6.3 ftp://ftp.suse.com/pub/suse/i386/update/6.3/n1/xinetd-2.1.8.8p3-141.i386.rpm 3c29917f0688aa7509f98b0a00a38eed source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.3/zq1/xinetd-2.1.8.8p3-141.src.rpm b7f8cc1e5a7d3c2f6c56040c327a4b20 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/xinetd-2.1.8.8p3-89.sparc.r… a78dd53e2da211b8822b4ca86359a6e0 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/xinetd-2.1.8.8p3-89.src.rpm 9b0acb0dacee2962f19057de43d9f421 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/xinetd-2.1.8.8p3-96.alpha.rpm bb2b45d56d2cf54733a20561c8a8e440 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/xinetd-2.1.8.8p3-96.src.rpm 60610276aba8c103a43a40ea0366f675 SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/xinetd-2.1.8.8p3-96.alpha.rpm 1e4f0685f380db64025837685f8e79c2 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/xinetd-2.1.8.8p3-96.src.rpm addfd497500387b4de4e2c77ff226e01 SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/n1/xinetd-2.1.8.8p3-95.alpha.rpm f39287594d3297d2625f3878be6b7d98 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/xinetd-2.1.8.8p3-95.src.rpm ea727667791cd774a5df8bcb5b8b2870 SuSE-6.3 ftp://ftp.suse.com/pub/suse/axp/update/6.3/n1/xinetd-2.1.8.8p3-95.alpha.rpm 364120a5e0ba13587efba8c082faafa0 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.3/zq1/xinetd-2.1.8.8p3-95.src.rpm 08c540c506809a9a5b080aa21fe97406 PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/xinetd-2.1.8.8p3-102.ppc.rpm b73446661fe3f5967acd0242e83fb815 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/xinetd-2.1.8.8p3-102.src.rpm c89cb923d3c837e50e7f2efc2c9708d2 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/xinetd-2.1.8.8p3-101.ppc.rpm 01fec52a269c456636bcda0d8401b639 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/xinetd-2.1.8.8p3-101.src.rpm f91f365e3cbedc3de52aab7667db97b2 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/xinetd-2.1.8.8p3-101.ppc.rpm ed8e343b428fe812502195a15d9c4219 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/xinetd-2.1.8.8p3-101.src.rpm a340276cec8a5dedcbcd29e199bef6a1 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - rxvt The rxvt program contains a buffer-overflow which allows an attacker to locally execute arbitrary code under a different group-id. Please update to the newest rxvt packages. - dqs The dsh-program, shipped with the dqs package contains a buffer-overflow which allows local attackers to execute arbitrary code as root. Please update to the newest packages. - pcp A /tmp - race has been found in the pcp package which allows a local attacker to escalate his priviledges. Affected versions: 7.1, 7.2. We thank Mark Goodwin and Keith Owens from SGI who quickly responded to SuSE in this issue and who released a fixed version of the SGI Performance Co-Pilot in response to the security problem. Future SuSE Linux releases will include the most recent version of the package. Workaround: chmod a-s `rpm -ql pcp` /nosuchfile update-package does the same. ______________________________________________________________________________ 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 uninstalled 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 toplevel 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 annoucements 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>. The <security(a)suse.com> 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 cleartext signature shows proof of the authenticity of the text. SuSE GmbH 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 mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CohGBBARAgAGBQI7HmHDAAoJEJ5A4xAACqukTlQAoI4QzP9yjPohY7OU F7J3eKBTzp25AJ42BmtSd3pvm5ldmognWF3Trhp+GZkBogQ57vSBEQQAk/GN+ftr 7+DBlSoixDDpfRnUk+jApGEt8hCnrnjVnPs/9Cr33+CXLQbILOO7Y5oiPbJdHh45 t4E0fKyLVzDerCRFB1swz/mNDxT26DLysdBV5fwNHTPhxa67goAZVrehQPqJEckk IpYriOaYcKpF3n5fQIZMEfMaHEElQhcXML8AoJVXDkJYh7vI8EUB8ZURNLZMEECN A/sH0MCnb4Q6ZcRyeZ3+1PHP8hP73b6TepRdLZhaylwVF/iu7uIn62ZUL4//NTOC DY7V63qg4iba/fUbOsWtEnGaiE7mQuAlsSWvRspwRA9/g9rdVf3/JdLJrLmKBThe yG+PSJE3W7cAE4ZWafGxIRCwXhmj3TQnJn2euqylHRubEQP/aL53NZK0kBdvrKgf f6O8Of6tqoss8Dkk55I7QVFSp+My1Dn+mngQKFejTAgtyo/WmR3wPjQ9HoT2lRiY I2lTRYT4uMdHuwVC3b4DqAKmoy375FERwHkrMVyKBJslv8QtbAWw5A1CAUseaHo+ 91wmYJ4/4p6YUahqbG/tZyhbxfq0KFN1U0UgUGFja2FnZSBTaWduaW5nIEtleSA8 YnVpbGRAc3VzZS5kZT6IXAQTEQIAHAUCOe70gQUJA8JnAAQLCgMEAxUDAgMWAgEC F4AACgkQqE7a6JyACspfLACffAYA+NM8NBhyRyH+nTX58CNjwLIAoIx9fj52BJe0 xY7WbKoXs1+72b2AiEYEEBECAAYFAjpwXlIACgkQnkDjEAAKq6TczgCgi+ddhWb7 +FWcfeE6WwPZccqAHowAnjjtRyGwHLQHr5OTFAYTXi2Wv6jNiQEVAwUQOnBgb3ey 5gA9JdPZAQE1pwf/QJ+b34lFBNVUJ7fk/xGJJREt7V12iSafaRzGuH8xWvIz1bb+ VARxnnt16FDQ1cDNjoEhCEmcW83Vxp6iJXE9PE8wVA/Yue/bon5JS7J69+UiQ2eq 2pudfwljp52lYVM53jgPYEz0q/v3091nlZ8CYkAkN9JDS1lV1gEzJ7J0+POngDpU +lDQT2EC6VKaxeWK8pNt6UFDwICRDQxKnlOoiDvTrdWT7QdJZ4sPv8Qotdw9+tKN bWQ2DqdIRxyTdw9xDfAtcj6mXeQr7852Lwem1gSKVnEYHZ9g1FTJqVOutY8KhpUc 9RfOCRv8XuIxrs4KSbfSF0s8qIRCQelxufg9AbkCDQQ57vSSEAgAhJHQTejMX+Vr 6g1pHDEcusJ63fQ2CfFFE5iE9okH9O7UVCiSfb9CV38dmeHdPCEEjDUWquFYEnvj 3WICMtH249t1Ymuf4Du3yRKQ9oXdn/qTJzlrx9qzjiG3mH7ocwHOgUIwCrZoEdBE VE2n0zPVm+hddwjWWTWXw6pxQz+i9dsN89xexRV5M9O0bNwCLaNWX2GXeLAkqTK/ 9EuZy6x2yLxi6du9YYUAXkZpqBhCjtiUXpRoFCdglMznbcAyCk9C2wqb2j/D1Z2B eSBaGCSFkR6pRLebnE17LWcu72Iy+r0z+JecbPiyDpDZj4apn7IC81aNFGi7fNIT sHODbwwjiwADBgf/YPvVdzkc8OC7ztacEWCanwylKvxCdKzTDA+DfES6WUYShyiV JvZzRy25LJ5WcK20kzOS6Qv1OrIXiz/pdGy1aKtJZrAnFEsofpmOj8VoqyyFgp/y AGQBp12+mXek7SCZRhuqalDfEMRiWEJ6J5dLkyShyRDWyPbFh0HXE7QTHN+IKKxx QqNQXL6Z3NSxS61p+5n6BseiDUI39xxkKTFwFrkgUIc5Gs2Or2lhaWvGwSfoCmwb sklszZt6xbU+R0SjFqTvjPWx6eHfqbmNC9WMDdTjGrXDDKXFp2aYlokfN6It9vsb VlGNlOwHt/JjGoPMxW6Xqj0FLA7/VewgCdXW64hMBBgRAgAMBQI57vSSBQkDwmcA AAoJEKhO2uicgArKSyIAmwUHf/vtKQfcmVg4asR7U6XQl0bAAJ4pO22B5U8UH6IY l2LBCXFqw5+5fA== =Jnnf - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOzxlG3ey5gA9JdPZAQHe3wf/fyRLvSPGLGV1KQQed4eBqqXSxJgZBskB FVgCYtYFUTbcg0cSRjE7yRp1qBYg0jeKLf1PqNoDt+GcVR2HbsG3cvmyW/8ZZUiP tfgd/7lKqDyYBYMMmSOxf16AqUwHp8sVihmBkE8UGKy/2EIu4UBzlMaD4bkbGB+P /T/L5NjIct/yoTKVbksJmQeEW03XfXLG9a9X1LXS/4oR030Rco1I3dVAjHsGkwj/ Ya9zlwz7DfZCOhdeqD5LiCApbzFcn4fRxofyhp/M2DkTQp3650yp0H2/nGBZJ3fH davxTMzZ7m34oC2cTcOMoDeYDjQRX2eYI3bQKlE50v9x/n5XLbfAmg== =vVay -----END PGP SIGNATURE----- -- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer(a)suse.de - SuSE Security Team ~

1 0