May 2000 - openSUSE Users - openSUSE Mailing Lists

[SLE] mounting floppy drive
by pras＠linux.ca 07 May '00

07 May '00

I am unable to mount the floppy drive (/dev/fd0) to /floppy as a regular user. In /etc/fstab, I have this line: /dev/fd0 /floppy auto noauto,owner 0 0 I have added myself to the group 'disk'. I have made the /floppy folder rewriteable by group disk. However, when I type 'mount /floppy' or 'mount /dev/fd0' as a regular user, I get an error saying 'mount: must be superuser to mount'. How can I fix this? Thanks. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

6 10

[SLE] vmware
by brumsey＠world-net.co.nz 07 May '00

07 May '00

This may sound a bit stupid , but I am going to set up a kind of cybercafe and am wondering if it would be possible to have linux on all m/c but run vmware to run the cafe as the program I want to use only runs on windoze. I was thing that if they broke out of the system or a virus/worm was let loose they would only damage the vmware dir and maybe have a more secure system. Any ideas on this? B.Rumsey ------------------------------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0

[SLE] qmail (controlling pop3 with tcpserver)
by colWilson＠bigfoot.com 07 May '00

07 May '00

qmail ===== I have been working on trying to get wvdial-popup et al to run under tcpserver but as it always tries to check then REMOTEHOST on a dns, it continues to dial out on my modem (diald). I have tried to get around this by using "tcpserver -H -R -l fqdn" but no luck I even tried specifying LOCALHOST, REMOTEHOST and REMOTEINFO in a .cdb database, but this di not work either. Can anyone help? Col Wilson colWilson(a)bigfoot.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0

[SLE] mesa 3dfx 6.4
by ahenry＠cusa.dyndns.org 07 May '00

07 May '00

Hello all. I am using 6.4, with a Voodoo2 BlackMagic card. I am having problems getting Mesa and glide_v2 to coexist (YaST tells me both are not needed), so I found the recommended packages for 6.2 from the Support Database: <http://sdb.suse.de/sdb/en/html/hoe_voodoo_3d.html> Which packages do I need to install, using SuSE 6.4? thanks end. -- [-=-=-=-=-=-=-=-=-=-=- adam j henry =-=-=-=-=-=-=-=-=-=-=] | [http: www.heidelberg.edu/~ahenry] [pgp: 0xBD168A74] | | [mailto: ahenry(a)heidelberg.edu] [icq: 69243836] | [-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=] -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

2 1

Re: [SLE] lprold || lprng || plp?
by mircea.andrei＠wanadoo.fr 07 May '00

07 May '00

Since you did not get an immediate answer, I'll share my experience although it is not much. Usually I carry my old lpr programs and scripts from one update to the next - I don't like to change. Moving to 6.3 I did the same - carrying from 6.1 what I had there (I guess it is "lprold"). But before doing that, I tried the 6.3 lprng. It works quite nicely and has some cool features I do not have with my old lpr. It is widely different from lprold but I can't go into the details here - it is in the documentation. Still, after testing lprng and being satisfied with it, I decided I don't need the new features and went back to my old lpr. I have two simple scripts which allow me to switch from one system to another, just to see what happens from time to time (when I seem to have problems with printing), like so (being root or su root): /usr/local/bin/lprold: --------------------------------- killall lpd cd /etc cp printcap.61 printcap cd /usr/sbin cp lpd.61 lpd cp lpc.61 lpc cd /usr/bin cp lpr.61 lpr cp lprm.61 lprm cp lpq.61 lpq cp lpstat.61 lpstat rm -f cancel lpd & ------------------------- /usr/local/bin/lprng: -------------------------- killall lpd cd /etc cp printcap.63 printcap cd /usr/sbin cp lpd.63 lpd cp lpc.63 lpc cd /usr/bin cp lpr.63 lpr cp lprm.63 lprm cp lpq.63 lpq cp lpstat.63 lpstat cp lprm.63 cancel lpd & -------------------------- On Sat, May 06, 2000 at 06:27:53PM -0400, Steven T. Hatton wrote: > There are three options for print daemons included in the SuSE 6.4 > distribution. I am wondering what the differences between them are. I > anybody knows, I'd like it have a clue myself. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0

[SLE] succinct, yet pithy...
by tjhanson＠home.com 07 May '00

07 May '00

This is from the Red Rock Digest, a list to which I subscribe, on the love virus. "Some notes on Microsoft viruses, economic history, and the rational side of Luddism, plus another batch of URL's. "I received about 60 copies of the latest Microsoft e-mail virus and its variants. How many did you get? Fortunately I manage my e-mail with Berkeley mailx and Emacs keyboard macros, so I wasn't at risk. But if we're talking about billions of dollars in damage, which equates roughly to millions of lost work days, then I think that we and Microsoft need to have a little talk. "Reading the press reports, Microsoft's stance toward this situation has been disgraceful. Most of their sound bites have been sophistry designed to disassociate the company from any responsibility for the problem. One version goes like this quote from Scott Culp of Microsoft Public Relations, excuse me, I mean Microsoft Security Response Center: This is a general issue, not a Microsoft issue. You can write a virus for any platform. (New York Times 5/5/00) "Notice the public relations technology at work here: defocusing the issue so as to move attention away from the specific vulnerabilities of Microsoft's applications architecture and toward the fuzzy concept of "a virus". Technologists will understand the problem here, but most normal people will not. Mr. Culp also says this (CNET 5/5/00): This is by-design behavior, not a security vulnerability. "More odd language. It's like saying, "This is a rock, not something that can fall to the ground". It's confusing to even think about it. Even though Microsoft had been specifically informed of the security vulnerability in its software, it had refused to fix it. Microsoft even tried to blame its problem on Netscape, which had fixed it: http://news.cnet.com/news/0-1005-200-1820959.html "The next step is to blame the users. The same Mr. Culp read on the radio the text of a warning that the users who spread the virus had supposedly ignored. That warning concludes with a statement to the effect that you shouldn't execute attachments from sources that you do not trust. He read that part kind of fast, as you might expect, given that the whole point of this virus is that people receive an attachment from a person who has included them in their address book. This particular blame-shifting tactic is particularly disingenuous given that the virus spread rapidly through Microsoft itself, to the point that the company had to block all incoming e-mail (Wall Street Journal 5/5/00). "Similarly, CNET (5/4/00) quoted an unnamed "Microsoft representative" as saying that companies must educate employees "not to run a program from an origin you don't trust". Notice the nicely ambiguous word "origin". The virus arrives in your mailbox clearly labeled as having been sent by a particular individual with whom you probably have an established relationship. It bears no other signs of its "origin" that an ordinary user will be able to parse, short of executing the attachment. "So what on earth is Microsoft doing allowing attachments to run code in a full-blown scripting language that can, among many other things, invisibly send e-mail? Says the "Microsoft representative", We include scripting technologies because our customers ask us to put them there, and they allow the development of business-critical productivity applications that millions of our customers use. "There needs to be a moratorium on expressions such as "customers ask us to". Does that mean all of the customers? Or just some of them? Notice the some/all ambiguity that is another core technology of public relations. Do these "customers" really specifically asked for fully general scripts that attachments can execute, or do they only ask for certain features that can be implemented in many ways, some of which involve attachments that execute scripts? Do the customers who supposedly ask for these crazy things understand the consequences of them? Do they ask for them to be turned on by default, so that every customer in the world gets the downside of them so that a few customers can more conveniently get the upside? And notice how the "Microsoft representative" defocuses the issue again, shifting from the specific issue of scripts that can be executed by attachments to the fuzzy concept of "scripting technologies", as if anybody were suggesting that scripting technologies, as such, in general, were to blame. "Microsoft shouldn't be broken up. It should be shut down. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0

Re: [SLE] (OT): M$ response to I LOVE YOU
by Master9116＠aol.com 07 May '00

07 May '00

In a message dated 5/6/00 4:36:36 AM Pacific Daylight Time, adcarlso(a)visinet.ca writes: > >> > -----Original Message----- > >> > From: Ole Kofoed Hansen [mailto:k01164@ko.sdu.dk] > >> > Sent: Friday, May 05, 2000 7:17 AM > >> > To: suse-linux-e(a)suse.com > >> > Subject: Re: [SLE] (OT): M$ response to I LOVE YOU > >> > > >> > > >> > At 08:36 05-05-00, Dennis wrote: > >> > >Microsoft Corp., for its part, said the virus was not > >> > indicative of any > >> > >particular vulnerability associated with Microsoft Outlook. > >> > [...snip...] > >> > >Anyway, here's what a spin-doctor at Mickey$oft has to say about > >> > >it, courtesy of Reuters-- prepare to gag. > >> > >-------------BS follows----------- > >> > > > >> > >``Viruses are really an industry-wide issue,'' said Scott Culp, > >> > >program manager for Microsoft's security response center. ''They > >> > >can > >> > > be written for any platform. They can be written to use a > >> > variety of > >> > >e-mail clients. > >> > > > >> > > ``In this case the virus author chose to target Outlook probably > >> > >because it gave him better reach,'' he said. ``There isn't a security > >> > > vulnerability in Outlook involved in this at all,'' Culp said. > >> > >------------end BS------------- > >> > > >> > Actually he was right. As far as I know, this worm (it is NOT a virus) > >> > still requires the user to actively tell the computer to run > >> > the program. > >> > > >> > If the user will run it, he might also save it and run it if > >> > he was using > >> > a different MUA or even OS. (Of course, in this specific case, > >> > the program would only run on a MS OS.) > >> > > >> > Please note that I am not saying that Microsoft programs are > >> > safe, just that as long as a user has to actively run a program, > >> > it is no fault of the OS or applications if the program is > >> > malicious. > >> > >> You can't possibly say that the amount of damage that can be done by this > >> worm could be done on Linux. I could see a user running a script or > >> executable that would send out e-mails but basic system files (such as > the > >> registry if there were one on Linux) aren't going to be overwritten on a > >> decent multi-user system. > >> > > > > It won't be that hard to right a shell or perl script to go though a pine > or > > elm address book and send it's self to all the users in it. The registry > on > > win would be the /etc directory on Unix (or LDP), but the scritpt won't be > > able to do this on Unix (and shouldn't be able to on NT/2000), only Win9* > > and MacOS are suspectiable to this type of "user == root at all times" > type > > of attack. > > > > > > > > > > -- > The only problem with writing such a script, is that you must get it to > attack > (i.e. read) the file for a particular email app. Unlike Windows, Linux > users > seem to have a plethora of email apps, albeit some more popular than others. > > And the "address files" are probably slightly different for each. > > But the inherent security within Linux itself prevents such a script from > being > too destructive (maybe at best a single user). And even then, the script > would > have to be run...who runs apps or scripts from unknown sources?!?! > > ----------------------------------- > Here is my 2 cents. I administer several FreeBSD systems and I have to say from that experiance, it is very difficult if not impossiable for a user executed script to damage the system unless the script is run at UID 0. At the most only a single user will be damaged or destroyed. This is the reason why I run all internet access daemons from their own UID to separate the services from each other AND to limit the vurnabilities to the system if one should crash and dump the user into the shell session for that UID. Windows Nice Try and Windows 2Knockout more than likely have numerous holes in their security that people (Hackers/Crackers/Sysadmins/End Users) have not yet discovered. This E-Mail Virus or Worm is in the message atachment with the filename "I LOVE YOU.TXT.vbs". Basically the .vbs is critical here. It types the file to Visual Basic Script which is akin to either a shell script in a UNIX environment or a BATCH file in the DOS world. This malicious program is targeted directly at Microsoft Outlook because VBS is a Microsoft only scripting language. Even Netscape 4.72 under Windows as well as any other Windows E-Mail client and other platforms such as Unix, Macs, etc are immune from it. Dan. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0

[SLE] Napster Usage
by BobFi＠swbell.net 07 May '00

07 May '00

This was on INCIDENTS(a)SECURITYFOCUS.COM today: If anyone wants a good way to detect napster usage (as well as lots of other shenanigans) you might try using snort IDS. http://myweb.clark.net/~roesch/ "A Lightweight Intrusion Detection System" Jim Forster wrote some snort rules to report on Napster usage. http://snort.rapidnet.com/ Here are the Napster Rules that show ports and content. You can adapt this to your own IDS. It triggers for me whenever I go on napster (I only use napster for research purposes ;^> ) alert tcp any any <> any 6699 (msg:"Napster Client Data"; flags:PA; content:".mp3"; nocase;) alert tcp any any <> any 8888 (msg:"Napster 8888 Data"; flags:PA; content:".mp3"; nocase;) alert tcp any any <> any 7777 (msg:"Napster 7777 Data"; flags:PA; content:".mp3"; nocase;) alert tcp any any <> any 6666 (msg:"Napster 6666 Data"; flags:PA; content:".mp3"; nocase;) alert tcp any any <> any 5555 (msg:"Napster 5555 Data"; flags:PA; content:".mp3"; nocase;) alert tcp any any <> any 4444 (msg:"Napster 4444 Data"; flags:PA; content:".mp3"; nocase;) alert tcp any any <> any 8875 (msg:"Napster Server Login"; flags:PA; content:"anon(a)napster.com";) -- Bob F EMail BobFi(a)SWBell.net A Truly Wise Man Never Plays Leapfrog With A Unicorn... -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0

[SLE] TCP port 6699 ?
by icarus＠guldennet.nl 07 May '00

07 May '00

Hi, I've noticed that a lot of hosts from many diferent locations are trying to access my hosts port 6699 every once in a while. Does anyone know what that port does? Thanks, Rogier Maas -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

2 1

Re: [SLE] NT4 and suse 6.4
by brumsey＠world-net.co.nz 07 May '00

07 May '00

I have now made up my mind to forget about NT4 and go with the dds service. It may cost a lot more ($899 NZD ) but I can run it linux. My next question is what is the best way to connect 6 windoze mc to linux I was thing squid or is there a better way. B.Rumsey On Thu, 04 May 2000, scsijon wrote: > Jerry, he's talking about a system that used a uplink via either cable or a > phone line and a satellite downlink into a dish and to the modem, We have a > similar link to New Zealand available in Australia that gets you : > > uplink - phone - 56K > uplink - cable - 400k > downlink - satellite - 128K to 400k > > can be setup anywhere in our country (phone link). > > price is about the same. > > Problem is the "modem" is not relly that, it's a hell of a lot more, so I > suspect their a little bit "chewey" against trying it on other os's, when > thwy have to guarantee service. > > regards > scsijon > > -----Original Message----- > From: Jerry Kreps <JerryKreps(a)alltel.net> > To: suse-linux-e(a)suse.com <suse-linux-e(a)suse.com> > Date: Thursday, May 04, 2000 12:31 PM > Subject: Re: [SLE] NT4 and suse 6.4 > > > >On Thu, 04 May 2000, B.Rumsey wrote: > >> No It is not free (about $300NZD a month). They would not give me any > >> information on the modem. All I got told was that the data gets sent down > >> the phone line and returnning data comes back via satellite. The hardware > >> alone is going to cost me $1100.00 + sales tax(%12.5)NZD. All the other > isp > >> wanted to charge me over $1000.00 a month + hardware on top. > >> > >> B.Rumsey > > > >Wow! What's the conversion rate between NZD and USD? > >How can you justify the expense of that type of internet connection? > > > >-- > > __ _ > > / / (_)__ __ ____ __ > > / /__/ / _ \/ // /\ \/ / Jerry L Kreps > > /____/_/_//_/\_,_/ /_/\_\ > > > > > > > >-- > >To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com > >For additional commands send e-mail to suse-linux-e-help(a)suse.com > >Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ > > -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0