January 2002 - openSUSE Security - openSUSE Mailing Lists

Re: [suse-security] SuSEfirewall2 and NTP
by Igor Nichvolodin 17 Jan '02

17 Jan '02

> I tried to open my firewall up to NTP (client) using the > "FW_ALLOW_INCOMING_HIGHPORTS_UDP" in the" firewall2.rc.config" file. > This did not work. The problem is that when the NTP request is sent to > the server (dest port 123) the response was coming back with a source > port of 123 as well. The "FW_ALLOW_INCOMING_HIGHPORTS_UDP" permits NTP > replies on source ports 1024-65535. I fixed it by adding the following > rule to "firewall2-custom.rc.config"; > > iptables -A input_ext -j ACCEPT -m state --state ESTABLISHED,RELATED -p > udp --sport ntp --dport ntp > > (Opinions on the security of this rule welcome.) > > Is this a promblem with the NTP software/configuration on the client or > server or a problem with SuSEfirewall2? SuSEfirewall2 is commented as > follows, regarding the "FW_ALLOW_INCOMING_HIGHPORTS_UDP" option; > > # Common: "DNS" or "domain ntp", better is "yes" to be sure ... > > rickey Try something like this: FW_TRUSTED_NETS="... your.time.server.ip-address,udp,ntp" and FW_ALLOW_INCOMING_HIGHPORTS_UDP="... time" Igor

2 1

How many firewalls?
by Max Lindner 17 Jan '02

17 Jan '02

Hi! I want to set a up a DMZ in my school. The only thing I want to know, is: - Internet -> HARDWARE-ROUTER -> FW -> DMZ -> FW -> Intranet or - Internet | | Hardware-Router | | | FW DMZ _______/\______Intranet (I hope, this ascii art is good enough... :-/) Our school has no good connection and low traffic but this is for a skilled work (the german term is 'Facharbeit') and so I want a really secure thing (no, I won't cut the cable ;-D). Any comments or proposals? Thanks, Max

4 3

pers.firewall- rulechains get longer and longer
by Ekki Plicht 17 Jan '02

17 Jan '02

Hi list, as a newbie to Linux I decided to use SuSEpersonal-firewall for simplicity reasons. Works fine on a T-DSL line with dial-on-demand. To learn how the fw works i looked at the output of iptables -L . Now, after some days i looked again and found that the "forward" rules get longer and longer. I am not sure, but my guess is that for each dial-up a new line is added. The line is: Chain FORWARD (policy ACCEPT) target prot opt source destination TCPMSS tcp -- anywhere anywhere tcp flags:SYN,RST/SYN TCPMSS clamp to PMTU TCPMSS tcp -- anywhere anywhere tcp flags:SYN,RST/SYN TCPMSS clamp to PMTU and on and on, 40 lines at last count. Does anybody know the reason for this? Has this something to do with how the script for the pers. fw is invoked at each dial-up? Thanks, Ekki

2 1

Re: Re: [suse-security] Server shut down by hacker ??
by gerol＠web.de 17 Jan '02

17 Jan '02

Hi, i found out, that there are no entries about a shut down in /var/log/messages . is it normal for a hard shut down or is it a hacker? > > sorry if I am offtopic, but I am not sure why my co-located server shuts > > down abruptly. This is the second time, the first time it needed a file > > system check, and in the logs there was an entry that someone startet a > > X. auth (or so) ? > > You don't need to be sorry if you're offtopic, you need to stop writing > mails that are offtopic. > > > > I use Suse 7.2, kernel 2.4.7, proftpd 2.2.4rc2 (newest), apache 1.3.19, sendmail 9.1.2, sshd (prot 2 +1!!!) > > i alsouse a IDE RAID Controller from 3ware, which hasn't caused any trouble yet... > > We will issue a kernel announcement today or tomorrow. For now, install > 2.4.16 from ftp://ftp.suse.com/pub/suse/i386/update/7.2/kernel/ and see if > it goes away. > > My guess is that your 3ware controller and your disks suck too much > electric power from the power supply, or there is another hardware bug. > Security implications are possible, but why would a cracker reboot your > system? > > > > > Is this problem know to someone ? sorry, this is getting very annoying ;-( > > > > thanks so far. > > Gero > > Roman. > ________________________________________________________________ Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13

2 1

NETWORK SLOWDOWN
by Omppu 17 Jan '02

17 Jan '02

hello i have the following setup Internet | S0 -------------- | internet | | cisco router | -------------- | F0 195.165.91.1 mask 255.255.255.240 | | | ---------- ---------- | HUB |----------------| server | 195.165.91.3 mask 255.255.255.240 ---------- ---------- | | | 195.165.91.2 netmask 255.255.255.240 GW 195.165.91.1 -------------- | SuSE 7.3 | | |----------------| 195.165.91.129 netmask 255.255.255.192 -------------- | 195.165.91.193 netmask 255.255.255.192 | route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 195.165.91.0 * 255.255.255.240 U 0 0 0 eth0 195.165.91.0 * 255.255.255.240 U 0 0 0 eth0 195.165.91.192 * 255.255.255.192 U 0 0 0 eth2 195.165.91.128 * 255.255.255.192 U 0 0 0 eth1 default 195.165.91.1 0.0.0.0 UG 0 0 0 eth0 SuSE 7.3 running on a pentium3 550Mhz with 128mb ram and intel ethernet pro100+ network cards for some reason im getting some lags on connections going through the linux box, and the laggs become longer and worse when i startup the firewall. any ideas what is causing this and how it can be resolved??? regards O.

3 2

LOGparser--->html
by aliu 17 Jan '02

17 Jan '02

hi i search for a logparser which reads in the firewalllog and put a compact html page out thanks for help

2 1

Interesting sshd2 log = Thanks
by Webmaster 17 Jan '02

17 Jan '02

Sorry List, Scanning logs I found similar entries. What was unusual perhaps that the second comment "DNS lookup failed" was missing. Sorry for the trouble. Antal Jan 14 17:34:55 mand sshd2[159]: connection from "193.126.123.19" Jan 14 17:34:55 mand sshd2[31967]: DNS lookup failed for "193.126.123.19". Jan 14 17:35:01 mand sshd2[31967]: Local disconnected: Connection closed by remote host. Jan 14 17:35:01 mand sshd2[31967]: connection lost: 'Connection closed by remote host.' ++++++++++++++++++ Kreorg Oktatóközpont http://www.kreorg.hu kreorg(a)kreorg.hu Tel:+36-1-321-00-31 Fax:+36-1-397-27-80 GRID Erő a változáshoz.

1 0

Interesting sshd2 log
by Webmaster 17 Jan '02

17 Jan '02

Hi List, Let me ask your opinions on that ssh connection log below. What puzzles me is the difference between PIDs while there is a 10 sec time elapse between the two log entries. The PID[159] is a bootup root PID, the same since a month. The daily PIDs are high numbers. Strange, there is no IP at the disconnected lines, generally there is. Any ideas? Antal -------- Jan 16 18:26:57 mand sshd2[159]: connection from "24.27.53.63" Jan 16 18:27:08 mand sshd2[9141]: Local disconnected: Connection closed by remote host. Jan 16 18:27:08 mand sshd2[9141]: connection lost: 'Connection closed by remote host.' ++++++++++++++++++ Kreorg Oktatóközpont http://www.kreorg.hu kreorg(a)kreorg.hu Tel:+36-1-321-00-31 Fax:+36-1-397-27-80 GRID Erő a változáshoz.

1 0

SSH
by JW 16 Jan '02

16 Jan '02

Can anyone tell me if openssh-2.5.2 is vulnerable the crc32 compensation attack? Thanks. ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com

1 0

SuSE Security Announcement: at (SuSE-SA:2002:003)
by Roman Drahtmueller 16 Jan '02

16 Jan '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: at Announcement-ID: SuSE-SA:2002:003 Date: Wednesday, Jan 16th 2001 16:00 MET Affected SuSE versions: 6.4, 7.0, 7.1, 7.2, 7.3 Vulnerability Type: local privilege escalation Severity (1-10): 5 SuSE default package: yes Other affected systems: most Linux systems with the at package installed Content of this advisory: 1) security vulnerability resolved: at 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 The 'at' command reads commands from standard input for execution at a later time specified on the command line. If such an execution time is given in a carefully drafted (but wrong) format, the at command may crash as a result of a surplus call to free(). The cause of the crash is a heap corruption that is exploitable under certain circumstances since the /usr/bin/at command is installed setuid root. A temporary workaround against the bug is to disable the at command for non-root users by removing the setuid-bit from the /usr/bin/at command. As a permanent solution it is recommended to install the update packages as listed for download below. In addition to the fixed heap corruption, file handling security has been improved by adding the O_EXCL (exclusive) option to an open(2) system call inside the at(1) code. We thank zen-parse for reporting this vulnerability. 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. i386 Intel Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/ap1/at-3.1.8-459.i386.rpm db3d2bd38f81667dcece38d1c4a86725 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/at-3.1.8-459.src.rpm 82701057fc8ea3217800b0ab1e2e544b SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/ap1/at-3.1.8-458.i386.rpm 91b759e6a8d433273c5567ed26735690 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/at-3.1.8-458.src.rpm 3df6d6d708d4ef90515f6f1fbbdea5bf SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/a1/at-3.1.8-458.i386.rpm 73eb22d5c958c17e264fd31ec339b763 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/at-3.1.8-458.src.rpm 1303a1328f31313a62f5645f7cb476ef SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/at-3.1.8-459.i386.rpm 3179e64f87371d7864d1956ceb9bd020 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/at-3.1.8-459.src.rpm 67efafe83908ac53fc54acac9a0f056b SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/a1/at-3.1.8-458.i386.rpm aaffed7c302b9ec42885087296c6f0a1 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/at-3.1.8-458.src.rpm 374cf4374fbe1e66ab2e685aa0449034 Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/ap1/at-3.1.8-356.sparc.rpm ec76d45245ef917e22f5f1a863a89988 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/at-3.1.8-356.src.rpm 40de9490a06bd294ad6a7f90e682c0cd SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/a1/at-3.1.8-356.sparc.rpm 27f575762c0b1643008968a167324347 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/at-3.1.8-356.src.rpm 66546dc729e071039595a13d01feacfb SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/a1/at-3.1.8-357.sparc.rpm 98007292769f55e4239b6922157bfa13 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/at-3.1.8-357.src.rpm 2d20cdbb10680282596677aac3106f30 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/a1/at-3.1.8-360.alpha.rpm df71ebf25a2252637ee1421d08779b8d source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/at-3.1.8-360.src.rpm b8b3a4f80e0d19e0211131ca58c1e0fe SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/a1/at-3.1.8-361.alpha.rpm 0bc21b9ddc12746a17592fa74473bbf6 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/at-3.1.8-361.src.rpm 4d93aa10b426224936e3de357540ea49 SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/a1/at-3.1.8-361.alpha.rpm aeb76c2eb37f7e442c49c7ba3c5e44a5 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/at-3.1.8-361.src.rpm 6d783c34eb0b855a96736e58d67bc053 PPC Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/ap1/at-3.1.8-363.ppc.rpm 111bd6e813ef33265035b21d19776b49 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/at-3.1.8-363.src.rpm fa2ee9aca5b73009b1d9c90731265a19 SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/a1/at-3.1.8-362.ppc.rpm 868a1662f751823432d3d881edd371cd source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/at-3.1.8-362.src.rpm d759233bfc2ce230e1c46d2ec0f15a73 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/a1/at-3.1.8-362.ppc.rpm 7b12fe4b5f31434eb7cf3c0caae75811 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/at-3.1.8-362.src.rpm 4c6e2724bb76e08be66831ed85c60f85 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/a1/at-3.1.8-362.ppc.rpm 7ebc9a1fde97f5ac8226b9e17621a40b source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/at-3.1.8-362.src.rpm fa3c5e08703eb54b4f493de56ec837bb ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Linux Distributions and Workarounds: - clanlib dotslash(a)snosoft.com reported an environment variable copying buffer overflow in the clanlib package. If a program that is linked against the clanlib shared library is installed setuid or setgid, this error may lead to elevated privileges. In the case of SuSE Linux distributions, this is only the case for the methane package: It comes installed with a setgid bit to group "game", which is used to store highscores in group- writeable files. This setgid bit will be cleared in future releases of the SuSE Linux distribution. For already installed "methane" packages, we recommend to remove the setgid bit with the command chmod -s /usr/X11R6/bin/methane The methane package is not installed on SuSE systems by default, nor is the defective library "clanlib". - thttpd The thttpd daemon contained several off-by-one overflows. Due to internal organization of the variables affected by these overflows, they seem not exploitable. However, these bugs have been fixed. Please update to the newest thttpd packages. - pine The popular mail client "pine" was found vulnerable to an attack where shell metacharacters inside an URL could be used to execute arbitrary commands if pine passes the URL to an external viewer on the commandline. The pine packages on SuSE products are not vulnerable to this weakness because they contain a patch that works around this problem since it is not new. - xchat We are working on updates for the xchat packages in the SuSE Linux 7.0 and 7.1 distributions that are vulnerable to an encoding bug while receiving and decoding ctcp datagrams. This bug can lead an xchat IRC client to execute IRC protocol specific commands to an IRC server such as channel mode changes. ______________________________________________________________________________ 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> 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 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+GYkAlQMFEDe3O8IWkDf+zvyS FQEBAfkD/3GG5UgJj18UhYmh1gfjIlDcPAeqMwSytEHDENmHC+vlZQ/p0mT9tPiW tp34io54mwr+bLPN8l6B5GJNkbGvH6M+mO7R8Lj4nHL6pyAv3PQr83WyLHcaX7It Klj371/4yzKV6qpz43SGRK4MacLo2rNZ/dNej7lwPCtzCcFYwqkiiEYEEBECAAYF AjoaQqQACgkQx1KqMrDf94ArewCfWnTUDG5gNYkmHG4bYL8fQcizyA4An2eVo/n+ 3J2KRWSOhpAMsnMxtPbBmQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCk YS3yEKeueNWc+z/0Kvff4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP +Y0PFPboMvKx0FXl/A0dM+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR 8xocQSVCFxcwvwCglVcOQliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U 8c/yE/vdvpN6lF0tmFrKXBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0S cZqITuZC4CWxJa9GynBED3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEh ELBeGaPdNCcmfZ66rKUdG5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtB UVKn4zLUOf6aeBAoV6NMCC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOo AqajLfvkURHAeSsxXIoEmyW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1n KFvF+rQoU3VTRSBQYWNrYWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohc BBMRAgAcBQI57vSBBQkDwmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8s AJ98BgD40zw0GHJHIf6dNfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQ EQIABgUCOnBeUgAKCRCeQOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACe OO1HIbActAevk5MUBhNeLZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vf iUUE1VQnt+T/EYklES3tXXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEI SZxbzdXGnqIlcT08TzBUD9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9g TPSr+/fT3WeVnwJiQCQ30kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23p QUPAgJENDEqeU6iIO9Ot1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1y PqZd5CvvznYvB6bWBIpWcRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IX SzyohEJB6XG5+D0BuQINBDnu9JIQCACEkdBN6Mxf5WvqDWkcMRy6wnrd9DYJ8UUT mIT2iQf07tRUKJJ9v0JXfx2Z4d08IQSMNRaq4VgSe+PdYgIy0fbj23Via5/gO7fJ EpD2hd2f+pMnOWvH2rOOIbeYfuhzAc6BQjAKtmgR0ERUTafTM9Wb6F13CNZZNZfD qnFDP6L12w3z3F7FFXkz07Rs3AIto1ZfYZd4sCSpMr/0S5nLrHbIvGLp271hhQBe RmmoGEKO2JRelGgUJ2CUzOdtwDIKT0LbCpvaP8PVnYF5IFoYJIWRHqlEt5ucTXst Zy7vYjL6vTP4l5xs+LIOkNmPhqmfsgLzVo0UaLt80hOwc4NvDCOLAAMGB/9g+9V3 ORzw4LvO1pwRYJqfDKUq/EJ0rNMMD4N8RLpZRhKHKJUm9nNHLbksnlZwrbSTM5Lp C/U6sheLP+l0bLVoq0lmsCcUSyh+mY6PxWirLIWCn/IAZAGnXb6Zd6TtIJlGG6pq UN8QxGJYQnonl0uTJKHJENbI9sWHQdcTtBMc34gorHFCo1Bcvpnc1LFLrWn7mfoG x6INQjf3HGQpMXAWuSBQhzkazY6vaWFpa8bBJ+gKbBuySWzNm3rFtT5HRKMWpO+M 9bHp4d+puY0L1YwN1OMatcMMpcWnZpiWiR83oi32+xtWUY2U7Ae38mMag8zFbpeq PQUsDv9V7CAJ1dbriEwEGBECAAwFAjnu9JIFCQPCZwAACgkQqE7a6JyACspLIgCb BQd/++0pB9yZWDhqxHtTpdCXRsAAnik7bYHlTxQfohiXYsEJcWrDn7l8 =ojbD - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBPEWe7Hey5gA9JdPZAQGPCwf/QrDn2sd0oKT6gehLPdCxZqH7qluObAUV Kzkb0dLx47O6LeiX/TEo7ssx30Y2boLyGG6X1Hy/jlHk9+Lx864AW/9EHX+kXmJg iiRMfNoWTswZU4gqZWyemW/pRYVN7U62LhKbe/m7GVy3JpxPCDZZQi4oGLIN114K p50J86r2GoGEKeQfQi+cShndfohuaS1KA0U1H5O2gODrEsuGcXUfNyYq8MraS1qF knWzC+5FZZMAyoJ5Jr4AhYttrtuRoyRfS6z0gJkqeC0s+dUhNEEV/auGckuo2k4T A4F39QxnxlB220iItOedJPhj+dSgfe8IrJx2t4z2uNoXuqkIaSCnlA== =GPsQ -----END PGP SIGNATURE-----

1 0