From: Digestifier To: Linux-Admin@senator-bedfellow.mit.edu Reply-To: Linux-Admin@senator-bedfellow.mit.edu Date: Tue, 7 Sep 93 13:28:08 EDT Subject: Linux-Admin Digest #38 Linux-Admin Digest #38, Volume #1 Tue, 7 Sep 93 13:28:08 EDT Contents: Bootdisk made by SLS install hangs during boot (Cornell Kinderknecht) Re: Long shadow passwords less secure than normal ones? (Ruediger Helsch Ramz) Wangtek 5150ES & DC300 carts (Bob Knight) SLS 1.03 and tcp/ip (11086) Re: Printers and Linux (Jon Brawn) Cirrus Textmode (Kai Kretschmann) Re: "lpd" won't run (Alexey Loginov) Re: XDM bug/Shadow passwords. (Jeremy Bettis) Where's the PostScript stuff for groff? (Rick Miller) Re: Long shadow passwords less secure than normal ones? (Peter Gutmann) Booting from hard drive with SLS 1.03 (C Wayne Huling) ---------------------------------------------------------------------------- Crossposted-To: comp.os.linux,comp.os.linux.misc,comp.os.linux.help From: cornell@syl.dl.nec.com (Cornell Kinderknecht) Subject: Bootdisk made by SLS install hangs during boot Reply-To: cornell@syl.dl.nec.com Date: Mon, 6 Sep 1993 17:03:25 GMT SLS version: 1.03 Machine1: NEC Powermate 386 Machine2: Amax PC/386 I've installed the SLS v.1.03 release on three machines. The two listed above had the same trouble after installing, making a bootdisk, and trying to boot from that bootdisk. The trouble that came about was when I tried to boot from the bootdisk (5.25" floppy drive A:). Just after it prints out that it's trying to detect sound cards (one of the machines has no sound cards and the other has a PAS), it just sits there and never goes on. Can anyone help me get beyond this? I've been booting from the install disk and telling LILO to go to the harddisk where it's installed but I'd really like to get the boot floppy to work. The boot messages are included at the bottom of this post. The third machine that I installed on (an Insight 486 with a PAS16) boots fine off of it's boot floppy. --- Cornell ==== messages at boot time ==== Loading............................ Uncompressing Linux...done. Now booting the kernel. Console: colour EGA+ 80x25, 8 virtual consoles Serial driver version 3.96 with no serial options enabled tty00 at 0x03f8 (irq = 4) is a 16450 tty01 at 0x02f8 (irq = 3) is a 16450 tty03 at 0x02f8 (irq = 3) is a 8250 lp_init: lp0 exists (0), using polling driver lp_init: lp1 exists (253), using polling driver lp_init: lp2 exists (253), using polling driver Detecting soundcard: ProAudioSpectrum (type 3). PAS2: Found a Pro AudioSpectrum 16 board, revision 255. IRQ = 7, DMA = 3 AdLib compatible FM chip detected and initialized Detecting soundcard: SoundBlaster (type 2). Detecting soundcard: AdLib (type 3). and then we sit and wait forever...... (of course the machine without a soundcard does not print the message about the PAS) -- | Cornell Kinderknecht Email: cornell@syl.dl.nec.com | | CSTC/CNAD | | NEC Systems Lab./NEC USA Phone: 214-518-3509 | | Irving, TX (Dallas) Fax: 214-518-3552 | ------------------------------ From: ruediger@ramz.ing.tu-bs.de (Ruediger Helsch Ramz ) Subject: Re: Long shadow passwords less secure than normal ones? Date: Mon, 6 Sep 1993 18:28:40 GMT The 16-character handling of the shadow password package seems suboptimal. Though I think it is better than the standard Unix procedure which discards everything but the first eight characters: At our place I cracked the passwords of some users, and found they had used long words with some special characters, but the first eight characters formed a simple word. How could they know that their good passwords were silently truncated? I think the best solution would be to XOR the characters past the eighth character with the others, like this: ThisIsAV eryLongA ndGoodPa ssword -------- (XOR characters in the same column). XXXXXXXX (Crypt this value) The XORed password would form a pretty random and difficult to guess word. This would work with arbitrary long passwords, and it would be compatible to systems that don't use this procedure as long as short passwords are used. Ruediger Helsch ------------------------------ Subject: Wangtek 5150ES & DC300 carts From: knight@santafe.santafe.edu (Bob Knight) Date: 6 Sep 1993 20:08:36 GMT Hi - I have a bunch of DC300 tapes lying around that I'd like to use with said QIC drive. Anyone successfully done so under Linux? Thanks in advance. Please email me so as to conserve net.bandwidth. Bob ------------------------------ Crossposted-To: comp.os.linux.help From: u1086aa@unx.ucc.okstate.edu (11086) Subject: SLS 1.03 and tcp/ip Date: Mon, 6 Sep 1993 20:50:02 GMT I just upgraded to SLS 1.03 and am having trouble getting tcp/ip going. I am using an ne2000 clone board with IRQ=5 and I/O memory at 0x300. It is detected fine on startup, and rc.net is being run. I configured by editing the /etc/inet/hosts file and running hostcvt.build. (In fact, I saved the hosts file from the earlier release and tried it also.) Whenever I try to telnet out I get the message telnet: Unable to connect to remote host: Network is unreachable The same hosts file worked perfectly with the earlier SLS release (1.01, I believe). When I try to telnet in from another machine connection is made, and the Linux console echos: ARP: Bad packet received on device "eth0" ! I'm pretty sure the board is ok because it works fine with DOS. I tried moving the board to IRQ 2, but it was detected on IRQ 9 at boot and didn't work either. Has something changed since with new release of SLS that I am missing? Any help will be greatly appreciated! Jim ========== My opinions are my own Jim West Associate Professor Electrical and Computer Engineering Oklahoma State University jwest@jwest.ecen.okstate.edu ------------------------------ From: jonb@specialix.com (Jon Brawn) Subject: Re: Printers and Linux Date: Mon, 6 Sep 1993 19:29:15 GMT tracey@cs.wm.edu (Tracey Beauchat) writes: >I want to set up a printer on my PC running Linux. I am Me too >familiar with printers on Unix systems, and so I am assuming >it is set up the same basic way in Linux. I am familiar with System V print schedulers - I know nothing about lpd and friends. >Thanks for any help, >-Tracey So, I have SLS 1.2 (1.02?), net2 stuff installed, etc... WHERE do I go to find the correct info on how to setup printers on this system? [RTFF answers are fine, so long as they tell me *where* the FAQ is, and what its called]. ------------------------------ From: kai@fix.kmk.rhein-main.de (Kai Kretschmann) Subject: Cirrus Textmode Date: Mon, 6 Sep 1993 16:28:15 GMT How can I use other text modes in my VCs than only the standard 80x28 and 80x50? I have a Sigma legend 24LX which has an CL-GD5426 on it. The kernel source seems to support Cirrus modes like 100x and 132x, but when I select ASK_VGA, it only displays me the two simple modes mentioned above. Kernel version is 99pl12 with Linus' patches. Any help or hint welcome. -- Kai Kretschmann, >>> FidoNet: 2:248/312, 21:100/5729, 16:100/6006 <<< >>> Internet: kai@fix.kmk.rhein-main.de <<< >>> FAX/BBS: +49-6172-305379 <<< ------------------------------ From: loginov@doc.cc.utexas.edu (Alexey Loginov) Subject: Re: "lpd" won't run Date: 6 Sep 93 19:09:36 I can't get lpd to work either - I have the same symptoms that Chris has. I type lpd and it just returns. I have set all the permisions as suggested (in addition to the setgid etc. described in the installation) and created the /usr/spool/lpd with 775, and it still just returns. In article <1993Sep1.131112.1571@knobel.knirsch.de", Andreas Klemm (andreas@knobel.knirsch.de) writes: "chris@chrism.demon.co.uk (Chris Marriott) writes: " ""I've just installed the SLS 1.03 linux implementation on my 486/33. I'm ""trying to get printing working, following the instructions in the FAQ. ""I have a printer on LPT1: which works - I can copy a file to /dev/lp1 and ""it prints fine. " ""My problem is that the printer daemon "lpd" refuses to run. If I run it, ""it terminates with no error messages immediately (exit code 0, if that ""helps). When I try to print through "lpr" I get the message "job queued, ""but no daemon present". When I run the printer control program lpc and ""give the "restart" command I get the message: " "" lp: "" cannot open lock file "^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ "" lp: "" lpc: connect: No such file or directory "" couldn't start daemon " ""I've edited the "printcap" file to simply say: " "" lp:\ "" :lp=/dev/lp1:\ "" :sd=/usr/spool/lp1:\ "" :mx#0: " ""I've create the directory "/usr/spool/lp1". " "Since the lpd program doesn't run under a certain "meta" user id "lp or daemon, it runs under the user id of the user, who initiated "the print job .... "Therefore each user needs permission for reading and writing in "the spool directory. My spool directory - as predefined in the "SLS 1.01 installation - has the permissions rwxrwxrwx like /tmp. " "Do a chmod 777 /usr/spool/lp1, and it should work ... "-- "/-\ Andreas Klemm Daniel T. Schwager (danny@dragon.stgt.sub.org) wrote in <1993Sep2.181414.8524@dragon.stgt.sub.org>: >>Download the shadow-version of xdm from sunsite or tsx. >I downloaded the file /pub/linux/sources/usr.bin.X11/xdm-shadow.tar.Z >from tsx-11 and can't get it to compile. I am using SLS 1.03 with >the shadow suite. It dies while linking verify.c, complaining >that the symbol _valid is referenced in the text segment but undefined. >I looked in verify.c and indeed it makes a call to some function valid() >which I've grepped for on my system but can't find anywhere. The valid() function call in the the shadow lib, although the version which came with SLS 1.02 had an error in the makefile which caused valid.o NOT to be included in libshadow.a. The recent posting of the shadow suite to comp.sources.misc (or was is c.s.unix ? I don't recall) did not have this problem. -- Jeremy Bettis -*- Jerbo Jehoshaphat -*- University of Nebraska INET: jbettis@cse.unl.edu "Those who stand in the middle of the UUCP: jerbo@tddi.UUCP road are often hit by passing cars." Running Linux .99p11 Free Unix for i386/i486 machines. Ask me how. ------------------------------ From: rick@ee.uwm.edu (Rick Miller) Crossposted-To: comp.os.linux.help,comp.os.linux.misc Subject: Where's the PostScript stuff for groff? Date: 7 Sep 1993 13:10:14 GMT I've got all the nifty groff stuff that came with the SLS-1.03, but it doesn't seem to include a directory needed by "groff" to produce PostScript output. The error I get is: gtroff: can't open `DESC' gtroff: fatal error: sorry, I can't continue I looked around with "find" and have deduced that I need a directory called "/usr/lib/groff/font/ps" (which would contain the file DESC, among others). So, where do I find this directory? (...and why wasn't it included in SLS?) RICK MILLER Voice: +1 414 221-3403 P.O. BOX 1759 FAX: +1 414 221-4744 MILWAUKEE, WI Send a postcard and I'll send one back. 53150-1759 USA Sendu bildkarton kaj mi retrosendos unu. ------------------------------ From: pgut1@cs.aukuni.ac.nz (Peter Gutmann) Subject: Re: Long shadow passwords less secure than normal ones? Date: Tue, 7 Sep 1993 13:24:29 GMT In <1993Sep6.182840.8481@ibr.cs.tu-bs.de> ruediger@ramz.ing.tu-bs.de (Ruediger Helsch Ramz ) writes: >The 16-character handling of the shadow password package seems suboptimal. >Though I think it is better than the standard Unix procedure which discards >everything but the first eight characters: At our place I cracked the passwords >of some users, and found they had used long words with some special >characters, but the first eight characters formed a simple word. >How could they know that their good passwords were silently truncated? >I think the best solution would be to XOR the characters past the eighth >character with the others, like this: > ThisIsAV > eryLongA > ndGoodPa > ssword > -------- (XOR characters in the same column). > XXXXXXXX (Crypt this value) This is a Bad Thing. xor is a linear transformation - all you'll be doing is flipping bits in some predetermined manner (eg if you map 16 -> 8 chars by xoring then you'll end up clearing the high bits which the two lots of chars will have in common). Since people will use standard phrases rather than `P8;!KL,2P,)!PL)"PD'%@<(!@4&!P8%-@<6%PL*!@@*"P4&%00&%P4*"`4&' as long passwords, it will allow you to perform a frequency analysis of the language in use and determine the most common bit patterns which will result from this xor-ing. The longer the password, the closer the statistical analysis will be to the real text. You can then use the probable bit-patterns to mount an attack. This may even be easier than an attack on the standard password system. I'll repeat again what I said in a previous message, if you're going to make an incompatible change you may as well use a secure algorithm like MD5 or SHS to do it. Peter. -- pgut1@cs.aukuni.ac.nz||p_gutmann@cs.aukuni.ac.nz||gutmann_p@kosmos.wcc.govt.nz peterg@kcbbs.gen.nz||peter@nacjack.gen.nz||peter@phlarnschlorpht.nacjack.gen.nz (In order of preference - one of 'em's bound to work) -- Nostalgia isn't what it used to be -- ------------------------------ From: wayne@rose.cs.odu.edu (C Wayne Huling) Subject: Booting from hard drive with SLS 1.03 Date: 07 Sep 1993 14:11:11 GMT I have set the boot flag from fdisk, and written the partition table back, but is still won't boot from the hard drive? Could someone please enlighten me? Wayne ------------------------------ ** FOR YOUR REFERENCE ** The service address, to which questions about the list itself and requests to be added to or deleted from it should be directed, is: Internet: Linux-Admin-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux.admin) via: Internet: Linux-Admin@NEWS-DIGESTS.MIT.EDU Linux may be obtained via one of these FTP sites: nic.funet.fi pub/OS/Linux tsx-11.mit.edu pub/linux sunsite.unc.edu pub/Linux End of Linux-Admin Digest ******************************