[OpenSource live USB OS] BitSafe, a safety deposit box for your bitcoins.

[Red Emerald]

Any interest in this with Armory installed?  Armory is heavier weight right now than I think BitSafe was originally designed, but it looks like an awesome client.

[simonk83]

Bump...   Be nice to have a new version,  if only for the latest bitcoin client

[rb1205]

I'll release a version with the last official client within tomorrow.

[rb1205]

New beta version released. The only real change is the updated cliento to V0.5.2. More feature will come as soon as I figure out how to fix this damned transparent TOR routing.

[ovidiusoft]

I can send you a pull request to also include Electrum, would that be ok? (see more here: https://bitcointalk.org/index.php?topic=54376.0 )

[rb1205]

I noticed your pull request on GitHub. I think that, given the different requirements, electrum needs a different tailored build.
On top of that, there's no point IMHO to have both electrum and the bitcoin client on the same image.

[RoloTonyBrownTown]

Is anyone able to suggest a fast USB drive suitable for this?   

[rb1205]

Is anyone able to suggest a fast USB drive suitable for this?   

Here's a brief list:

Lexar JumpDrive Lightning II
Transcend JetFlash
OCZ Rally2 Turbo
Corsair Voyager GT (rugged!)
Silicon Power LuxMini 920
Sandisk Cruzer Contour

You can check the speeds for almost any usb drive at http://usbflashspeed.com/

[RoloTonyBrownTown]

Great, thanks!

[Red Emerald]

I've started using a Tails Live CD and an encrypted flash drive with scripts similar to what you wrote for BitSafe.  I like the idea of BitSafe, but theres security vulnerabilities being patched all the time.  I feel more comfortable using a live cd built specifically for security and anonymity.

[rb1205]

I like the idea of BitSafe, but theres security vulnerabilities being patched all the time.  I feel more comfortable using a live cd built specifically for security and anonymity.

Being for 99.9% a Debain stable distribution, I have very little to say about security updates and patches. I deliberately choose stable over testing for that specific reason.
That said, the main purpose of this software is to give the most secure environment to keep your bitcoin, anonymity is more about using them in a safe way, so I think it will always be secondary. If your priorities are different than you probably need something else 

[Red Emerald]

I like the idea of BitSafe, but theres security vulnerabilities being patched all the time.  I feel more comfortable using a live cd built specifically for security and anonymity.

Being for 99.9% a Debain stable distribution, I have very little to say about security updates and patches. I deliberately choose stable over testing for that specific reason.
That said, the main purpose of this software is to give the most secure environment to keep your bitcoin, anonymity is more about using them in a safe way, so I think it will always be secondary. If your priorities are different than you probably need something else 

I'm talking about these: http://www.debian.org/security/2012/

They usually have patches for both oldstable, stable, and unstable.  The vulnerability in ffmpeg are probably less of a worry than the oones in openssl, iceweasel, and ecryptfs-utils.

[rb1205]

Version 0.6B released. Updated bitcoin client to 0.6, fixed some bugs and disabled random data filling for the storage partition on creation.

[rb1205]

Version 0.6.1B released.

• Added a script to download and install the latest (daily) blockchain image from this archive
• Storage partition size increased to about 3.5 GB.
• Random data filling of the storage partition has been disabled by default.
• Changed bootloader splash image

[chunglam]

Version 0.6.1B released.

• Added a script to download and install the latest (daily) blockchain image from this archive
• Storage partition size increased to about 3.5 GB.
• Random data filling of the storage partition has been disabled by default.
• Changed bootloader splash image

Unable to download from Dropbox(error 404).

[rb1205]

Unable to download from Dropbox(error 404).

Temporary problem, fixed now.

[chunglam]

Unable to download from Dropbox(error 404).

Temporary problem, fixed now.

Thanks, downloaded and tried it on my laptop. Since my laptop main OS is Windows, the clock is local time. How to config this system to aware my clock is not UTC? And persistently? Because the Bitcoin client will constantly try to download block chain even after last block has been downloaded(my time zone is UTC+8).

[rb1205]

That's odd: BitSafe's default tz should be UTC, and that shouldn't introduce any offset to the time reported by your hardware clock, which should be set to local time already by Windows.
Can you please launch the terminal and paste here the output of the "date" command, timezone included, along with the correct local time?

[chunglam]

That's odd: BitSafe's default tz should be UTC, and that shouldn't introduce any offset to the time reported by your hardware clock, which should be set to local time already by Windows.
Can you please launch the terminal and paste here the output of the "date" command, timezone included, along with the correct local time?

My understanding is a bit different: Windows sets the hardware clock to local time(in my case, UTC+8) and BitSafe expects UTC time, so the time is offset +8 hours.
After a little bit google, I need to edit /etc/default/rcS and change the UTC=yes to UTC=no and add TZ='Asia/Hong Kong' to ~/.profile. But I don't know how to make these changes persistent, do I have to edit filesystem.squashfs to make it persistent?

[rb1205]

The point is that BitSafe doesn't know which timezone you're on, so it (shoulds) default to UTC and not UTC+8. As you stated correctly, linux expects the hwclock to be in UTC, so UTC=UTC-> it just takes its time as it is, hence giving the correct local time (if the main OS is Windows). In fact, my Windows PC shows the correct time when runs bitsafe even if i'm on CET/CEST.
Maybe your hardware clock is able to tell the OS on which timezone it's set, or maybe Windows is doing some weirdness. We'll know better with the output from date  

Which localization are you choosing at boot?