Completed the first draft of my slides+speaker-notes for my upcoming
"Defeating Trojans" talk at the OHM2013. BitCoin is one of the main
examples I use in this talk to emphasize the need for programs like
BitCoin to have
their own private storage apart from $HOME.
To make sure I don't misrepresent
open to a pull-request that would
incorporate a copy of this library into Bitcoin, making BitCoin use
private storage when available, implemented using the above API.
Please let me know what you think.
Rob
On Fri, August 26, 2011 08:48, Rob Meijer wrote:
> A few years ago I wrote a least au
On Mon, September 5, 2011 13:55, Rob Meijer wrote:
> On Sat, September 3, 2011 00:05, Nils Schneider wrote:
>> MinorFs sounds like an interesting concept and but wallet encryption
>> (already being tested and close to release) is a simpler solution for
>> end-users.
>
> I
On Sat, September 3, 2011 09:04, John Smith wrote:
> On Fri, Sep 2, 2011 at 8:32 PM, Rob Meijer wrote:
>
>> Given that there was not a single response to my post, I gather there is
>> no to little interest in an updated MinorFs that could be used by
>> bitcoin
>> on
that, what is considered the currently proper
way to keep backups for bitcoin?
> On 02.09.2011 22:32, Rob Meijer wrote:
>> Given that there was not a single response to my post, I gather there is
>> no to little interest in an updated MinorFs that could be used by
>> bitcoin
>&
nyone would like to comment on them to make a future match
with Bitcoin more likely, I'm open to all sugestions:
http://minorfs.polacanthus.net/wiki/Concepts_for_MinorFs2
On Fri, August 26, 2011 09:48, Rob Meijer wrote:
> A few years ago I wrote a least authority based set of filesystems na
A few years ago I wrote a least authority based set of filesystems named
MinorFs that worked closely together with AppArmor (suse/ubuntu) to give '
pseudo persistent processes' their own private but decomposable and
delegatable piece of filesystem storage:
http://www.linuxjournal.com/magazine/mino
7 matches
Mail list logo
