April 2005 - openSUSE Security - openSUSE Mailing Lists

Problems setting up key based ssh access to suse 9.2 ...
by Robert Rozman 14 Apr '05

14 Apr '05

Hi, I have problems setting up rsa based ssh access to suse 9.2 machine. I did this: ssh-keygen -t dsa -C 'root@voipy' cat .ssh/id_dsa.pub >> .ssh/authorized_keys and then corrected /etc/ssh/sshd_config (at the end of email). I did /etc/init.d/sshd restart and I can still log in in old fashioned way with username and password.... I can login also with private key (but it asks for normal user password instead of passphrase of the key??), but I'd like to eliminate old fasioned way... What am I doing wrong ? Thanks in advance, regards, Rob. -----------------------------------------------sshd_config---------------------------------------------------------------- $OpenBSD: sshd_config,v 1.69 2004/05/23 23:59:53 dtucker Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for more information. # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin # The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options change a # default value. #Port 22 #Protocol 2,1 #ListenAddress 0.0.0.0 #ListenAddress :: # HostKey for protocol version 1 #HostKey /etc/ssh/ssh_host_key # HostKeys for protocol version 2 #HostKey /etc/ssh/ssh_host_rsa_key #HostKey /etc/ssh/ssh_host_dsa_key # Lifetime and size of ephemeral version 1 server key #KeyRegenerationInterval 1h #ServerKeyBits 768 # Logging #obsoletes QuietMode and FascistLogging #SyslogFacility AUTH #LogLevel INFO # Authentication: #LoginGraceTime 2m PermitRootLogin yes #StrictModes yes #MaxAuthTries 6 RSAAuthentication yes PubkeyAuthentication yes AuthorizedKeysFile .ssh/authorized_keys # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts RhostsRSAAuthentication no # similar for protocol version 2 HostbasedAuthentication no # Change to yes if you don't trust ~/.ssh/known_hosts for # RhostsRSAAuthentication and HostbasedAuthentication IgnoreUserKnownHosts yes # Don't read the user's ~/.rhosts and ~/.shosts files IgnoreRhosts yes # To disable tunneled clear text passwords, change to no here! PasswordAuthentication no PermitEmptyPasswords no # Change to no to disable s/key passwords ChallengeResponseAuthentication yes # Kerberos options #KerberosAuthentication no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes #KerberosGetAFSToken no # GSSAPI options #GSSAPIAuthentication no #GSSAPICleanupCredentials yes # Set this to 'yes' to enable support for the deprecated 'gssapi' authentication # mechanism to OpenSSH 3.8p1. The newer 'gssapi-with-mic' mechanism is included # in this release. The use of 'gssapi' is deprecated due to the presence of # potential man-in-the-middle attacks, which 'gssapi-with-mic' is not susceptible to. #GSSAPIEnableMITMAttack no # Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication mechanism. # Depending on your PAM configuration, this may bypass the setting of # PasswordAuthentication, PermitEmptyPasswords, and # "PermitRootLogin without-password". If you just want the PAM account and # session checks to run without PAM authentication, then enable this but set # ChallengeResponseAuthentication=no UsePAM yes #AllowTcpForwarding yes #GatewayPorts no #X11Forwarding yes #X11DisplayOffset 10 #X11UseLocalhost yes #PrintMotd yes #PrintLastLog yes #TCPKeepAlive yes #UseLogin no #UsePrivilegeSeparation yes #PermitUserEnvironment no #Compression yes #ClientAliveInterval 0 #ClientAliveCountMax 3 #UseDNS yes #PidFile /var/run/sshd.pid #MaxStartups 10 # no default banner path #Banner /some/path # override default of no subsystems Subsystem sftp /usr/lib/ssh/sftp-server

3 2

Re: [suse-security] Problems setting up key based ssh access to suse 9.2 ...
by Robert Rozman 14 Apr '05

14 Apr '05

Hi, yes I cannot login in username/password way, but also cannot login with key.... Is problem if I use keys that were generated in Linux on Windows clients (winscp, putty) ? I get this : Authentication log (see session log for details): Using username "root". Unable to use key file "C:\robi\TINIA\ASTERISK_development\Astera 2\id_dsa" (OpenSSH SSH2 private key) No supported authentication methods left to try! Connection has been unexpectedly closed. Server sent command exit status 0. Any advice ? regards, Rob. ----- Original Message ----- From: "Christian Volkmann" <dummy100(a)cv-sv.de> To: "Robert Rozman" <rozman(a)fri.uni-lj.si> Sent: Thursday, April 14, 2005 2:54 AM Subject: re: [suse-security] Problems setting up key based ssh access to suse 9.2 ... > Hi, I am read only to the list. > > you might try to turn this parameter off: > > # Set this to 'yes' to enable PAM authentication, account processing, > # and session processing. If this is enabled, PAM authentication will > # be allowed through the ChallengeResponseAuthentication mechanism. > # Depending on your PAM configuration, this may bypass the setting of > # PasswordAuthentication, PermitEmptyPasswords, and > # "PermitRootLogin without-password". If you just want the PAM account and > # session checks to run without PAM authentication, then enable this but > set > # ChallengeResponseAuthentication=no > UsePAM yes > > Please post to the list if you have success. > > Best regards, > > Christian

1 1

how to do switching between two gateways
by Markus Feilner 13 Apr '05

13 Apr '05

Hello list, we have two dsl gateways with two DSL lines. One line is used for VPN, the other for the rest. I want to test the availability of both lines and switch routing to the other while line one is not available, and back when everything works again. I have read about heartbeat and linux-ha, it works fine, but not for that purpose. Or did I miss something? How would you do that? Any help appreciated! Thanks! -- Mit freundlichen Grüßen Markus Feilner --------------------------- Bitte beachten Sie unsere neuen Adressdaten! Vielen Dank. --------------------------- Feilner IT Linux & GIS Linux Solutions, Training, Seminare und Workshops - auch Inhouse Beraiterweg 4 93047 Regensburg fon +49 941 9465243 fax +49 941 9465244 mobil + +49 170 3027092 mail mfeilner(a)feilner-it.net web http://www.feilner-it.net

3 2

RE: [suse-security] how to do switching between two gateways
by Matt T. Duval 12 Apr '05

12 Apr '05

I would use a commercial box like F5 or radware (sub 10K). If that is not an option, you could use a script that pings a host or hosts and then makes routing changes based on the return. AIX also has a dead gateway detection routine, dunno if this is in Linux. Thank you, Matt Duval Sr. Systems Engineer HealthTrans www.healthtrans.com (720) 493-8252 6061 South Willow Drive Suite 125 Greenwood Village, CO 80111 "Transforming Healthcare, One Transaction At A Time" -----Original Message----- From: Bill.Light(a)kp.org [mailto:Bill.Light@kp.org] Sent: Tuesday, April 12, 2005 11:17 AM To: suse-security(a)suse.com Subject: Re: [suse-security] how to do switching between two gateways Hello list, we have two dsl gateways with two DSL lines. One line is used for VPN, the other for the rest. I want to test the availability of both lines and switch routing to the other while line one is not available, and back when everything works again. I have read about heartbeat and linux-ha, it works fine, but not for that purpose. Or did I miss something? How would you do that? Any help appreciated! Thanks! ===================================== Take a look at http://www.lartc.org/ Lots of goodies that address what you want.

1 0

help: iproute2 portbased routing (in combination with heartbeat)
by Markus Feilner 12 Apr '05

12 Apr '05

Hello List, I need some help about iproute2... I have a linux router / firewall connected via two dsl lines (one fast, one flat) to the internet. heartbeat and linux-ha seem to switch flawlessly when one line disconnects but: [ now comes the hard part: ] I want to forward all our VPN traffic (one UDP port, e.g. 6000) via the fast line. [if this line is down, linux-ha should switch routing, to the other line, but thats another little problem] I did not manage up to now to have the linux router do port-based routing. (even though i read LARTC howto and many other docs.) I know: 1) iptables -t mangle "tags" packets 2) a routing table is added with ip route 3) ip rule add fwmark 4 table should "sort" the packages to the routing tables According to http://www.linux-ip.net/html/adv-multi-internet.html that should be all. But it's not working - why? Is there a mistake in the document? Are there any steps i forgot? -- Mit freundlichen Grüßen Markus Feilner -------------------------- Feilner IT Linux & GIS Linux Solutions, Training, Seminare und Workshops - auch Inhouse Beraiterweg 4 93047 Regensburg fon +49 941 9465243 fax +49 941 9465244 mobil + +49 170 3027092 skype ID: mfeilner mail: mfeilner(a)feilner-it.net -- Mit freundlichen Grüßen Markus Feilner --------------------------- Bitte beachten Sie unsere neuen Adressdaten! Vielen Dank. --------------------------- Feilner IT Linux & GIS Linux Solutions, Training, Seminare und Workshops - auch Inhouse Beraiterweg 4 93047 Regensburg fon +49 941 9465243 fax +49 941 9465244 mobil + +49 170 3027092 mail mfeilner(a)feilner-it.net web http://www.feilner-it.net

1 1

SuSE Firewall
by Guus Teley RI 11 Apr '05

11 Apr '05

Hello, I'm really lost at the SuSE firewall 2. As far as I can see, the ONLY firewall in place is the SuSE firewall, but it doesn't seem to matter what rules I configure, it keeps blocking those ports I thought I'd just opened. The system is up to date as far as patches are concerned. I'm wondering what other mysterious component is acting as a firewall? I recently upgraded from 8.2 to 9.2 I did not see any errors, but did notice that the default KDE login screen keeps saying 8.2 instead of 9.2. Please give me some direction to look for.

6 11

RE: [suse-security] OWA with squid 2.5 stable6, problem with connect
by Dörfler Andreas 11 Apr '05

11 Apr '05

just for the archive, problem solved ! for a little howto, look below my layout: suse 9.x for reverse proxy ( public ip ) | firewall ( allow access on port 443 to internal owa server, restrict from proxy server only: tcp host public-ip host private-ip eq 443) | outlook web access on exchange 2003 ( private ip ) first: enable the formular based login on the owa server for https reverse proxy running now with apache (2.0.5x) apache configure: ./configure --enable-layout=SuSE --enable-headers --enable-ssl --enable-cgi --enable-vhost-alias --enable-dir --disable-userdir --enable-mime --enable-auth --enable-log-config --enable-rewrite --enable-so --enable-cache --enable-dav --enable-mime-magic --enable-proxy --enable-proxy-connect --enable-proxy-ftp --enable-proxy-http --with-ssl=/usr/include/ssl --with-mpm=prefork this apache running as webserver too, for reverse the proxy parts the important add to http.conf: Listen 443 NameVirtualHost *:443 create ssl certificates for this host ! virtual host layout: <VirtualHost *:443> SSLEngine on SSLProxyEngine on ServerSignature off ServerName host.domain.tld ProxyPreserveHost on ProxyRequests off ErrorLog /var/log/httpd/owa_error CustomLog /var/log/httpd/owa_access \ "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown SSLCertificateFile /etc/httpd/certs/server.crt SSLCertificateKeyFile /etc/httpd/certs/server.key Redirect / https://host.domain.tld/exchange ## srv066 = 192.168.22.25, better work with ip here ProxyPass /exchange https://192.168.22.25/exchange ProxyPassReverse /exchange https://192.168.22.25/exchange ProxyPass /exchweb https://192.168.22.25/exchweb ProxyPassReverse /exchweb https://192.168.22.25/exchweb ProxyPass /public https://192.168.22.25/public ProxyPassReverse /public https://192.168.22.25/public ProxyPass /exchweb/bin/auth https://192.168.22.25/exchweb/bin/auth ProxyPassReverse /exchweb/bin/auth http://192.168.22.25/exchweb/bin/auth ProxyPass /iisadmpwd https://192.168.22.25/iisadmpwd ProxyPassReverse /iisadmpwd https://192.168.22.25/iisadmpwd </VirtualHost> hope it will help someone in the future. greetings andy --free your mind, use open source http://www.mono-project.com ASCII ribbon campaign ( ) - against HTML email X & vCards / \ > -----Original Message----- > From: Dörfler Andreas [mailto:Andreas.Doerfler@kempten.de] > Sent: Wednesday, March 23, 2005 12:11 PM > To: suse-security(a)suse.com > Subject: [suse-security] OWA with squid 2.5 stable6, problem > with connect > > > hi there, > > after reading multible sites over a long time > i hope im getting help via this list, im running > crazy here > > sheme: > > client (www) -> squid (www - public ip) -> firewall -> owa > (lan - private ip) > > squid.conf: > > visible_hostname host.domain.tld > https_port 443 cert=/etc/squid/server.crt key=/etc/squid/server.key > hosts_file /etc/squid/hosts > http_port 127.0.0.1:8080 > > httpd_accel_host srv066 > httpd_accel_port 80 > httpd_accel_uses_host_header off > httpd_accel_single_host on > httpd_accel_with_proxy off > > acl acl_testmail dstdomain srv066 > http_access allow acl_testmail > > acl to_index urlpath_regex /$ > acl to_favicon urlpath_regex /favicon.ico$ acl to_exchange > urlpath_regex /exchange http_access allow to_index > http_access allow to_favicon http_access allow to_exchange > > acl all src 0.0.0.0/0.0.0.0 > header_access Accept-Encoding deny all > never_direct allow all > http_access deny all > > > when i try the connect via https://host.domain.tld, the following > error ocoured: > > While trying to retrieve the URL: http://srv066 > > The following error was encountered: > > * Unable to forward this request at this time. > > This request could not be forwarded to the origin server or > to any parent caches. The most likely cause for this error is that: > > * The cache administrator does not allow this cache to > make direct connections to origin servers, and > * All configured parent caches are currently unreachable. > > > > its an urgent problem, so i hope getting help here

1 0

SUSE Security Announcement: various KDE security problems (SUSE-SA:2005:022)
by Marcus Meissner 11 Apr '05

11 Apr '05

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: kdelibs3 Announcement-ID: SUSE-SA:2005:022 Date: Mon, 11 Apr 2005 15:00:00 +0000 Affected products: 9.1, 9.2, 9.3 SUSE Linux Enterprise Server 9 Novell Linux Desktop 9 Vulnerability Type: remote code execution local denial of service Severity (1-10): 8 SUSE default package: yes Cross References: CAN-2005-0237 CAN-2005-0396 Content of this advisory: 1) security vulnerability resolved: several security problems in KDE problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: See SUSE Security Summary Report. 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion Several vulnerabilities have been identified and fixed in the KDE desktop environment. - A buffer overflow via specially crafted PCX pictures was fixed. This could lead to a remote attacker being able to execute code as the user opening or viewing a PCX images. This PCX image could have been embedded within a web page or Email. This affects SUSE Linux 9.1 up to 9.3, SUSE Linux Enterprise Server 9 and Novell Linux Desktop 9. - The IDN domain name cloaking problem was fixed. A remote website could disguise its name as another potentially trusted site by using a extension originally meant for non-ASCII domain names by using "homographs" which look exactly like other letters. The fix used by KDE is only use homographs for trusted domains. It is disabled by default for the .net, .com and .org domains. This issue exists in SUSE Linux 9.1 and 9.2, SUSE Linux Enterprise Server 9 and Novell Linux Desktop 9. It has been assigned the Mitre CVE ID CAN-2005-0233. - A denial of service attack against the DCOP service was fixed. A local user could cause another users KDE session to visible hang by writing bad data to the world writable DCOP socket. The socket has been made writable only for the user itself. This was found by Sebastian Krahmer of SUSE Security. This affects all SUSE Linux versions, except SUSE Linux 9.3. Updates for SUSE Linux up to 9.0 and SUSE Linux Enterprise Server 8 are not included for this minor issue. They will be included should a later security update for different issues be necessary. This is tracked by the Mitre CVE ID CAN-2005-0396. Additionally following bug was fixed: - A possible race in the DNS resolver causing unresolved hosts in rare cases was fixed. This only affected SUSE Linux 9.3. 2) solution/workaround Please install the updated packages. 3) special instructions and notes Make sure you restart your KDE session after this update. 4) package location and checksums 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. x86 Platform: SUSE Linux 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/kdelibs3-3.4.0-20.3.i5… 6b63160218d7e9023418980186942ab3 ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/kdelibs3-32bit-9.3-7… 7de0dcf016ad28f3f95c9110a376dc7b SUSE Linux 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kdelibs3-3.3.0-34.5.i5… 47c8c9ccb24b30261de0910ff5bfa19e ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/kdelibs3-32bit-9.2-2… 7da9ca5c0cefb043ea170c59beaa588a SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kdelibs3-3.2.1-44.46.i… 6dd4f0b38a750f256f6639decda2a968 ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/i586/kdelibs3-32bit-9.1-2… 955791a7b3973698f2c9ea8b0cd09716 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kdelibs3-3.2.1-44.46.sr… 3f5585b97d663b7d6d9bcac0f8c0b7a0 x86-64 Platform: SUSE Linux 9.3: ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/kdelibs3-3.4.0-20.3.… 5c79a3e9e143bd0c29ecbf7d4b4222a2 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/kdelibs3-3.4.0-20.3.src… 6a3f653fe866b9cfb7f9215fed404e94 SUSE Linux 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/kdelibs3-3.3.0-34.5.… d2970930a5757b3a2758eb53efda5d8b source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kdelibs3-3.3.0-34.5.src… 4ae72b2108db739ebc4aefca67b5b566 SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kdelibs3-3.2.1-44.… 7355ab449354f49fdc0de161d6fb86ab source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kdelibs3-3.2.1-44.46.… 1587e0cfa6ce3dae17c4f6fa8c10ef01 ______________________________________________________________________________ 5) Pending vulnerabilities in SUSE Distributions and Workarounds: See SUSE Security Summary Report. ______________________________________________________________________________ 6) 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.2.4 (GNU/Linux) iQEVAwUBQlqaQney5gA9JdPZAQHmVAf/ZmqLy6ioDYLfaw3xzwFjVGCKPMJMwCDw z7ncZ53/l82oLlFNIlt4A9FpK6Nq3vXCQuNCI0av6uGlhlRvqlp+XoWfYfPDVIuX wQ6ROHyJBVV2NgLCendUp/DzukF0V1aeZ8dJ4zYwlqrc5lq6HGrkxBN2ILNuBOwA mxMRk2mXcFO8f1LKqTQxrONyWRsj08F8JwZNvqosZ92ft+MnY5Cv48dl6GeRKBMX zyHvN6j/mknEUCUmTJmXHWT8bhLYCdgdWNcxvZGrMSz32m6p/B+AM4nOVn22lfYN swdN8VvaRoaGu+PBFSdvRXep71cDMZ0Y2mLMoD/+c9eHaDrs6UI7RQ== =LHnC -----END PGP SIGNATURE-----

1 0

unsubscribe,
by Stephen Aaron Meade 11 Apr '05

11 Apr '05

unsubscribe,

2 1

Open Source Protocol Analyzers
by Lucky Leavell 08 Apr '05

08 Apr '05

OS: SuSE 9.2 Pro We are currently using ethereal to analyze various attacks on our network but it is rather time consuming and we were wondering if there are any good protocol analyzers out there which can summarize and present the results. The commercial appliance NetVCR looks good but with a starting price of $US 10,000, it is WAY beyond our means. Thank you, Lucky Leavell

2 1