<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Cool!<br>
<br>
I'd like to suggest several changes to the implementation strategy
for Cute:<br>
<br>
* Cute should be an "application" and it must not be for any reason
a virtual machine that's a nerdy/geeky things.<br>
An application has to be distributed trough Mac App Stores,
Ubuntu App Stores, Windows App Stores.<br>
<br>
* Cute should not have multiple process running (only a single
process, no LAMP that's difficult to be maintained)<br>
<br>
* Cute's Wordpress must use SQLite backend (to keep it
selfcontained)<br>
<br>
* Wordpress should run over a secure Python sandbox<br>
Assuming the use of APAF, wordpress must be run using php-cgi,
with a sandboxed profie from Twisted<br>
<a class="moz-txt-link-freetext" href="http://stackoverflow.com/questions/14541813/python-twisted-render-php">http://stackoverflow.com/questions/14541813/python-twisted-render-php</a><br>
<br>
* Use Tor2web for "Edge Cache Nodes", without using other piece of
software<br>
It just need to implement caching with
<a class="moz-txt-link-freetext" href="https://github.com/globaleaks/Tor2web-3.0/issues/29">https://github.com/globaleaks/Tor2web-3.0/issues/29</a><br>
<br>
Fabio<br>
<br>
Il 10/10/13 2:02 PM, Michele Orrù ha scritto:<br>
<span style="white-space: pre;">> Dear Team,<br>
><br>
> For completeness' sake I am attaching to this email the
report I wrote last<br>
> week in order to summarize what the project APAF is about,
and what there is in<br>
> common between it and the Otter/Cute proposal.<br>
> Eventually, feel free to add it to the trac page.<br>
><br>
> After reading ["Cute" design and challenges], though, I think
the report lacks<br>
> an exhaustive description of APAF's threat model.</span><br>
<br>
<br>
</body>
</html>