Greetings : I'm running SuSE 6.2 and am having some problems with YaST... if I add a user to my system, then try to send mail to that user, or su to that user, or do anything to that user, I get a 'User does not exist' error. HOWEVER, the user is listed in both the shadow and passwd files, belongs to a vaild group, has a mail spool and a home directory. I'm more that a little confused. :) Any help here would be greatly appreciated. Regards, Bryan Porter
Bryan Porter wrote...
Check the /etc/shadow file and make sure that user isn't pre-expired. here are the fields: 1) username 2) encrypted password 3) days since 1/1/1970 password was last changed 4) days before which password may not be changed 5) days after which password must be changed. 6) days before password is to expire that user is warned of pending password expiration. 7) days after password expires that account is considered inactive and disabled. 8) days since Jan 1, 1970 when account will be disabled. 9) reserved for future use. I have seen programs like useradd, etc. add a user with a pre-expired password. josh
At 14:07 21.09.99 -0500, you wrote:
Don't use nscd (name service cache daemon) and it works! If you want to use nscd, edit /etc/nscd.conf: enable-cache passwd no enable-cache group no ----------------------------------------------------------------------- Peter Griessl, System Administrator email: griessl@ihs.ac.at Institute for Advanced Studies Tel: +43-1- 599 91 222 Stumpergasse 56, A-1060 Vienna, Austria Fax: +43-1- 597 06 35 -----------------------------------------------------------------------
Don't use nscd (name service cache daemon) and it works!
By the way: what is/does nscd? and why the hell it is enabeld by default? (I hate programs beeing enabeld by default and I don´t know what they are doing. There is no Information on SuSE 6.2 about it (e.g. a manpage or anything else) and after upgrading to SuSE6.2 there was this new obscure demon running - I kicked it at once) (And on some machines it caused some trouble so that they weren´t able to connect to some other machines on the net) I think all these demons (nscd, httpd,.....) should NOT be enabeld/started by default by /etc/rc.config (SuSE). Especially for a Linux-new-users it is difficult to oversee what all these demons are for and he does not know that they could be security risks. +-+
what is/does nscd?
daemon to speed up name service requests (user, hosts, ...) (query SuSE Support Database for "nscd", I didn't find any other information)
absolutely right ----------------------------------------------------------------------- Peter Griessl, System Administrator email: griessl@ihs.ac.at Institute for Advanced Studies Tel: +43-1- 599 91 222 Stumpergasse 56, A-1060 Vienna, Austria Fax: +43-1- 597 06 35 -----------------------------------------------------------------------
Hi all!
It should be very useful, if further yast-versions asks the user whether his host acts as standalone client or server. Liebe Gruesse, Stephan Lauffer [ Paedagogische Hochschule Freiburg - Systemtechnik - Germany ] [ ZIK Zentrum fuer Informations- und Kommunikationstechnologie ] [ Tel.: 0761 - 682 459 Mobil: 0172 - 7145 197 ]
On Wed, 22 Sep 1999, Stephan Lauffer wrote:
It should be very useful, if further yast-versions asks the user whether his host acts as standalone client or server.
And then give the user a choice of what demons it wants run, and then warn the user of the security risks involved with the running of that demon, possibly by directing them to some security documentation. Most users will be unaware of what demons are running, and what those demons are, so they're unlikly to know about the security of them. More advanced users are less likly to use yast for getting demons started. Just an idea. cog -- ,------------------------------, ,====================| S H U N A N T I O N L I N E |===================, | David M. Webster '------------------------------' (aka cogNiTioN) | |=======================================================================| | cognition@bigfoot.com |=============| cognite.net will be online RSN. | '====== I use Linux everyday to up my productivity - so up yours! ======'
Hi all!
Maybe - if you´re the sysadmin of a server, you must check and modify the system in any cases. A "normal user" instead normally does not have a internet connection 24h a day and also no static ip-adress. So it´s not very important, if the security-level of the system is not very high. Liebe Gruesse, Stephan Lauffer [ Paedagogische Hochschule Freiburg - Systemtechnik - Germany ] [ ZIK Zentrum fuer Informations- und Kommunikationstechnologie ] [ Tel.: 0761 - 682 459 Mobil: 0172 - 7145 197 ]
On Wed, 22 Sep 1999, Stephan Lauffer wrote:
Sounds like Security Through Obscurity. That, "...is the microsoft approach... and should never be allowed" [-- Linus Torvald] Besides I don't want programs I not using running all the time. most normal users don't need to be running httpd/ftpd/telnetd/etc.., so why spend valuable resources (and they are on my 486) running these useless programs. (Useless to people who don't have a use for them, before I get flamed for saying apache is a useless program, full stop.) cog -- ,------------------------------, ,====================| S H U N A N T I O N L I N E |===================, | David M. Webster '------------------------------' (aka cogNiTioN) | |=======================================================================| | cognition@bigfoot.com |=============| cognite.net will be online RSN. | '====== I use Linux everyday to up my productivity - so up yours! ======'
Hi all! I don´t want to increase the traffic on this list about this diskussion, but...
By the way; pop3, imap, ftp, telnet, samba without encrypt passwords, nis are not secure. So, if you´re planing to sell a secure distribution, you must not distribute netscape, because all users can configure a pop3 account. ;) pop3 without ssl, oder imap without ssl is a high risc. Maybe now you understand my comment right: "So it´s not very important, if the security-level of the system is not very high". Secure systems are in any cases important - but I think, you can´t define it deffinetifly when a distribution is good enough. Ok, I´m quite. :) Liebe Gruesse, Stephan Lauffer [ Paedagogische Hochschule Freiburg - Systemtechnik - Germany ] [ ZIK Zentrum fuer Informations- und Kommunikationstechnologie ] [ Tel.: 0761 - 682 459 Mobil: 0172 - 7145 197 ]
On Wed, Sep 22, 1999 at 14:56 +0200, Stephan Lauffer wrote:
I HATE this point for being so dangerous and yet so widespread. Dymanic IP gives you NOTHING in regard of security and "normal" users MAY have internet sessions of a couple of hours in a week. And when working with computers, one second can be VERY long ... Make EVERY computer as safe as possible and think of EVERY data as being worth to be protected! virtually yours - Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.
I have personally witnessed break-ins on MSWinXX machines using dynamic IPs over dial-up lines. Port scanners are often used by malicious ( and otherwise ) hackers to find vulnerabilities in systems on an ISP ( it is much easier to find a target by scanning ISP users for vulnarabilities than it is to find one using a random IP off the net. ISPs generally own one C class subnet or so, and rent out the last four digits to users dynamically. Ignoring security issues and trusting the upstream to do it for you does _not_ make them go away. It just makes users lazy in their regard to security, which puts corporate and home networks at risk. Robert_Helmer http://robert.namodn.com Stephan Lauffer wrote:
On Wed, 22 Sep 1999 you wrote:
Anyway, you should always disable EVERY daemon until you know exactly what it does and how to configure. Now, there are two ways to go: a) If you don't install a daemon that you don't know it won't be enabled by default/yast. It's much better to read the man page first -and install a daemon if it is needed. b) If you choose a standard installation with various daemons check your /etc/inetd.conf, disable all unknown daemons (that are enabled by yast) and edit your configuration file (in that you can disable those daemons). One paper to start securing linux ishttp://www.interact.com/~lspitz/linux.html and, if you are more interested in security, the 'Know Your Enemy'-series that you can find in .../~lspitz/pubs.html. Subscribe to bugtraq. Read Howtos and man pages.... -- ----------------------------------------------------- Martin Peikert EN 636 TU Berlin fon 314-23881 Sekretariat EN 2 fax 314-22284 http://www-tet.ee.tu-berlin.de/peikert/index.html -----------------------------------------------------
No problem to do this for somebody who knows Linux well. But even userers who are using Linux now for more than 2 years do not know a lot about the interns and the relatet security-risks. 99% of them do not know "Know Your Enemy" and 99% of them use some "Standard-Installation". And they aren´t that able to edit conf and rc scripts. (BTW: for nscd there seems to be no manpage/documentation. And I do not remember beeing asked at installation if I want to install nscd or not.) Hartmut
On Wed, 22 Sep 1999 you wrote:
Absolutely true.
And they arenŽt that able to edit conf and rc scripts.
They don't need to. It's an option in yast: edit configuration file. There you can decide if you want to start a daemon or not. By default, the most of them is enabled - that's a problem if you are connected to the internet permanently. In that case your sysadmin should configure the box. For home users I think it would be secure enough to disable inetd.
(BTW: for nscd there seems to be no manpage/documentation. And I do not remember beeing asked at installation if I want to install nscd or not.)
ARGH! What are you doing, SuSE?
Hartmut
Martin
And they aren´t that able to edit conf and rc scripts.
They don't need to. It's an option in yast: edit configuration file.
That is (nearly) the same for those kind of useres. The "Konfigurtionsdatei verändern" in Yast is still very long an cryptic even for slightly advanced users.
I´m talking about all those boxes that are indeed 24h connected to the net, standalone desktops at Universities etc., or as Derek just told homecomputers of " "power user" != "knowledgeable system administrator" " with 24h/statics (I think we will have those here in germany too sometime in the future). (Btw: at home a lot of people also need inetd running because they have a small home-network running) And these useres are almost their own sysadmins! I thing it is good that people emigrate from that frustrating, time-wasting m*-tr**h but this doesn´t mean Linuxinstallation/-administration needs less time or is much easier (but you are much more successfull :-) ). What has to be done by a Linuxdistribution (imho) is to give the (new-)user an (self-)explaning and transparent system and the information and the right consciousness (about network-secuity... and so on) to run such a system - even when it is online on the net! This is the difference with Linux! You are ALLOWED TO and you CAN DO EVERYTHING (nearly) with your system! Everything means everything - in Good as in Bad, knowingly or ignorant!
Yes, SuSE-6.2. Thats the reason why I am posting here at [suse-security] ;-) -------Markus Gaugusch wrote: ------ nscd is included in shlibs.rpm and related files are (I think): [output of rpm -ql shlibs |grep nsc] /etc/nscd.conf /usr/sbin/nscd /usr/sbin/nscd_nischeck ------------------------------ Yea, that is all I found! :-(( So, hey ho, lets go... Hartmut
I must disagree with your statistics. I hardly think that 99% of users that have been using a GNU/Linux system for at or around 2 years does not know anything about system configuration. The first thing I discovered when I booted my first SuSE install was that squid was grinding up my HDD and the "default install" had loaded all this crap on there ;) Anyhow, I prefer to configure the programs themselves, but under something like SuSE or any other commercial distrib, they supply tools such as YaST to easily configure your system, even if editing a self-documented file is a bit too much for someone. I do agree that many users only know vague details of system internals, but I hardly consider basic system configuration to be reserved only for GNU/Linux experts. As far as I remember, YaST was made fairly accessable through SuSE's default interface that they adapt to the various windowmanagers. Mayhaps the GUI interface part can be made easier for the end user? Robert_Helmer http://robert.namodn.com Hartmut Gerlicher wrote:
Dear dproc@dol.net, concerning your mail sent on Wed, 22 Sep 1999 let me reply tho following:
I'm sorry, it is http://www.enteract.com/~lspitz/linux.html Martin
* Hartmut Gerlicher (h.gerlicher@tu-bs.de) [19990922 13:25] spoke: [...] | what is/does nscd? | | and why the hell it is enabeld by default? | | (I hate programs beeing enabeld by default [...] I enjoyed reading this thread. Yes, most of you *hate* sloppy default-setups, and those security holes a SuSE-System has, if used by an unexperienced user. But, i think it's not fair to blame SuSE for that ( well, especially if they documented their policy anywhere... e.g. drop a note about things like nscd..) they do a damn good job in helping unexperienced users to get a working system set up, a system that *can* be made secure afterwards, without having to build from scratch. A newbie *can* use it out of the box, can play and test a lot, without having to bother to get the stuff simply to run. Imagine, how disappointing it is for a newbie, if he *cant* test all that funny services on his localhost, if he had to wander through all collected wisdom of wizardhood, just for getting to know how a UNIX behaves. Of course, this system *can not* be perfectly secure, by far not secure enough for a cable connection w/ statIP. You have to know what you're doing then, and YaST *can* be a valuable help then ( can be a threat also.. ;-) ). I'd suggest to the SuSE-People to prepare some kind of 'profile', with an outline of a setup for various tasks, and ask the user, if he wants a machine for standalone, family or www-server use. These set of permissions from "easy" to "paranoid" is already a good idea; why not try something in this fashion for the services ? Maybe increase the verbosity-level of package selection ( "hey U idiot, don't tell me U want *that* package on a server ? No, i won't install that." ) ;-) Bye ! -- Gruss / with best regards Jens-Eike Jesau <jens@hp9001.fh-bielefeld.de> /*************************************************************************** * `v'- Home: hp9001.fh-bielefeld.de/~jens * || |`. Linux on a single Disk: www.toms.net/rb * " The number of UNIX installations has grown to 10, with more expected " ( The UNIX Programmers Manual, 2nd Edition, June 1972.) */
Jens-Eike Jesau wrote:
Hi Jens,
I was about to write along the same line, but in the end didn't dare.
I am not a newbie anymore, but I am utterly confused by all these services, deamons and particulary what they are good for. Since I do not exactly know what to look for or ask, the amount of stuff to read (=time to spend) is enourmous.
Well, it does not need to be SuSE by the way. Imagine a "tool" that "edits" or "recreates" the relevant files in a style the kernel config works. If I press help in there, I get a nice description about an uncomprehensive option in a mostly umcomprehencive help text ending with "If you don't know what we talk about you probaply won't need this." or "It's save for most users to say NO here". I Like that ;-) One of my personal fears is something like the "windows effect". You install a new small tool that works perfect and two weeks later when you use your scanner the next time, it won't work. I fear similar things happen with disabled services. I know this is a lame comparision, but that's what I fear. Anyway, I had a look into /etc/inetd.conf and disabled pop3, talk, ntalk, finger, (what the heck is "ident"?), btx and midinet by double "##" them, to find the stuff easier... Juergen
-- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| /\\ /__/ / _ \/ // /\ \/ / ==========================================_\_v __/_/_//_/\_,_/ /_/\_\
On Sun, Sep 26, 1999 at 10:34 +0200, Juergen Braukmann wrote:
I think the catchword we're looking for is "AWARENESS" which has to be "injected" into an administrator's mind at installation time. It has to be obeyed (and freshened?) when further configuring the system. And to be of real use and effectiveness, knowledge should be its companion. But that's an ideal hard to reach ...
A newbie *can* use it out of the box, can play and test a lot, without having to bother to get the stuff simply to run.
That's ONE approach: Offer any service (read: "potential hole") and block away what is not needed. When you're lazy or unsure, you won't take any action, since "everything works". This one seems most similar to what a newbee would like (and what's common in other operating systems' areas). The other approach is to install an almost nonfunctional (in terms of application software) system which just offers the ability to configure itself. Then one could build up the services nessecary for one's own purposes. The result will be slim and fits perfectly to what it is meant to do. This one requires skill and most of all knowledge (I guess "orientation" is what newbies lack most, following a learning route once you know what you WANT should be easy to do). On the other hand -- everyone who has built up a system this way KNOWS what he has done. And since one saw it "grow" there's more understanding for the relations of the components inside, which I feel is a great point for free UNIXes (and what attracted me most and kept me with these for several years now). A compromise would be to install a minimal system AND some additional services, which is done by almost every distribution available these days. But I wouldn't know WHERE to place the warning "never run an unconfigured system" and "always know what you're doing and do it consiously(sp?)". I just think of the fact that YaST creates a normal user and despite people run around as root. I guess that is the habit of "I paid the hardware, so I want to be the master. How can a computer dare to stop me from doing something?" I didn't quite settle down in computer users' minds that restriction could be some sort of self defence. It seems hard to teach people in a polite way that "easily setup" means "almost unconfigured if at all useful". Nothing comes for free. Where should all the advantages come from Linux is said to have if not from the APPROPRIATE use of the mechanisms?
But I never had to regret the effort I spent to learn the UNIX mechanisms. I always got something in return: flexibility, stability, knowledge (applicable in other fields, too), fun (don't underestimate the feeling of "having something mastered AND doing it the right way(TM)").
Wasn't there mention of a SuSE hardening project (or script at least)? AFAIR this one asked some questions to create a profile of the intended use and took some action to customize some of the system's configuration. Didn't this make it into the newer releases?
( "hey U idiot, don't tell me U want *that* package on a server ? No, i won't install that." ) ;-)
I could accept the installer buzzing on me when I tried stupid things. But I would never want a software telling me "I know better than YOU do" -- that's exactly what drove me away from Windows ... Keep in mind "UNIX was not designed to stop its users from doing stupid things, as that would also stop them from doing clever things." :>
Once you reach a stage of interest for "is it configured properly" you're free to release the hounds, i.e. run Cops and Nessus and Satan and nmap against the machine. 'ps aux ww' and 'netstat -an' is something one anyway issues after installation. But then again, one should be able to judge the output -- I see the problem ("Ein Teufelskreis ..." :). But I always prefer things pushing me to learn how to handle a new tool in an appropriate way -- this way I get much more from using it. If I just want to keep stuck with old behaviour I might miss the actual advantage of the tool: I won't get any effect or not what I expected, maybe I even break some things. If I squeeze a new tool to behave like the old one, I could have stuck with the old one (which saves me from the effort of changing my tools at all).
That's the case when disbling something that was there before (and you didn't know what it was good for). That's NOT happening when you configure a system to fit your needs in the beginning and ADD features as you need them. The hard way I sketched above is just a special form of it: Deliver a skeleton and fill it with every function YOU need assuming NOTHING at the delivering party. I'm ALWAYS uncomfortable with default setups, since they NEVER meet MY requirements. I feel there's no real problem with technical aspects, it's the mind barrier: "I did it this way under Windows, I want to do is THIS way under Linux. And it doesn't work. Linux is crap!" It seems VERY hard to understand that UNIX is somewhat different. But once that's understood (and accepted, which makes people act differently) the result is great: anything is possible. "addicted to a scheme" seems to be a problem here. How hard is it to tell somebody that every feature has a downside (the ones even believing in the nice colored advertisements don't know better)? Should there be some bugtraq reading for the amusement of the admin (at the desktop: joe average user?) while YaST copies packages in background? BTW the repetition of always the same mistakes is somewhat scary -- will people never learn? "Those who don't know the past are doomed to reimplement it". And the accumulation of always the same program names (and companies) seems symptomatic. Another point comes to mind and is hard to teach, too: Security cannot be "delivered". It's not an automatic thing you can install. It's a point of view, it's a progress, it's the action one takes (again and again, learning and evolving on the way). A distribution can just create a sense or sharpen it, it's always the admin implementing it. And Linux users should get into their head that they ARE admins. If that's too much work for me, I should take the consequence and quit that job. I would never make a difference between private and professional security, but in maximum between isolated installation and connected computers. I don't see a point in saying "I won't be attacked since I'm just a newby sitting at my home computer". People really should realize what they do when putting the plug into the wall socket. virtually yours - Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.
Hi, blessed Linux-friends ! * Juergen Braukmann (juergen.braukmann@ruhr-west.de) [19990927 00:01] spoke: | Jens-Eike Jesau wrote: | > * Hartmut Gerlicher (h.gerlicher@tu-bs.de) [19990922 13:25] spoke: | > | > [...] | > | what is/does nscd? | > | | > | and why the hell it is enabeld by default? | > | | > | (I hate programs beeing enabeld by default | > [...] | I am not a newbie anymore, but I am utterly confused by all these | services, deamons and particulary what they are good for. Since I do not | exactly know what to look for or ask, the amount of stuff to read (=time | to spend) is enourmous. I suggest to digest this very intersting thread into one demand to the SuSE-People: Please, go on making such a nice distro, but, *PLEASE* document your policy somewhere, at least in some lines ! Just some words about the services enabled by default, some little enrty in the sdb ( fine thing, anyway), just to tell the littlebit advanced user about it. I hate to throw stuff out of the system, that might have been very well thought about by the SuSE-People, but i *have* to kill it just because i can't find out what it is. Especially when there is a very skillful solution in some script, it ist not that easy to understand. Remember, you are addressing the experienced users, so some hints may already be *very* helpful. Bye ! -- Gruss / with best regards Jens-Eike Jesau <jens@hp9001.fh-bielefeld.de> /*************************************************************************** * `v'- Home: hp9001.fh-bielefeld.de/~jens * || |`. Linux on a single Disk: www.toms.net/rb * " The number of UNIX installations has grown to 10, with more expected " ( The UNIX Programmers Manual, 2nd Edition, June 1972.) */
Hello! Since I updated the system from Linux 6.1 to 6.2 I do have the same problem as you described. I thought the problems come from an incorrect update. Since I wanted to use a new disk, I had mirrored the system before the update. Afterwards the update could not be executed up to the end. After I had executed an update of the system on the old disk, everything was o.k. so far. Unfortunately there are problems when creating a new users. The error message "user does not exist" does not appear after a reboot. Also I would be pleased about a note to the recovery of the error. Regards, Willy Sturm Bryan Porter wrote:
* Bryan Porter <bporter@epctech.com> writes:
This is a known problem with SuSE 6.2 and nscd. You'll find a short description of the problem and a solution in SuSE's support database. German URL: <http://www.suse.de/sdb/de/html/kukuk_nscd.html> I noticed some problems with nscd and "The Internet Junkbuster" (ijb). Sometimes multiple sessions of ijb were started. After I had disabled nscd the problems were gone. Anyone experiencing the same behavior? -- Mark Lutz Accept German and English
On Wed, 22 Sep 1999, Mark Lutz wrote:
yes i did. ijb isn't working properly with started nscd ... why ? thx nolo -- --- Manuel Paul [dAx] ================= email: nolo@altavista.net www: www.homepages.de/home/iwarf ICQ: 15775184 (preferred) PGP: Key is available at any server ----------------- There're many things that will be left unexplained. It's your thirst of knowledge that will find the answers. As the structural figure of our mind resembles our own, it might be predictable to forecast the future. Then again, maybe not. - Man from tomorrow - -----------------
Bryan Porter wrote...
Check the /etc/shadow file and make sure that user isn't pre-expired. here are the fields: 1) username 2) encrypted password 3) days since 1/1/1970 password was last changed 4) days before which password may not be changed 5) days after which password must be changed. 6) days before password is to expire that user is warned of pending password expiration. 7) days after password expires that account is considered inactive and disabled. 8) days since Jan 1, 1970 when account will be disabled. 9) reserved for future use. I have seen programs like useradd, etc. add a user with a pre-expired password. josh
At 14:07 21.09.99 -0500, you wrote:
Don't use nscd (name service cache daemon) and it works! If you want to use nscd, edit /etc/nscd.conf: enable-cache passwd no enable-cache group no ----------------------------------------------------------------------- Peter Griessl, System Administrator email: griessl@ihs.ac.at Institute for Advanced Studies Tel: +43-1- 599 91 222 Stumpergasse 56, A-1060 Vienna, Austria Fax: +43-1- 597 06 35 -----------------------------------------------------------------------
Don't use nscd (name service cache daemon) and it works!
By the way: what is/does nscd? and why the hell it is enabeld by default? (I hate programs beeing enabeld by default and I don´t know what they are doing. There is no Information on SuSE 6.2 about it (e.g. a manpage or anything else) and after upgrading to SuSE6.2 there was this new obscure demon running - I kicked it at once) (And on some machines it caused some trouble so that they weren´t able to connect to some other machines on the net) I think all these demons (nscd, httpd,.....) should NOT be enabeld/started by default by /etc/rc.config (SuSE). Especially for a Linux-new-users it is difficult to oversee what all these demons are for and he does not know that they could be security risks. +-+
what is/does nscd?
daemon to speed up name service requests (user, hosts, ...) (query SuSE Support Database for "nscd", I didn't find any other information)
absolutely right ----------------------------------------------------------------------- Peter Griessl, System Administrator email: griessl@ihs.ac.at Institute for Advanced Studies Tel: +43-1- 599 91 222 Stumpergasse 56, A-1060 Vienna, Austria Fax: +43-1- 597 06 35 -----------------------------------------------------------------------
Hi all!
It should be very useful, if further yast-versions asks the user whether his host acts as standalone client or server. Liebe Gruesse, Stephan Lauffer [ Paedagogische Hochschule Freiburg - Systemtechnik - Germany ] [ ZIK Zentrum fuer Informations- und Kommunikationstechnologie ] [ Tel.: 0761 - 682 459 Mobil: 0172 - 7145 197 ]
participants (15)
-
Bryan Porter -
cogNiTioN -
dproc＠dol.net -
Gerhard Sittig -
Hartmut Gerlicher -
Jens-Eike Jesau -
josh -
Juergen Braukmann -
M.Paul <nolo＠altavista.net> -
Mark Lutz -
Martin P. Peikert -
Peter Griessl -
Robert Helmer -
Stephan Lauffer -
Willy Sturm