Nguyen H.Vu wrote: >Hi all, > >This is /etc/motd of FreeBSD. I think that this is a very good idea. The >purpose of this file is very simple: Pop up a security warning when user login >in console mode. > Actually KDE already issues a warning to anyone loging in as root. And those who know enough to use the CLI should already be aware of root issues. The very long standing purpose of /etc/motd is to serve as a local broadcast tool. I think it should probably remain that even though the FreeBSD people apparently think otherwise.
> > >Another file LM should improve is /etc/issue and /etc/issue.net. >Instead of putting LM logo, kernel version, LM version, uptime etc... >Should we put a warning if a cracker try to log in our box? > This is an intriguing idea. In fact we used to use /etc/issue on Unix years ago for just that purpose. The problems are 1) alas, that was not the design intent of /etc/issue, we just used it that way on an emergency basis. The current use serves the original intent. 2) The need has been largely supplanted by very good and effective firewall and security monitoring technology. And its all available as free software. Use it! 3) The nature of cracking itself has changed to some degree. Today's crackers, operating internationally and largely through compromised boxes operate without a lot of fear. So your challenge would either be a bluff which could actually invite the hacker in to see what you are hiding, or it would be a tipoff to the hacker that he needs to avoid the booby traps. Desktop machines should be protected by a fulltime stealthing firewall. Servers should be protected by real time administration and heavy duty security monitoring. The fact of the matter is that if a hacker gets that far (/etc/issue) on your machine, you are probably already dead meat unless you are closely monitoring your logs. And if you are closely monitoring your logs, a warning message is unnecessary. But you are the admin of your own box and Linux is not Windows. You are free to change /etc/issue and /etc/issue.net to anything you think appropriate and Mandrake is not going to try to sue you for it. As one who has dealt with Unix security issues in a corportate setting for many years, those are my opinions. > > >---------begin of /etc/motd in FreeBSD---------------- > >FreeBSD ?.?.? (UNKNOWN) > >Welcome to FreeBSD! > >Before seeking technical support, please use the following resources: > >o Security advisories and updated errata information for all releases are > at http://www.FreeBSD.org/releases/ - always consult the ERRATA section > for your release first as it's updated frequently. > >o The Handbook and FAQ documents are at http://www.FreeBSD.org/ and, > along with the mailing lists, can be searched by going to > http://www.FreeBSD.org/search/ If the doc distribution has > been installed, they're also available formatted in /usr/share/doc. > >If you still have a question or problem, please take the output of >`uname -a', along with any relevant error messages, and email it >as a question to the [EMAIL PROTECTED] mailing list. If you are >unfamiliar with FreeBSD's directory layout, please refer to the hier(7) >man page. If you are not familiar with man pages, type `man man'. >You may also use `/stand/sysinstall' to re-enter the installation and >configuration utility. Edit /etc/motd to change this login announcement. > >------- End of /etc/motd in FreeBsd --------------- > > >===== >Takeshi's small space >http://site.TechViet.com/Vu.Hung/ >Join KDE-i18n-Vi? >http://groups.yahoo.com/group/KDE-i18n-VN > >__________________________________________________ >Do You Yahoo!? >Send your FREE holiday greetings online! >http://greetings.yahoo.com > >
