Преглед на файлове

Update README with ufw instead of ferm

Luke Cyca преди 10 години
родител
ревизия
111217184e
променени са 1 файла, в които са добавени 2 реда и са изтрити 2 реда
  1. 2
    2
      README.textile

+ 2
- 2
README.textile Целия файл

@@ -38,7 +38,7 @@ What do you get if you point this thing at a VPS? All kinds of good stuff!
38 38
 * An IRC bouncer via "ZNC":http://wiki.znc.in/ZNC.
39 39
 * "Monit":http://mmonit.com/monit/ to keep everything running smoothly (and alert you when it's not).
40 40
 * Web hosting (ex: for your blog) via "Apache":https://www.apache.org/.
41
-* Firewall management via "ferm":http://ferm.foo-projects.org/.
41
+* Firewall management via "Uncomplicated Firewall (ufw)":https://wiki.ubuntu.com/UncomplicatedFirewall.
42 42
 * Intrusion prevention via "fail2ban":http://www.fail2ban.org/ and rootkit detection via "rkhunter":http://rkhunter.sourceforge.net.
43 43
 * SSH configuration preventing root login and insecure password authentication
44 44
 * Nightly backups to "Tarsnap":https://www.tarsnap.com/.
@@ -120,7 +120,7 @@ bc. ansible-playbook -i ./hosts site.yml
120 120
 
121 121
 To run just one or more piece, use tags. I try to tag all my includes for easy isolated development. For example, to focus in on your firewall setup:
122 122
 
123
-bc. ansible-playbook -i ./hosts --tags=ferm site.yml
123
+bc. ansible-playbook -i ./hosts --tags=ufw site.yml
124 124
 
125 125
 You might find that it fails at one point or another. This is probably because something needs to be done manually, usually because there's no good way of automating it. Fortunately, all the tasks are clearly named so you should be able to find out where it stopped. I've tried to add comments where manual intervention is necessary.
126 126
 

Loading…
Отказ
Запис