(evil) hackers -> crackers

This commit is contained in:
Martin Cracauer 1998-04-08 11:52:41 +00:00
parent c512a02725
commit ea2aa372fb
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=2653
2 changed files with 9 additions and 9 deletions

View file

@ -1,4 +1,4 @@
<!-- $Id: firewalls.sgml,v 1.19 1997-11-22 14:03:24 alex Exp $ -->
<!-- $Id: firewalls.sgml,v 1.20 1998-04-08 11:52:40 cracauer Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Firewalls<label id="firewalls"></heading>
@ -16,10 +16,10 @@ your companies internal network and the ``Big Bad Internet'' will
solve all your security problems. It may help, but a poorly setup
firewall system is more of a security risk than not having one at all.
A firewall can only add another layer of security to your systems, but
they will not be able to stop a really determined hacker from
they will not be able to stop a really determined cracker from
penetrating your internal network. If you let internal security lapse
because you believe your firewall to be impenetrable, you have just
made the hackers job that bit easier.</quote>
made the crackers job that bit easier.</quote>
<sect1><heading>What is a firewall?</heading>
@ -389,19 +389,19 @@ only affects a specific chain entry.
<sect1><heading>Example commands for ipfw</heading>
<p>This command will deny all packets from the host
<bf>evil.hacker.org</bf> to the telnet port of the host
<bf>evil.crackers.org</bf> to the telnet port of the host
<bf>nice.people.org</bf> by being forwarded by the router:
<tscreen><verb>
ipfw add deny tcp from evil.hacker.org to nice.people.org 23
ipfw add deny tcp from evil.crackers.org to nice.people.org 23
</verb></tscreen>
<p>The next example denies and logs any TCP traffic from the entire
<bf>hacker.org</bf> network (a class C) to the <bf>nice.people.org</bf>
<bf>crackers.org</bf> network (a class C) to the <bf>nice.people.org</bf>
machine (any port).
<tscreen><verb>
ipfw add deny log tcp from evil.hacker.org/24 to nice.people.org
ipfw add deny log tcp from evil.crackers.org/24 to nice.people.org
</verb></tscreen>
If you do not want people sending X sessions to your internal network

View file

@ -1,4 +1,4 @@
<!-- $Id: userppp.sgml,v 1.28 1998-02-09 14:39:31 jkh Exp $ -->
<!-- $Id: userppp.sgml,v 1.29 1998-04-08 11:52:41 cracauer Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect>Setting up User PPP<label id="userppp">
@ -700,7 +700,7 @@
PAP is less secure than CHAP, but security is not normally an issue
here as passwords, although being sent as plain text with PAP, are being
transmitted down a serial line only. There's not much room for hackers
transmitted down a serial line only. There's not much room for crackers
to "eavesdrop".
Referring back to the <ref id="userppp:staticIP"