Hallo zusammen, diesen Mittwoch treffen wir uns wieder zum Bitcoin Themenabend in der dezentrale [1]. Dieses Mal als offene Fragen&Antworten Runde, jede/r darf alle Fragen in den Raum werfen. Zum Beispiel ist von der Themenliste noch offen: - Forks - Trading - Anonymität - Wallets - Multisig - Altcoins - Smart Contracts - Angriffsszenarien - Atomic Swap - Sidechains Wir sehen uns um 19:00, Ente [1] dezentrale eV Dreilindenstraße 19 04177 Leipzig https://www.openstreetmap.org/way/41760585 |
|
|
|
We have been looking through your project and your github. We are going to take on the task of Building our Own Hardware wallet for our Coin XcelR.
Resistance is futile. |
|
|
|
|
Weiter gehts nächste Woche Donnerstag, 2018-08-16, zum Bitcoin Stammtisch im Uptown.
Diesmal ohne mich, viel Spaß euch allen.
Libre Grüße,
Ente
|
|
|
|
Hallo zusammen, wir treffen uns diesen Mittwoch, 01. August, wieder zum monatlichen Bitcoin Themenabend in der dezentrale [1]. Noch git es kein definitives Thema. Ein Vorschlag war "Geschichte der Cryptograpie", da weiß ich aber nicht, ob das schon bereit ist :-) Meine Idee war ein informeller "Bitcoin und Steuern" Selbsthilfekreis, wo wir Einschätzungen, Ideen und Vorgehensweisen sammeln. Rechtssichere Anweisungen wird es nicht geben, da die Rechtslage in vielen Dingen noch nicht mal klar ist ^^ Fall ihr andere Ideen habt, bringt sie mit, und/oder setzt sie auf die Mailingliste. Libre Grüße, Ente [1] dezentrale eV Dreilindenstraße 19 04177 Leipzig https://www.openstreetmap.org/way/41760585 |
|
|
|
|
Diesen Donnerstag, 19:00, treffen wir uns zum nächsten Bitcoin Stammtisch im uptown.
Ich bin auch wieder am Start und freue mich schon drauf!
Libre Grüße,
Ente
|
|
|
|
|
Well, click the link in OP?
emptied on 2012-12-03 21:24:43
Ente
|
|
|
|
Hallo zusammen, diesen Mittwoch, 04.07. treffen wir uns wieder um 19:00 zum Bitcoin Themenabend in der dezentrale[1]. Dieses Mal gibt es eine einsteigerfreundliche Einführung in Kryptographie und gebräuchlichen Algorithmen. Ich bin gespannt! Bitte bringt auch Themenvorschläge mit, wir brauchen neues Futter für die nächsten Themenabende. Libre Grüße, Ente [1] dezentrale eV Dreilindenstraße 19 04177 Leipzig https://www.openstreetmap.org/way/41760585 |
|
|
|
|
Weiter gehts diesen Donnerstag, wie immer 19:00 im uptown.
Ohne mich, ich bin nächstes Mal wieder am Start.
Viel Spaß,
Ente
|
|
|
|
Hallo zusammen, diesen Mittwoch, 06.06. treffen wir uns wieder um 19:00 zum Bitcoin Themenabend in der dezentrale[1]. Diesmal gibt es einen Vortrag/Rezension/Zusammenfassung vom Buch "The Bitcoin Standard" von Saifedean Ammous. Ich hab schon viel Lob zu dem Buch gehört, die 304 Seiten selbst aber noch nicht gelesen. Um so mehr freue ich mich also auf den Themenabend. Libre Grüße, Ente [1] dezentrale eV Dreilindenstraße 19 04177 Leipzig https://www.openstreetmap.org/way/41760585 |
|
|
|
Hallo zusammen, der Bitcoin-Stammtisch trifft sich morgen, ab 19:00, wie immer im uptown [1]. Bis morgen, Ente [1] Uptown Coffee Bar Riemannstraße 44, 04107 Leipzig http://www.uptowncoffee.de/ |
|
|
|
|
Hope you had a good time, whatever you were up to, goatpig.
What can I say, I removed the armorydb database folder, let it rescan, and it now seems to work! Previously unknown wallets scan and show their (empty) balance.
I'll test some more scenarios, but for now it's solved.
Thank you for staying with me!
Ente
|
|
|
|
|
Next, I used a fresh Debian 8 for ArmoryQt. Still "hexit" errors.
Then I installed a fresh Debian 9 on a physical machine (instead of the VMs before). Just installed ArmoryQt, nothing else. And, again, scanning for a new wallet never ends in ArmoryQt, with "hexit" errors.
So it must be ArmoryDB after all?
Any ideas what to do? I did upgrade ArmoryDB before, no change. The last thing I didn't do yet is delete the ArmoryDB database?
Ente
|
|
|
|
https://cyber.bgu.ac.il//advanced-cyber/airgapThere are a couple of videos on the page above, but this is the direct link to the "BeatCoin" paper's pdf. I've seen exploits of this nature in the past but this one can use the GPIO pins on a raspberry pi to transmit the data (see first video). Given that historically Armory has offered downloads for the raspberry pi, and many here use the split online-offline/cold storage setup, I've posted here for awareness/discussion. Relevant to more typical computers/laptops too. This all assumes the offline machine has been compromised. While we can minimise the chances of that by not attaching USB drives and other external media, the reality is that software upgrades to the offline system (i.e. Armory's signer) do need to happen to ensure compatibility from time to time. Excluding that, there is still the need to get transactions on and off the offline system, which provides the opportunity for an attacker if the online system is compromised. For the RPi: this thread by TierNolan seems to offer an alternative to using USB devices for data transfer in order to help keep the offline system clean/secure. I'm unsure whether the GPIO being in use would mitigate outgoing transmissions by malware, but inclined to assume not. I'm not an expert, but it certainly unnerves me to see a layer of the security model eroded like this - the suggestion of needing some sort of Faraday cage doesn't seem as excessively cautious as it used to be. Certainly a win for dedicated hardware wallets that only have the required components included  "ODINI : Escaping Sensitive Data from Faraday-Caged, Air-Gapped Computers via Magnetic Fields" ..right from https://cyber.bgu.ac.il//advanced-cyber/airgapSCNR :-) Ente |
|
|
|
|
I started over with a freshly installed Debian 9, and then with again with a completely empty .armory folder too. v0.96.4, local ArmoryQT connecting to remote ArmoryDB.
Again, the same symptoms, it stops scanning at "one minute left" with those hexit errors.
I did everything exactly like always, with dependencies and commands from old written down notes.
So it can only be something broken at my ArmoryDB, or a general imcompatibility with the Qubes OS Debian VM templates, or a networking problem in between?
Ente
|
|
|
|
Hallo zusammen, diesen Mittwoch, am zweiten Mai, trifft sich wieder der Bitcoin Themenabend, wie immer in der dezentrale[1] um 19:00. Diesmal gibt es einen Blick hinter die Kulissen, wie Bitcoin in der öffentlichen Verwaltung positioniert ist. Unser langjähriger Undercoveragent M. wird exklusiv berichten. Ich freue mich drauf, bis Mittwoch! Ente [1] dezentrale eV Dreilindenstraße 19 04177 Leipzig https://www.openstreetmap.org/way/41760585 |
|
|
|
Send me one of those fresh, broken wallets.
E-mail sent. Ente |
|
|
|
Hallo zusammen, diesen Donnerstag treffen wir uns um 19:00 wieder zum Bitcoin Stammtisch im Uptown [1]. Nutzt schnell die Gelegenheit mit Bitcoin zu bezahlen, bevor die Gebühren wieder steigen ;-) Libre Grüße, Ente [1] Uptown Coffee Bar Riemannstraße 44, 04107 Leipzig http://www.uptowncoffee.de/ |
|
|
|
To remove factors, I tried again: - removed all wallets, ArmoryQt starts fine in online mode - created a new wallet, it's online immediately - shut down Qt and DB - started Qt, created a new wallet with password, nothing else changed or touched (in offline mode) - shutdown Qt - started DB, then Qt - Qt starts scanning (INFO) ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
(python:14412): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed
"Scanning" comes around every 5 secs, that Gtk warning came only once. Nothing else for an hour scanning. At "35 sec left", the last DBlog.txt line is -INFO - 12:29:15: (BlockchainScanner.cpp:852) scanned from block #514744 to #515526 (which is not the current blockheight) and Qt says -ERROR - : (BinaryData.h:563) odd hexit count
over and over. After restarting Qt, I can't connect to DB any more, I have to restart the service. tl;dr: a single fresh plain wallet, nothing changed, nor commented, and Qt hangs.Oh, maybe it has something to do with a recent upgrade to Debian 9? I probably didn't import/rescan since then. But I did install/compile v0.96.4, which threw no errors. Ente |
|
|
|
ArmoryDB is running by itself on its own headless host. Restarting the ArmoryDB service runs just fine, the last dbLog.txt entries are: -WARN - 16:13:54: (BDM_supportClasses.cpp:1944) running 35 zc parser threads
-INFO - 16:21:05: (BlockchainScanner.cpp:857) scanned block #518330
-INFO - 16:21:26: (BlockchainScanner.cpp:857) scanned block #518331
Starting ArmoryQt on a remote machine: (again, dbLog.txt) -INFO - 16:28:37: (BDM_Server.cpp:1121) registered bdv: a*****0
-INFO - 16:28:38: (BDM_supportClasses.cpp:401) Starting address registration process
-INFO - 16:28:43: (BlockchainScanner.cpp:852) scanned from block #0 to #142691
[..] and then, finally: -INFO - 17:11:48: (BlockchainScanner.cpp:852) scanned from block #514744 to #515526
As the last line, from then on ArmoryDB hangs. ArmoryQt says: (INFO) ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
-ERROR - : (BinaryData.h:563) odd hexit count (scanning comes a few hundred times, then the hexit error several times a second) Ente |
|
|
|
To triplecheck, after removing those wallets again, I created a fresh wallet while not connected to DB. Restarting DB and then Qt, it starts scanning history. Everything again the same, seconds before finishing it hangs DB and Qt. This time I got ever-repeating errors in Qt:
You mean the DB hangs even without any imports? These symptoms happen with creating a new plain armory-wallet via GUI, yes. Nothing imported, neither the wallet itself nor any single address. Of course I kept Armory offline when creating the wallet, so it would start a full rescan when being online, reaching DB again. Ente |
|
|
|
|
Show Posts
