pavement

Talk:Securing servers

From FreeBSDwiki
(Difference between revisions)
Jump to: navigation, search
(GHD Straightener Australia: new section)
m (Reverted edits by 98.126.95.50 (Talk) to last revision by Dave)
 
Line 11: Line 11:
  
 
things needed here:(cover common gotchas and SNAFUs concerning local security; ie preventing valid shell users from obtaining privileges they aren't supposed to have or doing damage they shouldn't be able to do. sudo is clearly a must with this one, as is some discussion of running daemons under special user accounts, and the dangers of overusing "nobody" to run daemons. a quick rundown of system files that permissions should be double-checked on, like /etc/passwd, /etc/master.passwd, /etc/group, and the databases associated with them should also be covered.)
 
things needed here:(cover common gotchas and SNAFUs concerning local security; ie preventing valid shell users from obtaining privileges they aren't supposed to have or doing damage they shouldn't be able to do. sudo is clearly a must with this one, as is some discussion of running daemons under special user accounts, and the dangers of overusing "nobody" to run daemons. a quick rundown of system files that permissions should be double-checked on, like /etc/passwd, /etc/master.passwd, /etc/group, and the databases associated with them should also be covered.)
 
== GHD Straightener Australia ==
 
 
Many thanks for this pleasant and priceless internet site. Let me talk about it with friends and neighbors and even I will come back once again to take a look at increasing intriguing data.
 

Latest revision as of 18:23, 1 August 2011

this needs more on:

keeping your machine updated -- general, OS and programs (firewalls, ssh security gotchas, choosing secure daemons, staying up to date with patches, etc.) keeping your machine updated -- security patches


-d.

[edit] Security in a local user context section needs:

things needed here:(cover common gotchas and SNAFUs concerning local security; ie preventing valid shell users from obtaining privileges they aren't supposed to have or doing damage they shouldn't be able to do. sudo is clearly a must with this one, as is some discussion of running daemons under special user accounts, and the dangers of overusing "nobody" to run daemons. a quick rundown of system files that permissions should be double-checked on, like /etc/passwd, /etc/master.passwd, /etc/group, and the databases associated with them should also be covered.)

Personal tools