mirror of
https://github.com/opnsense/src.git
synced 2026-06-09 08:43:19 -04:00
Correct minor typos.
This commit is contained in:
parent
3004d1ed4d
commit
a30de06b88
1 changed files with 2 additions and 2 deletions
|
|
@ -218,7 +218,7 @@ servers.
|
|||
.Pp
|
||||
Using something like kerberos also gives you the ability to disable or
|
||||
change the password for a staff account in one place and have it immediately
|
||||
effect all the machine the staff member may have an account on. If a staff
|
||||
effect all the machines the staff member may have an account on. If a staff
|
||||
member's account gets compromised, the ability to instantly change his
|
||||
password on all machines should not be underrated. With discrete passwords,
|
||||
changing a password on N machines can be a mess. You can also impose
|
||||
|
|
@ -441,7 +441,7 @@ options
|
|||
.Xr mount 8 )
|
||||
are what you want to look into. I would scan them anyway at least once a
|
||||
week, since the object of this layer is to detect a break-in whether or
|
||||
not the breakin is effective.
|
||||
not the break-in is effective.
|
||||
.Pp
|
||||
Process accounting
|
||||
(see
|
||||
|
|
|
|||
Loading…
Reference in a new issue