May 2002 - openSUSE Security - openSUSE Mailing Lists

RE: [suse-security] how to open ports
by Reckhard, Tobias 17 May '02

17 May '02

Re Flo, [snip] > conferences. I´m able to connect to this server, but there´s > no transmition > of sound and video. So I scan with nmap -p 1-65535 > [localhost] and look there > only the lisenport 1720 is open. All other ports which should > be open are > closed. Is there any possibilty to open the ports by hand? I [snip] It is perfectly normal for you to see only port 1720 open, since that's where the H.323 server is listening for incoming calls. The additional connections are only established later on, after they have been negotiated on the 'incoming call' connection. As such, you won't see any other ports as open, because there's no process listening on them. This is absolutely OK. See if you can increase the volume of output on your H.323 client and server and check what they say when you try to setup an H.323 session. And perhaps sniffing the network traffic will provide some insights as well. Tobias

1 0

Strange Web Behavior
by Austin Morgan 16 May '02

16 May '02

I am using an gateway on my network with NAT and firewall. Everything seems to work fine, but I am not able to connect to google.com. This is very strange because for the past 1 1/2 years I have been using this system I have not had a problem with it. I discovered that if I ssh into the firewall and use lynx that I can access google and run searches, but none of the computers behind the firewall can. There are no logs saying that the firewall is droping anything and the DNS reports an accurate ip address. Does anyone have any suggestions as to what might be happening? -- __ __ ____ ____ | \/ |/ ___/ ___| Austin Morgan | |\/| | | \___ \ Morgan Computer Services | | | | |___ ___) | 479-857-1189 |_| |_|\____|____/ www.morgancomputers.net

8 9

AW: AW: [suse-security] password not accepted
by mailinglists＠belfin.ch 16 May '02

16 May '02

Hi Andrés, +OK ready <21962.1021586037(a)pop.domain.ch> user test +OK Password required for test. pass Ct%I6+X -ERR [AUTH] Password supplied for "test" is incorrect. as you can see, it didn't work. Thanks, Philipp -----Originalnachricht----- Von: Andrés A. Nogueiras Meléndez An: 'suse-security(a)suse.com' Gesendet: 16.05.02 10:16 Betreff: Re: AW: [suse-security] password not accepted Raymond Leach wrote: > 02/05/16 9:37:20, mailinglists(a)belfin.ch wrote: > >>HI MIkkel >> >>there is NO spelling error. I tested it 10 times, even with direct use of >>pop3 commands and set local_echo on win2k telnet client. >>The UID of the users is 500+. So no mistake there either. >> > Maybe something is getting screwed up in the telnet translation of the % character ? > I bet too that this is happening. Some telnet/ftp/http conection use %20 as white space and %16 looks like an ASCII control char. In the other hand, I can tell that this kind of behaviour is strange, because I used to have a password with char "%" inside and nothing strange happened, maybe because the previously and next char where simple alphabetical characters, not numbers. Can you try with something like Ct%I6+X ( an uppercase i in place of the one digit ) and tell us in the list ? TIA -- [---------------------------------------------------------------] [ Prof. Andres Augusto Nogueiras Melendez ] [ Departamento de Tecnologia Electronica - Universidad de Vigo ] [ Campus Lagoas Marcosende, 9 http://www.dte.uvigo.es ] [ 36280 - Vigo, Pontevedra mailto:aaugusto@uvigo.es ] [ Spain tel: +34 986 812 091 fax: +34 986 469 547 ] [---------------------------------------------------------------] -- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

1 0

Linux Security theory/practice
by Ryan Swenson 16 May '02

16 May '02

> -----Original Message----- > From: Ryan Swenson > Sent: Wednesday, May 15, 2002 11:15 AM > To: 'suse-security(a)suse.com' > Subject: Linux Security theory/practice > > Hello, > > 1. Is it possible to take 2x kernel 2.4.18 systems with bridging, and = > the firewall bridge patch compiled in and setup transparent bridging = > along with iptable Forwarding permit or deny rules; Where we join both = > interfaces of the bridge and configure static addresses on the bridged = > ID interface, is it possible to now configure OSPF or BGP to provide = > failover among 2 Linux Bridge Peer devices? In short you take two = > switches and put in between them 2 transparent linux bridge firewalls = > which will both have unique bridge ip addresses: should 1 of these = > systems or interfaces fail, then the other will fail into a BGP = > secondary until the primary is reinstated? Any enhanced dynamic = > protocol should be fine and the only metric really concern is the weight = > of each peer and perhaps a few iptable rules to limit the size of tables = > for CPU/memory benefits as well.=20 > > If not with BGP or OSPF: with pirannha can serial/loadbalancing be = > applied to the situation or interfaces of this kind of setup where = > regardless of which device is up it must forward packets and extend the = > medium for which traffic is within the same broadcasts domains?=20 > > In theory or practice? > > > Regards/Gruesse, > > Ryan S.

3 2

Re: [suse-security] Suse Firewall Warranty
by Steve 16 May '02

16 May '02

On Thursday 16 May 2002 02:27 pm, you wrote: >* Steve (steve(a)videogroup.com) [020516 11:23]: >> What you might get is proof that it follows these standards: <list>. >> Gov's like to see some kind, ANY kind, of proof of SOMETHING. > >It's hard to imagine what <list> might be though. Oh, SSL version so and so RSA, blowfish etc. This many bits... >> I've always used my own F/W's so I don't know what they come with. But I >> doubt it's ever going to say you are never going to get hacked. Would be a >> dumb promise. >> >> But look on encryption. Something using one or another says that it's >> using this or that type of encryption. If you look at banking they have >> their standards, not always the best but if you have what they use you're >> OK with them. > >There's nothing magically on the SuSE firewall...if you build your >own using the SuSE forewall script it won't even be that different >probably. The features of the firewall on a cd product are that it >runs entirely from a cdrom and a read-only floppy disk. I guess you >could consider the gui configuration tool a feature but I find it >easier to just edit the configuration files on the floppy. -- Steve Szmidt V.P. Information Video Group Distributors, Inc.

1 1

how to open ports
by Florian Winger 16 May '02

16 May '02

Hi everybody, I´m using an openmcu server on Suse 8.0, because I want to hold multi video conferences. I´m able to connect to this server, but there´s no transmition of sound and video. So I scan with nmap -p 1-65535 [localhost] and look there only the lisenport 1720 is open. All other ports which should be open are closed. Is there any possibilty to open the ports by hand? I don´t care if all ports are open, cause I only use this Server in my LAN which is protected by a different firewall. By the way I already removed all firewall packages on the localhost with yast2. Regards Flo -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

2 1

Re: AW: [suse-security] SuSEFirewall2 - Primary Domain Controller[finally]
by mario ohnewald 16 May '02

16 May '02

Hallo! It finally works!! wooooooooohoooooooooo > Am 16.05.2002 16:16:56, schrieb "mario ohnewald" <mario.ohnewald(a)gmx.de>: > > >ups, did i mention that i have a samba PDC? > > > > Then its more important to servicepack your w2k > > check your /etc/smb.conf [suse] whether are restriction > like > > hosts allow = 192.168.1.0/255.255.255.0 > was fine! > or > > hosts deny = 192.168.2.0/255.255.255.0 > > or > > bind interfaces only > > and or in it or not > > Another issue is, that there were problems when the > length of the domainname gots an even/odd count > of characters. But thats not your game, you simply want > to > > \\servername at first > > wrote you that you can "ping servername" ????? yes > wrote you that you can "ping serverip" ???? yes > wrote you that "nmap serverip" gives the results you expected ????? yes > > what about > > \\the.server.ip.address ???????? > > I bloody hell forgot to add the line: wins server = yes ARGGHHH! now it works perfectly! Thanks a lot!!!!!!!!!!! I am really thankful that you tried to help me that much!!! Yours, Mario

1 0

AW: [suse-security] SuSEFirewall2 - Primary Domain Controller
by kreiter＠jic.at 16 May '02

16 May '02

I guess its the same Problem i have with W2K-Server and an NT4 PDC, when they are in the same subnet, all is ok. But when they are in different subnets, they get no securityinfo from the PDC. I can access the shares, ping it by name. When i try to join the Domain, it gives an Error. When i'm in the same subnet and join domain, everythings ok. When i then change the subnet back, then W2K only gets the S-Numbers instead of the names from Users. I haven't found a fix for this Problem yet. My solution was a second Network only for the Servers, to connect W2K with NT4 in the same subnet. Andreas Kreiter -----Ursprüngliche Nachricht----- Von: mario ohnewald [mailto:mario.ohnewald@gmx.de] Gesendet am: Donnerstag, 16. Mai 2002 09:59 An: suse-security(a)suse.com Betreff: Re: [suse-security] SuSEFirewall2 - Primary Domain Controller doooh! Well, not really solved yet ;( Working with names works now, but my w2k Client still cant find my PDC (when i wanna join my domain), but it can ping it "ping pdc". do i have to enable some ports for internal routing? Protect from Internal is off. Any Ideas? Cheers, Mario > Ahhh, now it works! > Thanks a LOT! > > Mario > > > >Yes, i did that. I can reach all the ips in each net, so the routing > seems > > >to work, i can just not work with Names. > > > > > >Mario > > > > So put the ip of the pdc as wins-server in the settings of your clients in > the > > other subnet :O) > > > > Yours Michael Appeldorn > -- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here

4 8

SuSE Security Announcement: lukemftp, nkitb, nkitserv (SuSE-SA:2002:018)
by Thomas Biege 16 May '02

16 May '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: lukemftp, nkitb, nkitserv Announcement-ID: SuSE-SA:2002:018 Date: Wednesday, May 15th 2002 12:30 MEST Affected products: 6.4, 7.0, 7.1, 7.2, 7.3, 8.0 SuSE eMail Server III SuSE Linux Database Server SuSE Firewall Adminhost VPN SuSE Linux Live-CD for Firewall SuSE Linux Admin-CD for Firewall SuSE Linux Connectivity Server SuSE Linux Enterprise Server 7 SuSE Linux Enterprise Server for S/390 Vulnerability Type: remote command execution Severity (1-10): 3 SuSE default package: yes Other affected systems: all systems using lukemftp Content of this advisory: 1) security vulnerability resolved: buffer overflow while parsing PASV command 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 Lukemftp (ftp(1), /usr/bin/ftp, /usr/bin/pftp) is a compfortable ftp client from NetBSD. A buffer overflow could be triggered by an malicious ftp server while the client parses the PASV ftp command. An attacker who control an ftp server to which a client using lukemftp is connected can gain remote access to the clients machine with the privileges of the user running lukeftp. The lukemftp RPM package is installed by default. You need to update the package, as no temporary workaround is possbible. 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. i386 Intel Platform: SuSE-8.0 ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/lukemftp-1.5-249.i386.rpm 0ae28f7ca49157bfa5783626d3e82cef source rpm: ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/lukemftp-1.5-249.src.rpm d9fc530c338ea2de122b6a4a1f89a627 SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/lukemftp-1.5-256.i386.rpm aeb64a5ba64b5b334dfcf244423a9809 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/lukemftp-1.5-256.src.rpm cc94b939696c76cda0fec683d12ff384 SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/lukemftp-1.5-256.i386.rpm 94812aeb3b164a67b0c85b0c9a61a450 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/lukemftp-1.5-256.src.rpm 5cd6642505a68be70ce9eac3ba5dd311 SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/lukemftp-1.5-251.i386.rpm 836df6046ce81fcc82e9939fde5003d1 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/lukemftp-1.5-251.src.rpm 788bc38fed7b486e857b5d780451b7a7 SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/nkitb-2002.5.8-0.i386.rpm e6199c28c700461a7ae10c3f7fba73a8 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/nkitb-2002.5.8-0.src.rpm e1c6379846842ea62a5c484167102cae SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/nkitserv-2002.5.8-0.i386.rpm 50bb6a7ae3f450ad530ad92ae8dad3e1 SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/a1/nkitb-2002.5.9-0.i386.rpm 6950a272cf3a30a02860cf179387a9e8 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/nkitb-2002.5.9-0.src.rpm 09d7ac9ba5e1420eeddb016a6d812067 Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/lukemftp-1.5-77.sparc.rpm 295d90e7bfeb94f27f542616e016bd65 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/lukemftp-1.5-77.src.rpm 42e213cfc930e0a00aa871e9996d3cba SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n1/lukemftp-1.5-76.sparc.rpm 50fc0f99b42347aee746450624ed4817 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/lukemftp-1.5-76.src.rpm 01cdff7ff9f908466b8d3269fe4529c5 SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/a1/nkitb-2002.5.8-0.sparc.rpm 210230a1a085af9f777f047a9edfa9f5 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/nkitb-2002.5.8-0.src.rpm b0e476e5ba4e9211cab20442f35b49d8 SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/nkitserv-2002.5.8-0.sparc.r… 70b063b1901c8655a23b008cc6ef4036 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/lukemftp-1.5-89.alpha.rpm 27c6ca255ef42c7e6851f309d6474fcd source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/lukemftp-1.5-89.src.rpm fdc27d3abae5bf6dfcd06907d2afc278 SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/a1/nkitb-2002.5.8-0.alpha.rpm 2c397f234a2326baba98a4da8dff601a source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/nkitb-2002.5.8-0.src.rpm 437a49653372205c4218e7283422fd6b SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/nkitserv-2002.5.8-0.alpha.rpm e2943d09b3bf82883bfd62aff74e500b SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/a1/nkitb-2002.5.9-0.alpha.rpm 33b7a7b2f81dc78035450c0643786c83 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/nkitb-2002.5.9-0.src.rpm 60960a0129207b317fc22089f6203589 PPC Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/lukemftp-1.5-154.ppc.rpm fd6bc23e95cd7a19283dd4067f376bb3 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/lukemftp-1.5-154.src.rpm bb301c6487a09a2b3d82ce9b000b8f69 SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/lukemftp-1.5-150.ppc.rpm 023a43cba32d976d0a5665365242647b source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/lukemftp-1.5-150.src.rpm 53f38c8f4a3205b3bedbc76b209d177b SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/a1/nkitb-2002.5.8-0.ppc.rpm 101d5af039c262f7b7e7d50598fa064c source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/nkitb-2002.5.8-0.src.rpm ed39244bcb57fad7b92287f5c9d26e3d SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/nkitserv-2002.5.8-0.ppc.rpm b6146585ab16d1d507e04f066f21f5d6 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/a1/nkitb-2002.5.9-0.ppc.rpm 10b66b58b887a1899df7e16b15689bfb source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/nkitb-2002.5.9-0.src.rpm 954dcd26ef2eb777e737621927f98835 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - imap A bug report about a buffer overflow in the RFC1730 code of the wu-imap eMail server was published. SuSE Linux' imap packages were compiled without RFC1730 support, so SuSE Linux is not vulnerable to this bug per default. - dhcp A format string bug was found in the DynamicDNS (DDNS) code of ISC's DHCP server software. New RPMs are currently being build. - imlib Due to packaging failures we have to re-release the imlib packages which should be available within the next days. This update addresses missing dependencies and affects applications like xcdroast. - perl-Digest-MD5 A bug was found in the UTF8 interaction between perl and perl-Digest-MD5 which leads into failures while verifying the MD5 hash. New RPMs are currently being build. ______________________________________________________________________________ 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 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: 2.6.3in Charset: noconv iQEVAwUBPOOaMney5gA9JdPZAQHhdggAmcDEmc+F15x5VI6LQhUyONMBQHr5HUAb Lb3iR3qAGEAxyyUL4VnSX18BNcTxMfTRVUqiwHhihTfAnDun70eObGEiJjPSEVwG jEACz3kFOz1HfGuowovn1O8VrK8kRcfBwhAUKSwgr2aXEgP+FbSKpdQbH6sDJVpR HUBa/YLhYGF9PiJ2ev+i5nt+1mYu4BMA22w1DVyHuSGzr3yPzo/wPUcak+J2VZHJ jgKm4hYpUHnRwU3CV/RPQOAgzV5OYp9aKE5wQU5bx35gvwl8U5RG00lcxltdjKAJ GGxKzvciEduusNPGWKEShjOGSMWiTwB3goDomv1KG6PwBmaxDSE4uA== =0IAE -----END PGP SIGNATURE----- Bye, Thomas -- Thomas Biege <thomas(a)suse.de> SuSE Linux AG,Deutschherrnstr. 15-19,90429 Nuernberg Function: Security Support & Auditing "lynx -source http://www.suse.de/~thomas/contact/thomas.asc | pgp -fka" Key fingerprint = 51 AD B9 C7 34 FC F2 54 01 4A 1C D4 66 64 09 83 -- Trete durch die Form ein, und trete aus der Form heraus.

1 0

AW: AW: [suse-security] SuSEFirewall2 - Primary Domain Controller
by kreiter＠jic.at 16 May '02

16 May '02

The PDC and Domain is in lmhosts. Under NT4 it only works with this Entry on the clients in another subnet, but W2K does not. The only thing i could not try is to change the name of the Domain. Under W2K there is a strange behavior with underline "_", it didnt let create a computername with an _ in it. And the Domain contains an _ Maybe in my situation is this the Problem. Andreas Kreiter -----Ursprüngliche Nachricht----- Von: Michael Appeldorn [mailto:appeldorn@codixx.de] Gesendet am: Donnerstag, 16. Mai 2002 12:18 An: 'mario ohnewald'; Andreas Kreiter Cc: suse-security(a)suse.com Betreff: Re: AW: [suse-security] SuSEFirewall2 - Primary Domain Controller There is a file called lmhosts where you can define pdc and domains by ips Did it to call user-managment from y2k to a nt-pdc in another subnet Try this and call back wether suceed or not Michael Appeldorn >I guess its the same Problem i have with W2K-Server and an NT4 PDC, >when they are in the same subnet, all is ok. >But when they are in different subnets, they get no securityinfo from the >PDC. >I can access the shares, ping it by name. >When i try to join the Domain, it gives an Error. >When i'm in the same subnet and join domain, everythings ok. >When i then change the subnet back, then W2K only gets the S-Numbers instead >of the names from Users. >I haven't found a fix for this Problem yet. >My solution was a second Network only for the Servers, to connect W2K with >NT4 in the same subnet. > >Andreas Kreiter > >-----Ursprüngliche Nachricht----- >Von: mario ohnewald [mailto:mario.ohnewald@gmx.de] >Gesendet am: Donnerstag, 16. Mai 2002 09:59 >An: suse-security(a)suse.com >Betreff: Re: [suse-security] SuSEFirewall2 - Primary Domain Controller > >doooh! Well, not really solved yet ;( >Working with names works now, but my w2k Client still cant find my PDC (when >i wanna join my domain), but it can ping it "ping pdc". >do i have to enable some ports for internal routing? >Protect from Internal is off. > >Any Ideas? > >Cheers, Mario > >> Ahhh, now it works! >> Thanks a LOT! >> >> Mario >> >> > >Yes, i did that. I can reach all the ips in each net, so the routing >> seems >> > >to work, i can just not work with Names. >> > > >> > >Mario >> > >> > So put the ip of the pdc as wins-server in the settings of your clients >in >> the >> > other subnet :O) >> > >> > Yours Michael Appeldorn >> > > >-- >To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com >For additional commands, e-mail: suse-security-help(a)suse.com >Security-related bug reports go to security(a)suse.de, not here > > > > >-- >To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com >For additional commands, e-mail: suse-security-help(a)suse.com >Security-related bug reports go to security(a)suse.de, not here > > >

1 0