Quoting Nick Daly (2014-04-16 01:08:20)
Jonas Smedegaard d...@jones.dk writes:
When Plinth directly edits configuration files, it is an
administrators' tool.
Solution is to have Plinth only ever communicate with debconf!
...and convince various package maintainers (e.g. by offering
[Jonas Smedegaard]
Good point!
James created a wiki page tracking transition to debconf, and I have now
referenced from that page a tutorial on packaging with debconf:
https://wiki.debian.org/FreedomBox/Build/DebconfConfig
I noticed you added this:
NB! Debconf is preferred over
Quoting Petter Reinholdtsen (2014-04-16 10:54:56)
can you add some details to the page on how the freedombox project can
use debconf to change the setup we apply to packages after
installation? For example, if the tor package started using debconf
and we used debconf to configure tor
One thing mentioned by Jacob Appelbaum in his talk the other day, was
the advantages of upgrading packages via Tor, to make it harder to
target a given machine with fake packages.
I suggest we implement this in the Freedombox, by asking Provixy to
send all requests via Tor, and ask APT to fetch
[Tim Retout]
I think this idea is worth trying - even if secure apt prevents
someone putting fake packages onto your machine, this will stop
people seeing which software they need to find zero-day
vulnerabilities in. :)
Yeah. :)
What's the best apt mirror to use with tor? Maybe
On Tuesday 15 April 2014 03:35 AM, Jonas Smedegaard wrote:
[...]
When Plinth directly edits configuration files, it is an administrators'
tool.
Solution is to have Plinth only ever communicate with debconf!
I can see that many uses cases for configuration can be done in this
manner.
On 04/16/2014 02:48 PM, Petter Reinholdtsen wrote:
Happy to report that our project was mentioned on Slashdot today,
URL:
http://linux.slashdot.org/story/14/04/16/1355220/all-packages-needed-for-freedombox-now-in-debian
.
As can be seen from the comments, the documentation need some work.
Quoting Sunil Mohan (2014-04-16 20:12:33)
On Tuesday 15 April 2014 03:35 AM, Jonas Smedegaard wrote:
[...]
When Plinth directly edits configuration files, it is an
administrators' tool.
Solution is to have Plinth only ever communicate with debconf!
I can see that many uses cases for
Regarding spreading the word, I just recently did FreedomBox sessions at
the following two events this month:
http://ausserreichweite.org/ - 5 April Berlin
http://barcamp-graz.at/ - 11-13 April Graz
I'm also going to the following events in May, and will demo FreedomBox:
On 04/16/2014 03:53 PM, Petter Reinholdtsen wrote:
[Ian Sullivan]
And I would very much like to get some help spreading the word about
the project. :)
I'd love to help get the word out about the 0.2 release in particular, I
just don't know all the relevant things that 0.2 actually does. Any
Hello.
(Apologies for starting a new thread; I just joined the mailing list and
don't have past messages available to make a proper reply.)
I'm one of the commenters on Slashdot who were puzzled by the whole
FreedomBox thing. I think I can (sort of) guess what the intention is
and how it's
Hi Stefan,
Have you seen Arkos?
https://arkos.io/
It fulfills the purpose stated in your last paragraph, and it is relevant to
the Freedombox list because it has clear documentation that hits all of your
bullet points.
-Jonathan
On Wednesday, April 16, 2014 6:08 PM, Stefan Weiss
On Wed, Apr 16, 2014 at 8:04 AM, Jonas Smedegaard d...@jones.dk wrote:
Quoting Petter Reinholdtsen (2014-04-16 10:54:56)
can you add some details to the page on how the freedombox project can
use debconf to change the setup we apply to packages after
installation? For example, if the tor
Quoting James Valleroy (2014-04-17 02:39:13)
On Wed, Apr 16, 2014 at 8:04 AM, Jonas Smedegaard d...@jones.dk wrote:
Second is specific to Plinth, and should be documented in manpages
of debconf. For an equivalent implemented in shell it would involve
debconf-set-selections and debconf
14 matches
Mail list logo
