[OLPC Security] P_READ_LOGS
Benjamin M. Schwartz
bmschwar at fas.harvard.edu
Sun Aug 10 22:58:57 EDT 2008
-----BEGIN PGP SIGNED MESSAGE-----
Jameson "Chema" Quinn wrote:
| For when we actually have bitfrost permissions in the interface, I propose
| another simple bitfrost permission: P_READ_LOGS.
I agree that reading logs is a valuable capability for Sugar to provide.
I don't see why any new Bitfrost permissions are required to enable it.
The easiest way to present logs, especially failure logs, is to make them
available through the standard Journal/Datastore interface. For example,
we have some agreement that when an Activity fails to launch, the failure
should appear as such in the Journal time-view, connected to an object
representing the log file for that failure. This log object has a "text"
type, and so can naturally be opened by any Activity that accepts this
type. No additional permissions are required. The user is responsible
for determining when to provide both sensitive data and P_NETWORK to the
Perhaps it would be helpful if you could give an example of a case in
which a P_READ_LOGS permission is the best solution, and better than
simply exposing the logs through the Journal.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Security