From: "Erik K." <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Wiki tutorial for P2P, Web lock and Child safty lock
Date: Tue, 25 Jun 2013 15:34:24 +0200 [thread overview]
Message-ID: <7E12F665-43AA-4288-8D85-5B1BCFC15619@ipfire.org> (raw)
In-Reply-To: <1371449349.2249.1.camel@fedora18x64-lan-e82.lan.e82>
[-- Attachment #1: Type: text/plain, Size: 2244 bytes --]
Hi all,
i think also it is a very good idea. Some documentations regarding to this theme should also be cleaned up and some others needs to be complete revised. It can be may a good idea to work on this sections too, so a clearer overview of the important themes can better be linked to another, also more background informations are available. So for this topic i think the following wikis are important.
- The new firewall wiki --> http://wiki.ipfire.org/nonpublic/de/configuration/firewall/start
It is still in the beginning and the informations are collected from the official wiki "Firewall 2013", but i think they can extend with more informations.
- The URL-Filter needs really a new revision --> http://wiki.ipfire.org/de/configuration/network/url-filter .
The screenshoots can be made again also with a higher resolution, also the wiki lags in some sections. It is a possibility to find a structure like in the proxy wiki, so the informations for every configuration section can be integrated and the informations for each side is not to long.
Greetings,
Erik
Am 17.06.2013 um 08:09 schrieb Daniel Weismüller:
> I really like this idea.
>
>
> Am Sonntag, den 16.06.2013, 21:09 +0200 schrieb Thomas Berthel:
>> He,
>>
>> i thought about doing that wiki topic
>> "Web-Security and control over the childs".
>>
>> I have considered the following points in one Wiki-Tobic with the name
>> "child safety lock (en) / Kindersicherung (de)"
>>
>> * P2P Block with examples
>> * Time control for devices
>> * Firewallsettings für child security
>> * Proxy and HTTP-URL Filtersettings with examples
>>
>> I think that it is very interesting for a lot of parents to find a topic
>> with important security settings for access the children.
>>
>> What do you think, or do you mean that would be unnecessary?
>>
>> BG, Thomas
>> _______________________________________________
>> Documentation mailing list
>> Documentation(a)lists.ipfire.org
>> http://lists.ipfire.org/mailman/listinfo/documentation
>
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
prev parent reply other threads:[~2013-06-25 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 19:09 Thomas Berthel
2013-06-17 6:09 ` Daniel Weismüller
2013-06-25 13:34 ` Erik K. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7E12F665-43AA-4288-8D85-5B1BCFC15619@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=documentation@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox