February 2004 - openSUSE Security - openSUSE Mailing Lists

access via SSH
by Richard Farla 28 Feb '04

28 Feb '04

Greetings, After upgrade from 8.0 to 8.2 I have problems accessing my system with SSH. >From the box to another system theire is no problem, but from other linux-boxes or windows (using Putty) I cannot access it anymore. The firewall is on, also services allowed is SSH and I also tell firewall to accept tru port 22. I read a lot of info and went tru some conf files but I do not know where the problems is located exactly Richard

13 17

Re: [suse-security] Strange entry in Apache log
by Keith Roberts 27 Feb '04

27 Feb '04

Hi Arjen. On Fri, 27 Feb 2004, Arjen Runsink wrote: > This has nothing to do with your smtp port > > They scanned for open proxies and tried if your apache would allow to proxy. > The trick is that even smtp connections can be proxied over a web proxy. > > Just make sure this is not possible with your apache > so check error_log for confirmation this failed. Whoops! that got deleted about 15 mins ago! I have just check my httpd.conf file and the proxy_module is not loaded. # LoadModule digest_module /usr/lib/apache/mod_digest.so # LoadModule proxy_module /usr/lib/apache/libproxy.so # LoadModule cern_meta_module /usr/lib/apache/mod_cern_meta.so # AddModule mod_digest.c # AddModule mod_proxy.c # AddModule mod_cern_meta.c I take it it is OK not having mod_proxy installed. Thankyou for the explaination. Kind Regards - Keith Roberts

1 0

Strange entry in Apache log
by Keith Roberts 27 Feb '04

27 Feb '04

Hi everyone. Can anyone tell what the following apache logs are? The last line looks like they managed to connect to port 25. Or did someone get my machine to connect to another servers port 25? 220.163.27.187 - - [27/Feb/2004:16:00:48 +0000] "\x04\x01" 200 0 "-" "-" 220.163.27.187 - - [27/Feb/2004:16:01:40 +0000] "\x05\x01" 200 0 "-" "-" 220.163.27.187 - - [27/Feb/2004:16:01:51 +0000] "CONNECT 207.217.125.22:25 HTTP/1.1" 200 5664 "-" "-" I have just been to grc.com, and my SMTP port is stealthed. Here is a listing of netstat keith@myserver:~> netstat -lt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:printer *:* LISTEN tcp 0 0 *:www-http *:* LISTEN tcp 0 0 *:afs3-fileserver *:* LISTEN tcp 0 0 localhost:smtp *:* LISTEN Anyone have any ideas? Kind Regards - Keith Roberts

4 4

SUSE Security Announcement: xf86/XFree86 (SuSE-SA:2004:006)
by thomas＠suse.de 27 Feb '04

27 Feb '04

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: xf86/XFree86 Announcement-ID: SuSE-SA:2004:006 Date: Monday, Feb. 23th 2004 16:30 MET Affected products: 8.0, 8.1, 8.2, 9.0 SuSE Linux Database Server, SuSE eMail Server III, 3.1 SuSE Linux Enterprise Server 7, 8 SuSE Linux Firewall on CD/Admin host SuSE Linux Connectivity Server SuSE Linux Office Server Vulnerability Type: local privilege escalation Severity (1-10): 5 SUSE default package: yes Cross References: CAN-2004-0083 CAN-2004-0084 CAN-2004-0106 Content of this advisory: 1) security vulnerability resolved: - several local buffer overflows in fontfile code problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - mutt - mod_python - mailman - metamail - libxml2 - lbreakout - pwlib 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information XFree86 is an open-source X Window System implementation that acts as a client-server-based API between different hardware components like display, mouse, keyboard and so on. Several buffer overflows were found in the fontfile code that handles a user-supplied "fonts.alias" file. The file is processed with root privileges and therefore a successful exploitation of these bugs leads to local root access. There is no known workaround. Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, to apply the update use the command "rpm -Fhv file.rpm". Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. Intel i386 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/XFree86-4.3.0.1-46.i58… dcaadc2b9438995c9a3ac6e4fc7bf181 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/XFree86-4.3.0.1-46.i58… f094861c9a0fbb5f27d168b680fe1a5b source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/XFree86-4.3.0.1-46.src.… 824c6173693342a033f75c503592e7e0 SuSE-8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/XFree86-4.3.0-120.i586… f1f01280e6e8a5a2f091a04c5836a51d patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/XFree86-4.3.0-120.i586… 16ba90ef0ad607d1547cda7734b28750 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/XFree86-4.3.0-120.src.r… 4100735436d4c8801c6add673fceb29e SuSE-8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/xf86-4.2.0-257.i586.rpm 9ed1fc5ec83a42a85315391387610e6b patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/xf86-4.2.0-257.i586.pa… 9652732385f8670ea9d36151378b7428 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/xf86-4.2.0-257.src.rpm e1d73191d2aabe3a6dda677e6fd716bc SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/x1/xf86-4.2.0-257.i386.rpm 9b69aac017a0ac9905e3fc4e9594d435 patch rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/x1/xf86-4.2.0-257.i386.patch.rpm 3076136bcdf20132f343768e4a71c7a2 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/xf86-4.2.0-257.src.rpm 1775eef155f4afdc9a3a08ff31a38607 Opteron x86_64 Platform: SuSE-9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/XFree86-4.3.0.1-52… 1714cb2eb566fab0e29277db9f9d2572 patch rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/XFree86-4.3.0.1-52… 930944efc868b28d87a69a9543206546 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/XFree86-4.3.0.1-52.sr… ee67773fcad341912b617d397991ed32 ______________________________________________________________________________ 2) Pending vulnerabilities in SUSE Distributions and Workarounds: - mutt The popular email client mutt is vulnerable to a remote denial-of-service attack and maybe remote command execution. The bug can be triggered by malformed messages that overflow an internal buffer. New packages are available on our FTP servers.. - mod_python A remote denial-of-service attack can be triggered against the Apache web server by sending a specific query string that is processed by mod_python. New packages will be available soon. - mutt The popular email client mutt is vulnerable to a remote denial-of-service attack and maybe remote command execution. The bug can be triggered by malformed messages that overflow an internal buffer. New packages are available on our FTP servers.. - mailman A remote denial-of-service attack can be triggered in mailman 2.0.x (CAN-2003-0991). New packages will be available soon. - metamail This update fixes two buffer overflows and two format string bugs that can be exploited remotely in conjunction with other tools to gain access to a system with the privileges of the user running New packages will be available soon. - libxml2 A buffer overflow in the URI parsing cde is fixed. This bug can lead to remote access to a system using libxml2. New packages will be available soon. - lbreakout A buffer overflow in lbreakout can be exploited locally to gain access to group 'game'. This just affects SuSE Linux 8.1. New packages will be available soon. - pwlib This update addresses several security vulnerabilities that may be exploited remotely via applications that link with pwlib, like GnomeMeeting or alike. New packages will be available soon. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SUSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SUSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(a)suse.de) the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an un-installed rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SUSE in rpm packages for SUSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SUSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the top-level directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SUSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SUSE's announce-only mailing list. Only SUSE's security announcements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. ===================================================================== SUSE's security contact is <security(a)suse.com> or <security(a)suse.de>. The <security(a)suse.de> public key is listed below. ===================================================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the clear-text signature shows proof of the authenticity of the text. SUSE Linux AG makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff 4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3 0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot 1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/ HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM 523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q 2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8 QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ 1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1 wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol 0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J /LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8 RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ 8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X 11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA 8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+ AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0 zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM /3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7 whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE= =LRKC - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBQDoqtney5gA9JdPZAQEFXwf/c/7wZeApCFm5EQLhBfXdeZOYFiP1APP2 CXyAuf1eUBQOrCoPtSgOqG3g3kL3Q0y4D/pkAYB6+ysJH0D6JGJHADUO012LsbgY UoOw0AZMQ0450I/C+rzcWM5tyL6+l5SJSIoGAzumUv9xW09EMV1Rg+dpBrEk7Dcu 0hs1Gt2ZtRXhlV1N0euEC3JzBWPgLjBJcNqrnmx9OFN83oZel32t7hxaXTI3hGqQ dotS9P6d+anvSpamkWq6sU96vb4QMAkuN1D81j1Fz7p9ut25XDgjRFNQfKJD6lFq f192BMnjTu2ssX5BCR0PA2AGw8xxgEuY+J/wvCXjUi+pMwh8y+Kaeg== =StId -----END PGP SIGNATURE-----

3 5

SuSE Firewall2 ? same as pro9 firewall2?
by Mike Partyka 27 Feb '04

27 Feb '04

Could someone please explain a little more about the suse firewall2 product? I purchased SuSE Linux Pro 9.0 and it has a firewall2 with it. Is that the same as the SuSE firewall2 product I've seen advertised on the SuSE website? I see there is also a VPN module that can be purchased is this somewhere with my distribution so I could try it out? If not, any way an evaluation can be gotten? I've looked on their site but there's realy not mich info about the firewall2 product. Thanks in Advance Mike

2 1

Re: [suse-security] SUSE Security Announcement: Linux Kernel (SuSE-SA:2004:005)
by Fred Merritt 27 Feb '04

27 Feb '04

Hi, can anyone at SuSE give us an update as to when the 8.0 kernels will be available. They have been promised a few times for 'tomorrow', but so far nothing has materialised. I believe that it's only a few days now till the exploit is released. TIA, and best regards. . . Fred

5 8

Kernel Patch
by Gero Schmidt-Kärst 26 Feb '04

26 Feb '04

Hi ! I'm going to setup a new Server with SuSE 9.0. Since it had been published there was several Kernel patches. My stupid question is: Do I have to install all of them or is only the last necessary ? Thanks for help GSK

2 1

Re: [suse-security] UML as security layer and for server consolidation
by Paranoiac_User 25 Feb '04

25 Feb '04

> Hello, > > maybe the vserver soulution is better than uml -> > Take a look at: http://www.13thfloor.at/vserver/project/ > > Good Luck Without blaming you too much, but this is a typical "dunno much about your question, but try this instead" anwser, that does not help very much, simply because the same question has to be asked under this new circumstances. You wrote nothing on the security impact/improvements of your suggestion. BTW: The project seems to have some problems: snip ---- As the project is undergoing a change of leadership and re-organisation there are still several other sites maintained by individuals. It is intended that in the future this site will become the central respository of information and coordination. To that end, all current developers and interested individuals are invited to contribute to these pages. ---- snap Michael

1 0

pam_limit.so question
by Philippe Vogel 24 Feb '04

24 Feb '04

Hello! I want to restrict user rights but give users ssh access. The users may use ssh, scp, sftp, but should not alter the server, if someone doesn't know much about scripting and for securing the server to possible kiddies with console-account. I setup following: /etc/security/limits.conf @admin - @users hard priority 17 @users hard maxlogins 2 @users hard core 0 @users hard cpu 10 @users hard data 8196 @users hard fsize 8196 @users hard memlock 2048 @users hard nofile 64 @users hard nproc 8 @users hard rss 8196 @users hard stack 2048 @users hard as 16384 What setting is needed, what settings are O.K. and what makes working impossibles canot be found in the manpage. Is there a possibility to secure the server, that users in group users cannot open socket without a kernel-patch? Any hints? Philippe

2 1

Can a Suse box be a proxy gateway and a DNS server at the same time??
by Joao M.C. Alvega 24 Feb '04

24 Feb '04

Hello, i'm having some problems. Does anyone know if it's possible to make a Bind to work in the same machine as Squid? If so could anyone explain me how? Here bind will work as a DNS Server(master) and not a cache. thank you very munch for any help tha may come!

3 3