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

ricklandman

newbie

Activity: 25

Merit: 0

It is a pity that the maintainer of bitsafe is not monitoring it's own product anymore. My former posting is still relevant. Meanwhile I tried running bitcoin-qt without using the quick download method. After two days of downloading the blockchain the program crashed and I cannot restart bitcoin-qt. Dmesg barks

Quote

terminate called after throwing an instance of 'DbRunRecoveryException'
what(): DbEnv::txn_checkpoint: DB_RUNRECOVERY: Fatal error, run database recovery
/usr/bin/wrapped_bin/bitcoin-qt.wrp: line 44: 28866 Aborted $WRAPPER_ORIGINALBIN -datadir=$BITCOIN_HOME -nolisten $*

At the moment of the crash db was 842MB.

I also don't know how to upgrade bitcoin-qt in bitsafe. There is no repository available in /etc/apt/sources.list. Anybody knows what repository I need for bitsafe ?

ricklandman

newbie

Activity: 25

Merit: 0

I donwloaded bitsafe, and ran it from a usb stick and connected it via ethernet. First thing bitsafe is asking after startup is if I want to download the blockchain, which I accept. I did this a few times, but after the download is completely finished (I see huge dat-files in /storage/bitcoins) I get consistently the same message

Code:

signature verification failed! This means that your downloaded file is invalid:
the signing key changed or your internet connection is being filtered or altered by
someone or something. Please try again in a couple of minutes

I tried it many times in a period of two weeks with the same result. Any ideas ?

notme

legendary

Activity: 1904

Merit: 1002

Does this include armory? I'm really only interested to simplify my air-gapped wallet setup.

EhVedadoOAnonimato

hero member

Activity: 630

Merit: 500

I've noticed that the behavior is different if I run bitcoin-qt as root. It starts normally, the splash screen shows up and stays there for a while (in contrast with the immediate crash as when I run with the normal user). While the splash screen is saying "Rescanning...", it crashes with the following error message:

Code:

root@bitsafe:/home/user# bitcoin-qt

************************
EXCEPTION: NSt8ios_base7failureE
CAutoFile::read : end of file
bitcoin in Runaway exception

terminate called after throwing an instance of 'std::ios_base::failure'
what(): CAutoFile::read : end of file
/usr/bin/wrapped_bin/bitcoin-qt.wrp: line 44: 3436 Aborted $WRAPPER_ORIGINALBIN -datadir=$BITCOIN_HOME -nolisten $*

Does this give you any clue?

EhVedadoOAnonimato

hero member

Activity: 630

Merit: 500

What do you mean by prefix? The directory? I've tried. Also, when I use the icon shortcuts, it doesn't work either (the splash screen shows up and closes almost instantly)

rb1205

hero member

Activity: 797

Merit: 1017

Try to run just bitcoin-qt without the prefix

EhVedadoOAnonimato

hero member

Activity: 630

Merit: 500

I'm having the following error when trying to launch bitcoin-qt in BitSafe:

Code:

user@bitsafe:/mnt/disk$ /usr/bin/bitcoin-qt
tar: ssh: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
/usr/bin/wrapped_bin/bitcoin-qt.wrp: line 44: 3907 Bus error $WRAPPER_ORIGINALBIN -datadir=$BITCOIN_HOME -nolisten $*

Does anyone have any idea of what this means? And, even better, does anyone have a workaround? Cheesy

rb1205

hero member

Activity: 797

Merit: 1017

Now I see your point. The problem isn't on the reported local time, but on the UTC time used by the Bitcoin client. Sorry for taking so long to get it Cheesy

I'll see how to fix this. In the meanwhile, here's a workaround to the issue tailored for your needs. Just copypaste it in a text file and save it in the same USB drive you installed BitSafe on.

Code:

#!/bin/sh

#Fix how debian reads/writes hwclock
sudo sed -i 's/UTC=yes/UTC=no/' /etc/default/rcS

#Set the timezone
sudo ln -sf /usr/share/zoneinfo/Asia/Hong_Kong /etc/localtime

#Set UTC time as current(hwtime) - 8 hours.
sudo date -s @$(expr $(date +%s) - 28800)

Once done, you'll have to launch it from /live/squashfs/ before launching bitcoin. Let me know if it works!

chunglam

donator

Activity: 229

Merit: 106

Quote from: rb1205 on April 18, 2012, 10:54:41 AM

Can you tell me the timezone reported by date?

UTC, that's why I thought it is wrong. If bitcoin client expect UTC time from OS, it should be my local time minus 8 hours in my time zone.

rb1205

hero member

Activity: 797

Merit: 1017

Can you tell me the timezone reported by date?

chunglam

donator

Activity: 229

Merit: 106

Quote from: rb1205 on April 18, 2012, 10:07:33 AM

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?

I choose English. The output from "date" command is exactly same as my local time, but it is wrong because it should be local time-8 in my case. Besides, the bitcoin client always complaint the incorrect time and keep saying the block chain data is behind 8 hours even it already downloaded latest block(I compared the block number with bitcoinwatch.com).

rb1205

hero member

Activity: 797

Merit: 1017

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?

chunglam

donator

Activity: 229

Merit: 106

Quote from: rb1205 on April 18, 2012, 08:17:21 AM

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

hero member

Activity: 797

Merit: 1017

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

donator

Activity: 229

Merit: 106

Quote from: rb1205 on April 16, 2012, 03:43:24 AM

Quote from: chunglam on April 15, 2012, 07:27:03 PM

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

hero member

Activity: 797

Merit: 1017

Quote from: chunglam on April 15, 2012, 07:27:03 PM

Unable to download from Dropbox(error 404).

Temporary problem, fixed now.

chunglam

donator

Activity: 229

Merit: 106

Quote from: rb1205 on April 15, 2012, 06:28:02 PM

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

hero member

Activity: 797

Merit: 1017

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

rb1205

hero member

Activity: 797

Merit: 1017

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

Red Emerald

hero member

Activity: 742

Merit: 500

Quote from: rb1205 on February 08, 2012, 11:46:59 AM

Quote from: Red Emerald on February 07, 2012, 05:25:54 PM

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.

Topic: [OpenSource live USB OS] BitSafe, a safety deposit box for your bitcoins. (Read 19491 times)