Je pense que c'est celui là
Changing your password every 3 months sounds good in theory -- if you have only one account in world. But what if you live in the real world? In that case, you probably have 50-100 accounts, each with its own password and user name. You can make this plenitude of accounts less onerous by using the same name and password for multiple accounts. But if your IT department insists that you change passwords every 3 months, how do you keep track of them? Most people write them down -- in a file on the computer or PDA, on a white board, or on post-it notes displayed prominently on the monitor for any and all too see.
With so many passwords to remember, this is a perfectly rationale way of coping with the changing-password demand. Of course, it must also be admitted that it has the opposite effect of the intended purpose. Rather than improving security, forcing users to change passwords makes security weaker, since everyone has to find some coping mechanism for dealing with the short expiration. Under the flag of strengthening security, this practice actually weakens it.
Source:
http://dontgogentle.blogspot.com/2007/12/magazine-passwords-(...)
[ Répondre ]
Re: Merci
Merci de penser au sysadmin ;)
http://www.sysadminday.com
[ Répondre ]
Re: Suggestion: Un article du Net
Merci Steve. C'est presque la config que j'ai pour ucarp et ça fonctionne. La question que je me demande est-ce que la différence des MAC influencera sur les routeurs sachant que c'est l'ISP qui peut faire un clean du cache arp.
[ Répondre ]
Cette page a été générée par Templeet en 0.0599s (dont 0.0067 de SQL).
Cette page est peut-être conforme xhtml 1.0.
Information sur le site.
apache_syslog
On utilise apache_syslog http://www.oreilly.com/pub/a/sysadmin/2006/10/12/httpd-syslo(...)
Qui envoi les logs dans syslog-ng et le syslog-ng de la machine locale envoi les logs sur un serveur de log distant puis avec un filtre syslog-ng on peut avoir un seul fichier de logs ayant tout les access.log des frontend
[ Répondre ]