On Wed, Jul 26, 2006 at 11:29:46PM +0200, David 'Bombe' Roden wrote: > On Wednesday 26 July 2006 23:17 Matthew Toseland wrote: > > > Can this be combined with SecurityManager settings to deny the plugin > > access to the local disk etc unless explicitly granted? If so then it > > seems reasonable. > > I think that is possible. I will check out how easy security managers > and access control mechanisms are to use. > > > Note that a plugin may be able to gather information about the user > > and return it to its author in any case; this only requires the > > ability to request and insert keys and the ability to read the clock. > > Sure. Access to any privilege should not be given lightly. The user > should be informed about what read and write access to freenet might > mean.
Long term the solution is separate client-caches for fproxy and individual plugins. > > David > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20060726/5bc0125e/attachment.pgp>
