Re: [SoaS] Limited Internet Access for SOAS
On Mon, Jun 21, 2010 at 10:04:57AM +0200, Raffael Reichelt wrote: > Thank you for this information James. Anyway I do not want to bother > you with this topic in this list - what would be an adequate place to > discuss? I agree, the topic of Squid configuration is not sufficiently SoaS. There are Squid mailing lists. I'm not on any of them. The best other place I know of is the OLPC server-devel@ mailing list, where the OLPC school server design and development is discussed. Perhaps you should be looking for a way to integrate SoaS clients into a school server configuration so that they can benefit from proxy and filtering services. I don't know enough about the school server design to be able to advise you on that, but the server-devel@ team should be able to answer. Also, the SoaS mailing list may be able to answer "can SoaS clients register with an OLPC XS school server?". -- James Cameron http://quozl.linux.org.au/ ___ SoaS mailing list [email protected] http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Limited Internet Access for SOAS
2010/6/21 James Cameron : > On Sat, Jun 19, 2010 at 08:15:18AM +0100, Peter Robinson wrote: >> Not in the SoaS image. SoaS is designed to run on netbooks, squid is a >> daemon that should run on a server, it also creates a massive >> directory structure that will cause issues on liveUSB keys and not >> really run at all on a live cd. > > This argument is invalid, because Squid can easily be configured to > proxy only, without caching anything, and without requiring a massive > directory structure. > > http://wiki.squid-cache.org/SquidFaq/ConfiguringSquid#Can_I_make_Squid_proxy_only.2C_without_caching_anything.3F > > It does, however, cost about 5Mb of memory, which can easily become a > threat to smooth operation on particularly small systems. > > -- > James Cameron > http://quozl.linux.org.au/ > ___ > SoaS mailing list > [email protected] > http://lists.sugarlabs.org/listinfo/soas > Thank you for this information James. Anyway I do not want to bother you with this topic in this list - what would be an adequate place to discuss? Raffael ___ SoaS mailing list [email protected] http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Limited Internet Access for SOAS
On Sat, Jun 19, 2010 at 08:15:18AM +0100, Peter Robinson wrote: > Not in the SoaS image. SoaS is designed to run on netbooks, squid is a > daemon that should run on a server, it also creates a massive > directory structure that will cause issues on liveUSB keys and not > really run at all on a live cd. This argument is invalid, because Squid can easily be configured to proxy only, without caching anything, and without requiring a massive directory structure. http://wiki.squid-cache.org/SquidFaq/ConfiguringSquid#Can_I_make_Squid_proxy_only.2C_without_caching_anything.3F It does, however, cost about 5Mb of memory, which can easily become a threat to smooth operation on particularly small systems. -- James Cameron http://quozl.linux.org.au/ ___ SoaS mailing list [email protected] http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Limited Internet Access for SOAS
* +1 to Sascha's very astute comments below. Caryl > From: [email protected] > To: [email protected] > Date: Sat, 19 Jun 2010 09:53:22 + > Subject: Re: [SoaS] Limited Internet Access for SOAS > > Excerpts from Raffael Reichelt's message of Sat Jun 19 06:47:02 + 2010: > > > I had a talk with sebastian at linuxtag about including local squid > > with a whitelist in soas. > Censoring internet access with Sugar (or SoaS in this case) comes up > regularly. If you really must filter (*), it's a task for the device > providing internet access, not the client device (the computer running > Sugar). One of the reasons is that it's way too easy ("kinderleicht" > in german) to circumvent local filtering if the user has full access (as > Sugar users do by design). > > > (*) Whether filtering is a good idea / achieves what it's supposed to is > a separate topic and doesn't belong on the SoaS list. Let me just > mention that filters are very "dumb" tools with a lot of false > positives AND negatives (e.g. some german blacklist even blocked > Wikipedia). Having a filter can make the parents believe their kids > are "safe" and stop supervising them. It's quite similar to anti- > virus software and personal firewalls: they make you believe you are > safe, while in fact you are not. > > Sascha > > -- > http://sascha.silbe.org/ > http://www.infra-silbe.de/ ___ SoaS mailing list [email protected] http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Limited Internet Access for SOAS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/19/2010 03:30 AM, Raffael Reichelt wrote: > I understand ... is there some other way to provide soas with > whitelist based internet access? Yes, at the network level. See for example DansGuardian[1] and OpenDNS's blocking features[2]. [1]: http://dansguardian.org/ [2]: http://www.opendns.com/solutions/k12/filtering/ - -- Luke Faraone http://luke.faraone.cc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwc2p4ACgkQtrC51grHAgZvwwCgkmY92yfHQe5r1PoOoqI1nkpb qA0AnA/mFXo9ZGP11n7zXseIb+NjLXpP =QNzc -END PGP SIGNATURE- ___ SoaS mailing list [email protected] http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Limited Internet Access for SOAS
Excerpts from Raffael Reichelt's message of Sat Jun 19 06:47:02 + 2010:
> I had a talk with sebastian at linuxtag about including local squid
> with a whitelist in soas.
Censoring internet access with Sugar (or SoaS in this case) comes up
regularly. If you really must filter (*), it's a task for the device
providing internet access, not the client device (the computer running
Sugar). One of the reasons is that it's way too easy ("kinderleicht"
in german) to circumvent local filtering if the user has full access (as
Sugar users do by design).
(*) Whether filtering is a good idea / achieves what it's supposed to is
a separate topic and doesn't belong on the SoaS list. Let me just
mention that filters are very "dumb" tools with a lot of false
positives AND negatives (e.g. some german blacklist even blocked
Wikipedia). Having a filter can make the parents believe their kids
are "safe" and stop supervising them. It's quite similar to anti-
virus software and personal firewalls: they make you believe you are
safe, while in fact you are not.
Sascha
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
signature.asc
Description: PGP signature
___
SoaS mailing list
[email protected]
http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Limited Internet Access for SOAS
I understand ... is there some other way to provide soas with whitelist based internet access? Raffael 2010/6/19 Peter Robinson : > On Sat, Jun 19, 2010 at 7:47 AM, Raffael Reichelt > wrote: >> I had a talk with sebastian at linuxtag about including local squid >> with a whitelist in soas. I do not know how others thinking about this >> but I am generally concerned about giving unlimited internet access to >> the children. This might be different in a schoolserver/XO >> environment, but if you want to have a widely spread soas deployment >> it should be available at least as an option. >> >> Unfortunately there are no constantly maintained whitelists available >> - I talked to the people of "Kinder im Netz" - a german organisation >> maintaining a whitelist - but they have legal/licence concerns opening >> the whitelist to other software beside their own (propietary) windows >> software. > > Not in the SoaS image. SoaS is designed to run on netbooks, squid is a > daemon that should run on a server, it also creates a massive > directory structure that will cause issues on liveUSB keys and not > really run at all on a live cd. If the parents/teachers that are > giving SoaS to their children want to restrict the access to the net > they can do it via their internet connection or turn on the child safe > internet option that just about all ISPs provide. > > Peter > ___ > SoaS mailing list > [email protected] > http://lists.sugarlabs.org/listinfo/soas > ___ SoaS mailing list [email protected] http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Limited Internet Access for SOAS
On Sat, Jun 19, 2010 at 7:47 AM, Raffael Reichelt wrote: > I had a talk with sebastian at linuxtag about including local squid > with a whitelist in soas. I do not know how others thinking about this > but I am generally concerned about giving unlimited internet access to > the children. This might be different in a schoolserver/XO > environment, but if you want to have a widely spread soas deployment > it should be available at least as an option. > > Unfortunately there are no constantly maintained whitelists available > - I talked to the people of "Kinder im Netz" - a german organisation > maintaining a whitelist - but they have legal/licence concerns opening > the whitelist to other software beside their own (propietary) windows > software. Not in the SoaS image. SoaS is designed to run on netbooks, squid is a daemon that should run on a server, it also creates a massive directory structure that will cause issues on liveUSB keys and not really run at all on a live cd. If the parents/teachers that are giving SoaS to their children want to restrict the access to the net they can do it via their internet connection or turn on the child safe internet option that just about all ISPs provide. Peter ___ SoaS mailing list [email protected] http://lists.sugarlabs.org/listinfo/soas
[SoaS] Limited Internet Access for SOAS
I had a talk with sebastian at linuxtag about including local squid with a whitelist in soas. I do not know how others thinking about this but I am generally concerned about giving unlimited internet access to the children. This might be different in a schoolserver/XO environment, but if you want to have a widely spread soas deployment it should be available at least as an option. Unfortunately there are no constantly maintained whitelists available - I talked to the people of "Kinder im Netz" - a german organisation maintaining a whitelist - but they have legal/licence concerns opening the whitelist to other software beside their own (propietary) windows software. For a fist start I guess it would be possible to a) provide squid in the image b) provide a minimum example whitelist (e.g. surgarlabs.org, google.com) to serve the links from the initial brwose-activity startpage c) provide a tutorial how to enable squid and to modify the whitelist ___ SoaS mailing list [email protected] http://lists.sugarlabs.org/listinfo/soas
