How To Install Debian 10 Buster - Complete Steps With ...
How To Install Debian 10 Buster - Complete Steps With ...
How to install Debian from USB : chrubuntu
How to run a Bitcoin node in Debian - Vicente Hernando
Debian USB bitcoin miner - Knowledge
How to install Electrum on a Debian or ... - Bitcoin Electrum
What if Bitkey but for Monero
I just learned about bitkey, and boy am I impressed. Like my actual point is that I think a critical fatal flaw in the crypto economy and bitcoin network is the reliance on centralized hardware manfufactures whose proprietary closed garden systems and also of course centralized exchanges. I think it's just a matter of time before Trezor and LedgerNano become targets, or some rouge intelligence agent releases to the darknet some tool to crack them or compromise them.
BitKey is a bootable system image based on Debian containing everything you need to perform highly secure air-gapped Bitcoin transactions. You don't need to install it to a hard drive because it runs live from RAM. You just write the ISO image to a USB drive or burn it to CDROM.
I'm a die hard open source linux open system advocate, and I think that bitkey is the right step in the right direction. And my point being, anyone who's a developer could make some version of their own to be audited by the public community. Eventually we would have a handful of publically trusted builds by different developers, and this could be done for the major cryptos, or any crypto, but especially monero since it barely has hardware support. But the design of bitkey being an iso image on a cd rom or a usb, set to maximum privacy with two computers and a third device that scans QR codes. (on a side note there are security issues with QR codes, so that is one area for improvement). I'm trying to imagine a world where people can't get safe devices, can't get hardware wallets, and need an open source alternative to compromised desktops. Obviously something as advanced as a linux OS build spread across three devices for airgapping has a learning curve, but UI can increase over time. We have to remember there are a lot of tyrants in this world who want the monero and btc network to fail, want the fungibility and privacy and cash like nature fail, want to backdoor everything, they want to know if you're hungry, if you need to take a shit, before you even know, Minority report shit, but sadly unironically, and increasingly so. Windows is the devil obviously, Apple even more so. We need a world moving towards Linux, RVISC chips, raspberry pis. Even the best intentions of cypherpunk and monero are very very vulnerable without the hardware to back it up. So there really needs to be a move towards this.
Hi everyone, Newbie here. Right now, I just want to pay for a VPN service, but I imagine I will use BTC to pay for more things as I get more familiar with the currency. For privacy, I am planning to buy BTC from a Bitcoin ATM in town. My problems begin with wallets. I understand that it is best to run your own full node for privacy, so I am going to run a full node bitcoin core installed on Tails OS to route it through TOR. But I have no experience with Debian, so if you happen to know a guide on doing this (besides the official one) would be most appreciated. My question is, if I am only going to make a single payment for now, do I have to run my node all the time? Could I just unplug the USB the wallet is on and make it a """cold""" storage? Or would there be associated problems? Should I use a mixer after buying Bitcoin from an ATM? Is my plan stupid and there is a much easier way that offers a comparable privacy level? Please let me know! My head is splitting from reading jargony articles, so I welcome any suggestions.
Hi Redditors. I am going to post in this thread my experiences in getting my Desktop (Debian) machine running Armory in watch-only mode, and coupling that with an offline Raspberry Pi (which holds my private keys) for signing the transactions previously made in watch-only mode. I actually compiled Armory from source directly on my Pi. This guide is probably more for the bitcoin 'power user', as to run Armory online, and broadcast the signed transactions, you need to have a bitcoin full node running (bitcoind). Basic requirements:
Online machine - running a full node (bitcoind)
Raspberry Pi - I used an old Pi 1 Model B with just 512Mb memory, and 2 USB slots.
2x USB thumb-drives. One for wallet backups, the other for transferring unsigned tx's to the rPi, and signed tx's back to the Desktop.
Armory 0.96.4 for the Raspberry Pi 1, Model B (512Mb RAM, 2xUSB) (compiled from github sourcecode on the Pi itself!)
Using the Pi as an offline complement to a Debian Desktop "watch-only" Armory install.
Desktop Debian Armory watch-only talks to my full node, bitcoind, which is also on the Debian desktop.
I'll post the guide in digestible sections...
I should begin by saying I installed source code from git, and got Armory to build the DB on my desktop initially, WITHOUT creating a wallet.. (This allowed me to debug what was going on a little!)
Go to Bitcoin.org, select Armory.. It leads to a Download from Git: https://github.com/goatpig/BitcoinArmory/releases Followed the procedure for Linux Debian verify code, compile, install, all straight-forward.. Began by running bitcoind, and telling Armory where to find it. This is the command I used, obviously it was all on one line and didn't include the arrows/explanations!:
python ArmoryQt.py \ --satoshi-datadir=/BlockChain/chain20180414/blocks \ # <-----(where my bitcoind blocks live) --datadir=/ArmoryDataDi \ # <-----(this is instead of ~/.armory) --dbdir=/ArmoryDataDidatabases # <-------(again, non std. place used for Armory's databases.. my choice.)
So, on the Desktop, after the initial "build databases" (NB the initial "Build Databases" took about 1.5h and my two CPUs were maxed the whole time, Temps up to 62C. Not ideal; Im not in a rush!) I then wanted to import a watch-only wallet. Before I did this, I took a full backup of the Armory data dir: /ArmoryDataDi (or ~/.armory in a default installation). I'd hate to have to make Armory do another full sync with the bitcoind node!
Next step: offline wallet (with Private Keys) is on a Raspberry Pi. I downloaded the source and managed to compile it on the pi itself! :) Though there were some gymnastics needed to setup the Pi. My Pi is running Raspbian based on Wheezy.. quite old! I did the following on the Pi:
apt-get update apt-get upgrade (<---took about an hour!) apt-get install autotools-dev apt-get install autoconf
Then I followed the instructions exactly as I had done for my Debian Desktop machine, EXCEPT: I had to increase the Pi's swap space. I upped it from 100Mb to 400Mb. The compilation took 7 hours, and my poor SD card got a thrashing. But after compilation, I put the Swap back to 100Mb and Armory runs ok with about 150Mb of memory (no swap needed). Swap increase on the Pi: use your favourite editor, and open the file /etc/dphys-swapfile add/change the following line:
Then, REBOOT the Pi:
sudo shutdown -h -P now
Once the compilation was done on the Pi, put the swap back, rebooted and created an Armory wallet. I added manual entropy and upped the encryption 'time' from 250ms to 2500ms - since the Pi is slow, but I'll be happy to wait for more iterations in the Key Derivation Function. Once the wallet was created, it obviously prompts you for backup. I want to add a private key of my own (i.e. import), so don't do the backup until this is over. I import my Private Key, and Armory checks that this corresponds to a Public Key, which I check is correct. This is the point now where the Pi storage medium (e.g an SD card) has to be properly destroyed if you ever get rid of it. I had thought that now would be a good time to decide if your new wallet will generate Segwit receiving addresses, and also addresses used to receive 'change' after a transaction.. But it seems Armory WON'T let you switch to P2SH-P2WPKH unless your Armory is connected to a node offering "WITNESS" service. Obviously, my Pi is offline and will never connect to a node, so the following will not work on the Pi:
x Use File Settings Fee and address types.
x Set the "Preferred Receive Address Type" to P2SH-P2WPKH
x Also Set the "Change Address" to P2SH-P2WPKH for left-over loose change!
NB: I thought about setting this on the Debian "watch-only" wallet, but that would surely mean doom, as the Pi would not know about those addresses and backups might not keep them.. who knows... So, end result:- no segwit for me just yet in my offline funds.
--If anyone can offer a solution to this, I'd be very grateful--
Ok, now this is a good point to back up your wallet on the Pi. It has your imported keys. I choose a Digital Backup - and put it on a USB key, which will never touch the internet and will be stored off-site. I also chose to encrypt it, because I'm good with passwords.. NB: The Armory paper backup will NOT back up your imported private keys, so keep those somewhere if you're not sweeping them. It would be prudent to have an Armory paper backup anyway, but remember it will likely NOT help you with that imported key. Now for the watch-only copy of the wallet. I want to get the "watch-only" version onto my Desktop Debian machine. On the Pi, I created (exported to a USB key) a "watching-only" copy of my wallet. I would use the RECOMMENDED approach, export the "Entire Wallet File". As you will see below, I initially exported only the ROOT data, which will NOT capture the watching-only part of the Private Key I entered manually above (i.e. the public Key!). Now, back on the Debian Desktop machine... I stopped all my crontab jobs; just give Armory uninterrupted CPU/memory/disk... I also stopped bitcoind and made a backup prior to any watch-only wallet being imported. I already made a backup of Armory on my Desktop, before any wallet import. (this was needed, as I made a mistake.. see below) So on the Debian Desktop machine, I begin by firing up bitcoind. my command for this is:
I know from bitter experience that doing a scan over the blockchain for a new wallet takes a looong time and a lot of CPU, and I'd like it to play nicely; not gobble all the memory and swap and run my 2xCPUs both at 100% for four hours... So... I aim to run with --ram-usage=X and --thread-count=X (For me in the end, X=1 but I began with X=4) I began with --ram-usage=4 (<--- = 4x128Mb) The result is below...
TypeError: cannot concatenate 'str' and 'int' objects
It didn't recognise the ram-usage and carried on, crippling my Debian desktop PC. This is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up, and it can take over 30 minutes just to exit nicely from bitcoind and ArmoryDB. So, I ssh to the machine from another computer, and keep an eye on it with the command
I'd also be able to do a "sudo reboot now" if needed from here.
So, trying to get my --ram-usage command recognised, I tried this line (added quotes):
Loading Armory Engine: Armory Version: 0.96.4 Armory Build: None PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('debian', '9.4', '') User home-directory : /home/ Satoshi BTC directory : /BlockChain/chain20180414 Armory home dir : /ArmoryDataDi ArmoryDB directory : /ArmoryDataDidatabases Armory settings file : /ArmoryDataDiArmorySettings.txt Armory log file : /ArmoryDataDiarmorylog.txt Do wallet checking : True (ERROR) ArmoryUtils.py:3723 - Unsupported language specified. Defaulting to English (en) (ERROR) ArmoryQt.py:1833 - Failed to start Armory database: cannot concatenate 'str' and 'int' objects Traceback (most recent call last): File "ArmoryQt.py", line 1808, in startArmoryDBIfNecessary TheSDM.spawnDB(str(ARMORY_HOME_DIR), TheBDM.armoryDBDir) File "/BitcoinArmory/SDM.py", line 387, in spawnDB pargs.append('--ram-usage=' + ARMORY_RAM_USAGE) TypeError: cannot concatenate 'str' and 'int' objects
So, I edit the Armory python file SDM.py:
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=4') #COMMENTED THIS, SO I CAN HARDCODE =4 # ' + ARMORY_RAM_USAGE)
Running it, I now have acknowledgement of the --ram-usage=4:
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=4
Also, even with ram-usage=4, it used too much memory, so I told it to quit. It took over 30 minutes to stop semi-nicely. The last thing it reported was:
ERROR - 00:25:21: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
But that didn't seem to matter or corrupt the Armory Database, so I think it's ok. So, I get brave and change SDM.py as below, and I make sure my script has a command line for --ram-usage="ABCDE" and --thread-count="FGHIJ"; the logic being that these strings "ABCDE" will pass the IF criteria below, and my hardcoded values will be used...
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=1') #COMMENTED THIS, SO I CAN HARDCODE =1 # ' + ARMORY_RAM_USAGE) if ARMORY_THREAD_COUNT != -1 pargs.append('--thread-count=1') #COMMENTED THIS, SO I CAN HARDCODE =1 #' + ARMORY_THREAD_COUNT)
So, as usual, I use my script and start this with: ./StartArm.sh (which uses command line:)
(this forces it to use my hard-coded values in SDM.py...) So, this is the command which it reports that it starts with:
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=1 --thread-count=1
Again, this is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up. So I ssh to the machine and keep an eye on it with:
So, on the Debian Desktop PC, I inserted the USB stick with the watch-only wallet I exported from the Pi. Start Armory... Import "Entire Wallet File" watch-only copy. Wait 4 hours.. YAY!!! After running Armory for about 30m, the memory usage dropped by 400m... wierd... It took ~2 hours to get 40% completion. After 3.5 hours it's almost there... The memory went up to about 1.7Gb in use and 900Mb of Swap, but the machine remained fairly responsive throughout, apart from a few (10?) periods at the start, where it appeared to freeze for 10-30s at a time. (That's where my ssh session came in handy - I could check the machine was still ok with a "free -h" command) Now, I can: Create an unsigned transaction on my Desktop, Save the tx to USB stick, Move to the Pi, Sign the tx, Move back to the Desktop, Broadcast the signed tx.
My initial Mistake: This caused me to have to roll-back my Armory database, using the backup. so you should try to avoid doing this.. On the Pi, I exported only the ROOT data, which will NOT capture the watching-only part of the Private Key It is RECOMMENDED to use the Digital Export of Entire Wallet File from the Pi when making a watch-only copy. If you just export just the "ROOT data", not the "Entire Wallet File", you'll have problems if you used an imported Private Key in the offline wallet, like I did. Using the ROOT data text import, after it finished... my balance was zero. So,. I tried a Help->Rescan Balance (Restart Armory, takes 1minute to get back up and running) No Luck. Still zero balance. So, I try Rescan Databases.. This will take longer. Nah.. no luck. So, I tried again, thinking it might be to do with the fact that I imported the text "root data" stuff, instead of following the (Recommended) export of watching-wallet file. So, I used my Armory backup, and wound back the ArmoryDataDi to the point before the install of the (zero balance) wallet. (you should not need to do this, as you will hopefully use the RECOMMENDED approach of exporting the "Entire Wallet File"!)
Ever since the post-credits scene in season 2, I've been thinking about how the stage 1 "payload" that encrypted all of the E-Corp systems might have been built, and how it might be flawed enough to permit data recovery. No sci-fi time-travel magic required for this theory. We never get a direct look at the malware, but we do get a smattering of references to what it is throughout the episodes so far. Not enough to get a totally clear picture, but it's somewhere to start with educated guesses. In S01E01, Mr. Robot is explicit about the aims:
If we hit their data center just right, we could systematically format all the servers, including backup. It would be impossible to enforce outdated paper records. It would all be gone.
Okay. They want to irreversibly delete the data on all of E-Corp's servers and backups. In S01E02, when tasking Elliot with blowing up the Comet electric natural gas plant to take out the tape backups at Steel Mountain, Mr. Robot elaborates:
Once we blow up the pipeline, Darlene's worm will kick into high gear at the US datacenter, which you helped us to install. Thank you very much. The redundant backups at their eastern datacenter in China? The dark army is covering us on that.
Okay, we've learned the way they'll do it is with a worm, which Darlene wrote. A worm is malware that is designed to replicate itself and carry a payload. In S01E08, after successfully entering the work order to remove the honeypot around CS30, Elliot states:
In 43 hours, exactly, our server will no longer be a honeypot, and that rootkit you wrote will take down Evil Corp. We did it Darlene. It's going to happen.
Despite what Lloyd might have said, rootkits are not serial rapists with very big dicks. They're malicious code designed to hide the presence of an attacker (inc. processes they might be running, alterations to system login and authentication modes to accept a backdoor credential) and their tools on a system once it has been compromised. Unqualified, the term "rootkit" commonly refers to kernel-mode rootkits, which operate directly within the context of the operating system, and frequently loaded through the same facilities provided for installing new device drivers. They can hide files/directories, running processes, network connections, and themselves (e.g. in the list of loaded drivers) from scanning entities on the same system. One way to detect a rootkit is to look for discrepancies between what tools on the system report (e.g. in terms of active network connections) versus what is observed externally (e.g. on a network monitoring device). That makes the discussion of "honeypots" a little bit strange. A honeypot usually refers to a target on a network that's designed to be enticing to attackers, so that they try to hack it, but isn't "real" in the sense that it processes real data. It might be instrumented such that probing and reconnaissance activities targeting the honeypot are tied to network hacking alerts. I can think of one of three interpretations of what turning server cs30 into a honeypot might mean:
They've installed additional monitoring software on cs30.
They've replaced cs30 with a totally different system that looks like cs30 to an outsider.
They've installed additional network monitoring around cs30.
But none of these interpretations really make sense. If it's #1, if the rootkit was written properly, it's likely that additional monitoring would be fruitless, and the attack could be carried out without the whole Whiterose meeting riddles. If it's #2, then the rootkit would probably not have been copied over to the clone, and fscociety would have noticed their server misbehaving. Unless, of course, E-Corp discovers the rootkit on cs30 as part of this process, in which case, they could have just cleaned it up, and closed off fsociety access to the internal server. If it's #3, then the periodic use of the backdoored access to cs30 by fsociety should have been noticed by looking at that network monitoring data, likewise leading to a server cleanup and removal of the backdoor. I'll chalk this up to somewhat cavalier and imprecise use of technical terminology by a TV show, and press on. What have we learned so far?
fsociety has backdoor root access to an internal server at E-Corp, which is adequately hidden by a rootkit
fsociety will use a worm to propagate a data destruction payload throughout the E-Corp network using privileged credentials extracted from that server
In S01E09, after Tyrell coerces Elliot into showing him the fsociety arcade:
Tyrell: What is it that you're doing exactly? Elliot: Encrypting all the files. All of Evil-Corp's financial records will be impossible to access. The encryption key will self-delete after the process completes.
Wait a second? Encryption? Encryption key? I thought we were after data deletion. Of course, there's a perfectly plausible explanation: deleting data takes time. If you go around rm -rf'ing servers, there's a good chance that recoverable data will be scattered around those hosts. By performing bulk encryption, you overwrite all data on the target systems once, can still permit access to everything on the system while the encryption is occurring, and then destroy the key once the encryption process is completed. This lowers the length of the window in which someone can realize that something has gone terribly wrong. The key is small (tens of bytes, not to gigabytes or hundreds of gigabytes), and can be deleted almost instantaneously. Several full disk encryption systems, including FileVault in macOS, and the now-defunct TrueCrypt have the ability to do this: you start encrypting the drive, but can continue working while the data is read, encrypted, and overwritten unnoticed in the background. Some ransomware strains also follow this practice, so it's not an unreasonable approach. However, cryptography is a loaded foot cannon for the unwary, and it's surprisingly easy to make a small mistake that unravels the whole thing. In S01E10, as Elliot looks for Tyrell at the E-Corp building, in voice-over he says:
A simple program: a worm that can make data unreadable. Malware that took Darlene maybe 2 hours to code. Is that all it takes to kill the world?
And follows with:
I wonder what stage they're at. Denial? Muttering to themselves "no, this can be fixed." Maybe bargaining? Forcing their techs to work overtime to try to decrypt our data. Or have they come to the realization yet that Darlene encrypted everything with 256-bit AES, and it would take an incomprehensible amount of time to crack? That all of their data is actually gone, for good.
AES is a symmetric encryption algorithm in wide use. It's stood the test of time since its standardization in 2000, and lots of people trying to find weaknesses in the last 2 decades. At a 256-bit key length, it would take many multiples of lifetimes of the universe to break, at least so long as computers are still made out of atoms. A quantum computer would not meaningfully assist in this kind of attack, as Grover's algorithm would still require 2128 quantum operations, and this is still going to take many multiplies of lifetimes of the universe to break. But it does raise questions about cryptographic hygiene. Mechanically: what mode of operation is AES being used in to encrypt files? Let's assume Darlene has heard of the ECB penguin and has picked something better like CBC with per-file random initialization vectors. More importantly: where is that key coming from? The right answer is to read it from a operating system provided cryptographically secure random number generator like /dev/urandom on UNIX-like systems, or the equivalent on Microsoft Windows CryptGenRandom. Ideally, perform this random key generation process individually (resulting in unique keys) on every single target system. There have been cases where CryptGenRandom has produced sub-par quality randomness on earlier versions of Windows, but not since Windows XP SP2 or older. My theory is that this is where the fsociety worm went wrong. In S02E01, we see the night of the hack for the first time, and in the terminal we see:
[email protected]:~# ssh -l root bkuw300ps345672-cs30.serverfarm.evil-corp-usa.com [email protected] password: The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usshare/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Thu May 8 16:26:57 2015 from cs30.serverfarm.evil-corp-usa.com [email protected]:~# cd /opt/2/task/2/fd1nfo/fsociety/hscripts/ [email protected]:/opt/2/task/2/fd1nfo/fsociety/hscripts# ls fuxsocy.py loadmod.py rootkitctrl sniff-out.pcap kernel_modules nuke.py sn1ff worm.py [email protected]:/opt/2/task/2/fd1nfo/fsociety/hscripts# ./fuxsocy.py
"Loading Source of Entropy" you say? That sounds awfully like a userspace random number generator. If the entropy pool is too small, or if the random number generation process is otherwise flawed, the key fed into the AES encryption process might be much more predictable than the 256-bit key length would suggest. There was a major incident of this type discovered in 2006, where the Debian GNU/Linux package maintainers for OpenSSL (a popular, and widely used, though terrible) cryptography library commented out some lines that were generating code safety warnings when packaging it for the Debian distribution. Turns out these lines were essential to introducing any kind of real randomness for uses by the library, and this includes key generation and certain signing operations. The fallout was that the affected versions of OpenSSL on Debian GNU/Linux would only generate 32,768 or 214 distinct keys. This also affected things like ECDSA signing, which was mirrored in 2013 when a similar vulnerability in Android led to the theft of about 56 Bitcoins. You would have to know how the flawed key generation was implemented, and it would not necessarily be obvious looking at the keys from the outside, but if there was a flaw of this magnitude, you could break that "256-bit" key almost instantly with e.g. 14-bits of effort. The use of Debian on the E-Corp servers might be a suggestive hint to this historical fiasco too. The screen output also suggests that there might have been a single key generated at the start of the process that was copied as part of the data destruction payload to all of the E-Corp servers. Not ideal from a cryptographic hygiene standpoint. In the post-credits scene of S02E12, Trenton and Mobley discuss:
Trenton: Have you given any more thought to what I said? Mobley: I don't want to discuss this. Trenton: Mobley... Mobley: Fredrick. Trenton: Seriously, Fredrick, what if we could? This might work. Mobley: And also, it might not. I've taken enough risks for one lifetime, I don't want to discuss it anymore. Trenton: But what if we could generate the keys... Mobley: Tanya... will you just please shut up? Trenton: What? This is important. We need to talk about it. ... Trenton: Please, just look at it. Mobley: Okay, so what? Say I did. Then what? Trenton: If what I discovered is real, do you know what that means? Mobley: Yeah, I know exactly what it means. Trenton: Yeah, it means we could potentially undo this whole thing. Put everything back the way it was. Mobley: I know. I know. Trenton: Please. Just look at what I found.
I bet they've looked over the fsociety data destruction payload code and discovered a way to reproduce the key, precisely because there's this kind of flaw in it. Finally, during Tyrell's AMA, a.k.a. S03E03, we get another shot of stage 1 running:
Thread #7 - 233 hosts online, initiating SCP transfer Waiting on thread updates ... Thread #2 - SCP complete. launched encryption tasks Thread #6 - SCP complete. launched encryption tasks Waiting on thread updates Thread #2 - Encryption tasks completed & verified Updating process log Thread #2 - Obtaining next hosts ... read 256 addresses Waiting on thread updates Thread #6 - SCP complete. launched encryption tasks Waiting on thread updates Thread #2 - Starting tasks on 10.0.0.29/24
I interpret this as cs30 copying (via SCP) the data destruction payload to every server on the E-Corp network. The 10.0.0.0/8 IP addresses are designated internal network addresses, and are common for large internal business networks. It's odd that E-Corp would have a totally flat network, and also odd that cs30 itself seems to be copying the payload everywhere (not very worm-like), but perhaps this is just artistic license from the VFX guys. Given how little we see of this screen, and how it was effective at wiping out E-Corp, I think it's safe to assume that the payload being transferred over SCP is both a propagator (i.e. the worm) and a data destruction payload, which would also address it spreading over the entire E-Corp network, even if it isn't flat. It is still suggestive of the single-key possibility though. So, did Darlene fuck up the crypto? I think so. There's a few more suggestive quotes. In S01E06, after dropping USB flash drives in the police parking lot for Elliot, the malware is blocked by antivirus.
Elliot: Did you write that exploit yourself? Darlene: I had an hour. Elliot: So what? You just pulled code from Rapid9 or some shit? Since when did you become a script kiddie? Darlene: I repeat: I had an hour.
We learn that Darlene can be sloppy when doing things quickly, and re-iterating Elliot's voice-over in S01E10:
Malware that took Darlene maybe 2 hours to code.
And another off-hand remark in S01E08:
Elliot: How'd it go with the climate control hack? Darlene: Handled. I happen to be really smart and good at things. Not like you give a shit.
There's a lot of ways that subtle faults in a cryptographic implementation can lead to the entire system coming tumbling down. Darlene might be an expert malware coder, but that's not a universal skill that necessarily translates over to other aspects of information security. If you're curious about not falling into "bad noob practices" with crypto, there's a great set of cryptography building and breaking challenges that don't require much more than basic algebra, statistics, and coding skills. Wildly speculating now:
The Dark Army has a copy of the original payload. Irving was probably directed to take a copy of it during the Dark Army visit to the arcade.
It's likely that the Dark Army analyzed and discovered this cryptographic flaw as a result.
Now that stage 2 has been executed, knowledge of this flaw is the only thing that could prevent the final collapse of E-Corp.
Leon's visit to Arizona is far from friendly, because the Dark Army will probably want to have oversight over anyone who might have seen the flawed code. Since Elliot (as Mr. Robot) is working with them, and Darlene is being minded by their inside guy at the FBI, they're under control. Romero is dead. That leaves Trenton and Mobley. RIP.
GUIDE: How to use Electrum with your Ledger Nano S on Tails 3.7
The official guide doesn’t provide useful info. Moreover, Tails has some restrictions for security and privacy reasons. This guide uses only well-documented features of Tails and doesn’t require any additional stuff (usb-sticks, other OS etc).
This guide assumes both features are activated on Tails Greeter every startup:
encrypted persistence storage;
Tails is based on Debian GNU/Linux. And to detect the Ledger Nano S we need the python library provided by python3-btchip package. This package is available on sid, but it depends on python3 (>= 3.6~). Tails has python 3.5.3 installed. So…
… we’ll install btchip-python library by means of the python’s pip tool. To make this library persistently installed you should activate Tails “Dotfiles” Persistence feature and restart Tails. I don’t know how to configure the pip tool to go through Tor. So this guide suggests to use GitHub repositories. Open terminal in the Home folder and download git repositories:
To check installation open the folder in terminal:
Don’t forget every login update udev rules. Start electrum… and get an error: Firmware version (or “Bitcoin” app) too old for Segwit support. Actually the Electrum 3.0.6 is too old for the latest Ledger Nano S firmware. So download Electrum-3.1.3.tar.gz from the official site and untar it. In the electrum directory, run: 'python3 electrum'. Your feedback is welcome. HODL! EDIT_1: fixed typo. EDIT_2: libudev-dev=237-3~bpo9+1 libudev-dev/stretch-backports EDIT_3: works for Electrum-3.2.2 on Tails 3.8 as well.
I bought a Digital Bitbox earlier this year. It's aesthetically pleasing, all the specs seemed pretty good, designed in Switzerland. Should have just got a Trezor. When it arrived, I moved my paltry savings onto it, made (and verified) a backup on the included SD card, and put it in my super secret closet box. It's not like I was carrying this thing around in my pocket. Yesterday, I decided to spend some bitcoin. I install the desktop app on my Debian machine, copy-and-paste in some random shell wizardry from their website to make a udev rule, plug the wallet in, type in my password, paste in the recipient address, type in the amount, and hit send. The app tells me to touch the virtual button on the wallet to confirm, and as son as I do... crash. Segmentation fault. I try a couple more times. Same result. So I try the usual things: different USB ports, reboot my computer... and then all of a sudden, instead of prompting me for my password, the desktop app gives me the screen where you initialize a new wallet. I have no idea how or why, but my hardware wallet was wiped. Fortunately, I had the backup, so after changing into a clean pair of pants, I restored it in electrum, and everything is fine. Other than the fact that I'm out whatever 80 euros was worth back when I bought it. And that I'm going to have to go through the hassle of transferring them to a paper wallet or a trezor, since I'm not happy having it all sitting on my desktop. Probably a paper wallet, because this is exactly the reason I held off getting a hardware wallet for a long time: I always worried about what would happen if it just didn't work one day. I guess you restore your backup is what, but this should just... never happen.
So I recently I became quite interested in mining and cyptocurrencies in general. So interested in fact that I bit the bullet and decided to buy myself a GAW Fury. I then spent some time doing research on how to set up a GAW or Zeus ASIC on Linux, in particular on a Raspberry Pi, and have found most guides to be awful. The reason they are so bad IMHO is that they assume quite a bit of prior knowledge, either with Linux or mining, and give very little instructions. So I have tried to put together a guide that requires very little prior knowledge. It is my aim that anyone could get their shiny new asic up and mining in no time using this guide. Anyway, I present...
The Complete Noobs Guide to Setting Up a Zeus or Gaw ASIC on Debian/Ubuntu/Raspberry Pi
About Cyrptocurrencies and Their Jargon
If you are new to cryptocurrencies and how they work I suggest taking a look at this series of KhanAcademy videos. They are for Bitcoin but the theory is the same. I found them very helpful when it came to understanding what mining actually does and the mechanics of cyrptocurrencies. Also take a look at sircamm22 his info found here, is great and breaks down a large number of concepts. I slightly disagree with no. 21 regarding preordering. Just exercise common sense.
If you are new to Linux you could follow along by simply typing in the commands. However I highly recommend taking the time to learn what you are doing. This course is a great place to start.
By the end of this section you will have your device turned on, fully setup and connected to the internet with. Note: Commands to be typed into the command line will be displayed like this:
echo Hello World
For laptops and desktops already running Ubuntu or Debian I will assume you have setup your internet setup as part of the installation. If not: There are plenty of guides out there and the installation/setup process is very easy. A good place to start for Ubuntu is here. Now open up a terminal window. Ctrl + alt + t on a standard Ubuntu installation. If you plan on using this PC without a monitor I would suggest installing an SSH Server. These commands will be discussed later on in the guide.
sudo apt-get -y install openssh-server sudo service openssh-server start
The Raspberry Pi Foundation has put together a great guide in PDF format. Use NOOBS it will save you a lot of trouble. NB: Some SD cards don't support NOOBs but will work fine if the image is put on using a different method. Here is a great guide for setting up the Raspberry Pi SD card from Elinux.org. In fact it's a great place to start for anything RPi related. Raspberry Pi hub at Elinux. Once the SD card is setup you will need to insert it into the Raspberry Pi and boot. Install Raspbian from the NOOBs menu and wait. Follow this guide by Adafruit for first time setup. You will need to enable SSH Server. I suggest not starting the desktop on boot. It can be easily run from the command line by typing startx. Follow this guide by Adafruit to setup your network. Found here. No need to do this if you set up previously in the first time config. We will also at this point want to setup ssh. Again I will point you to an Adafruit guide. Once done exit back to a standard command line interface. This can be done in LXDE by using the power off menu located in the bottom right corner.
If you want to the Raspberry Pi or PC without a monitor go ahead and SSH into your device. So now you should be staring at a command line interface whether on the device with a monitor or via SSH. First things first lets make sure we are all up to date. This will update our package list from the repositories and upgrade them to the newest version. "-y" Will simply say yes to any prompts.
sudo apt-get update && sudo apt-get -y upgrade
We are going to need to install some useful tools. Git-core is how we will clone and download BFGMiner from GitHub and Screen allows multiple command line instances and means if we exit out of ssh session or quit Terminal on Ubuntu, BFGMiner will continue to run.
sudo apt-get install git-core screen
We also need to download some other tools/dependencies to ensure that BFGMiner will compile successfully.
Once the download has completed move into the bfgminer directory.
The following steps may take a while. Now run autogen.sh
You will need to make the configure script execuitable.
sudo chmod +x ./configure
Now configure bfgminer
sudo ./configure CFLAGS="-O3" --enable-scrypt
Now lets make!
sudo make install
One more thing...
If you haven't already plug in your ASIC. Just confirm your system is recognising the ASIC.
Its output should look similar to this (no need to type this in):
Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Yep there it is our ASIC listed as device 005. There is no need to install any drivers, unlike in windows, as they come in the kernel. Now lets actually start BFGMiner. You will want to start a screen session to ensure BFGMiner doesn't quite when you exit. "-S" is the option for starting a new screen session. You can replace "miner" with anything you like.
screen -S miner
Now you can run the commands below. Here is a sample of what you should type. You will need to replace somethings with your own values.
Where: URL:PORT is the address and port of the pool you wih to use. Now I won't suggest a pool. I will leave that decision up to you. If you do wish to mine DOGE take a look at this site for a list of pools and comparisons. USERNAME this is the username you use on the pool. Every pool is different. Check your pool's website for details. PASSWORD same as above. Specific to your pool, not every pool requires one. CHIPCOUNT this is specific to which ASIC you are using. For GAWMiner ASIC's:
War Machine: 256
Black Widow: 64
For ZeusMiner ASIC's:
Hurricane X2: 48
Hurricane X3: 64
Thunder X2: 96
Thunder X3: 128
Now to make sure you don't stop mining when you exit ssh or terminal. Press:
ctrl + a + d
To come back to the BFGMiner screen simply run:
screen -r miner
Start on Boot
First off you will want to make sure you have BFGMiner running correctly. Ensure you have the miners set up properly and your pool correctly configured. Start a BFGMiner instance, detailed above. Once the instance has started and you are happy with how everything is working press "s" on your keyboard to enter the settings menu. Now press the "w" key. Don't press enter. We want to specify where our config will go. Type:
Substitute USERNAME for your user. On a standard RPI install its pi. On ubuntu it's what you set during the instillation. Now press the enter key to return back to the main BFGMiner screen. Press "q" on your keyboard to exit BFGMiner. You should now be back in the command line. Now we want to edit a file called rc.local. Any commands in this file will be executed on boot.
sudo nano /etc/rc.local
Depending on your system this file may already contain some commands. Be careful not to delete them. After the last command and before "exit 0" type the following on one line:
Where USERNAME = your username Hit ctrl + x then y to save and exit nano. The above command will create a new screen session and run bfgminer using the config we created earlier. All while as our username so that we can easily reattach. Lets reboot to ensure it is working correctly:
Once rebooted and logged in, show all running screen sessions:
Reattach to the session. You only need to use the numbers before the first dot. e.g Mine looks like: 2480..hostname (13/07/14 12:02:09) (Detached). So I type:
screen -r 2480
Verify everything worked as expected. Then ctrl + a + d to exit. You have now setup BFGMiner to restart on reboot.
If you are using a Raspberry Pi and it loses power it will automatically reboot on receiving power again. For standard desktop PCs there is an option in some BIOS/UEFI to turn the computer on when it receives power. Consult your motherboard's manual and manufacturer's website.
Congrats you've done it. You have managed to successfully get your shiny new asic mining away. I do plan to make another guide detailing how to setup and use StarMiner a ready to go RPi mining distro. So I hope this is helpful for you guys. I have seen lots of posts asking the exact same questions again and again and I have tried to answer these as best I can. I am still learning about this stuff so if there is something I have missed or a mistake I have made please tell me. Anyway good luck. And I'll see you at the moon. Cheers Frogsiedoodle Edit 1: Layout and formatting. Edit 2: Added instructions for screen which I initially forgot. Edit 3: Removed 1 unneeded dependency Edit 4: Added section on start on reboot and power failure.
Ledger HW.1 review and guide for use w/Electrum development version.
I've been really interested in hardware solutions for private key storage. Without jumping in head first and going for the obvious choice I decided to try to least expensive option first: Ledgers HW.1. At the time or writing one can buy a HW.1 for 15€ or 0.0717 btc. Mine took about 2 weeks to arrive in a hand written envelope from France. Inside was a piece of paper wrapped around a card the exact same dimensions as a US drivers license/credit card. The HW.1 is to be snapped out and folded over as explained on the site. Here is a pic of the device "assembled" next to the card it was snapped out of and plugged into a usb port on a laptop for perspective.
Ledger seems to have some sort of partnership with GreenAddress, but I don't like having a third party involved in my transactions. Regardless how 'ungoxable' they are bitcoin to me is about taking back full control. Therefore I chose to figure out how to use the device with Electrum. There is no guide for this on their site as the process is not simple. However I was able to achieve it and I will share my experience. I would also like to mention here that this whole process took me about two days of sporadic work to accomplish and a few emails to support. I ended up emailing back and forth with Nicolas Bacca, Ledgers CTO. He was helpful and really quick to answer my questions. Overall my experience has been really positive and I can honestly recommend purchasing. I'm really excited to try out some other products from Ledger. The first step is installing electrum development version as described on their site. From a Debian distro I had problems with dependencies, but from a Debian/Ubuntu distro the process was near effortless. I won't go into details on how to install electrum as that is a guide in itself. Regardless which client you use with the HW.1 you will still need to install the drivers. What follows is a guide I've put together for the setup and use of the HW.1 with electrum development version on a Debian/Ubuntu os.
We'll start the electrum gui from the command line along with two options.
-v, --verbose - show debugging information -o, --offline - remain offline
Here's is what the full command will look like:
$ electrum -v -o
At which point the gui will open and present you with the entry panel.
We are now presented with the option to execute creation of a new seed or re-creation of a previous one. For this guide I will choose to create a 'New Wallet'. (Note: it would be really cool if someone could explain to me how to turn a 12 word mnemonic into a 128 bit hexidecimal string as would be inputted here).
The next screen, 2/3 in the creation steps, will have us choose a security profile (2fa or pin only) and a pin. Basically 'hardened' is 2fa with the second factor being a 4 digit pin and the transaction details that the HW.1 will print to a text editor (as you will see with the seed backup in upcoming steps). Of course we will choose 'Hardened' for the most fun... and security. Then choose a strong PIN.
Opening a text editor, placing the cursor on it, and plugging the HW.1 back in we get a printout in a few seconds in the following format.
We will remove 'Seed' from the beginning and 'X' from the end. What remains is our seed. We will save it in case of an issue with our HW.1 (lost, damaged, forgotten pin, etc.). Note: To restore from this Master Private Seed one needs to put 'xpriv' at the beginning of the seed for electrum to recognize it. Using the seed from above if, we didn't have our HW.1 we could input the following to regenerate our private keys:
After backing up our seed we can click the 'Next' button. Where we will be asked if we backed our seed up.
The wallet/device are now created and we have a backup (at least one). Now we can spend some coins. Let's open our wallet with the HW.1 plugged in. This time we'll add an option for our chosen wallet path and remove the option to remain offline.
We won't see these again if we keep our wallet file, or continuously use the default_wallet created by electrum when the -w option is not used. For now we will answer these questions the same as at the beginning. The next window will be how electrum will start from now on when this wallet is used with the HW.1.
Now we have electrum running normally. This is a good place to note that a 'watching-only' version of this wallet can be opened even without the presence of the HW.1. So you can retrieve addresses without the privkeys at any time. Funding addresses in normal, spending is a little different. We'll create the spend from the gui the standard way.
After careful reading we should have determined that we are to open a text editor and make it the active screen. Take out the HW.1 and put it back in. At this point the HW.1 will print into your text editor the details of your spend and your 2fa pin in the following format.
Powercycle then confirm transfer of x.xxxx BTC to 1xxbitcoinaddress fees x.xxxx BTC change x.xxxx BTC with PIN 1234
From this output we can see how many btc are being sent to which address. In this case there is no change. The PIN in this scenario is '1234'. This is what will be entered into the 2fa challenge. DO NOT CLICK 'OK' YET. After entering our PIN we have to remove the HW.1 and then put it back in before clicking 'OK'. After doing this we can click 'OK'. At which point we are presented with a familiar screen.
File > New > Hardware wallet. Both Trezor and btchip work as they do on OSX, apart from the Pi's slow CPU taking ages to generate the HD tree and Sync. Limitations At this stage a Pi is too slow to receive btchip's 2fa OTP confirmation code, with the auto-type saturating the text buffer. I'm confident Nicholas can fix this in firmware. Edit: an ipad2 + Apple CCK is too slow to buffer the seed about 1/4 times. Edit 2: an iPhone5/retina iPad mini + Lighning to USB camera cable works with btchip with iOS 8.1 with selected text editors. You can use btchipPersoWizard.py to restore a BIP39 mnemonic, however btchip's HW1 is unable to support on-device BIP39 seed+passphrase, but this feature might be added to the electrum plugin later. I don't know if greenaddress CRX will work on piper, there doesn't seem to be an official armhf build available from google, and the latest sudo apt-get install chromium version is v22 whereas Chrome is at v38. (it might be possible to download https://github.com/greenaddress/WalletCrx and pack/drag-drop the extension manually in developer mode)
I'm using the same formatting here as suggested by the Tek Syndicate forums. Thanks for the help guys, it is much needed! Intro
I don't know much about building computers, yet, so thanks for reading this. I need a computer that can push four monitors. I use Linux which complicates things. Choosing the graphics card seems to be the hardest part for me. I'd like to get a graphics card that is either supported on Linux by the manufacturer with proprietary drivers or one that is supported with open source drivers. Whichever is fine, I just want it to work. Eyefinity support would be great too, I have 3 1920x1200 monitors in portrait mode so I'd like to run them all as one display when I watch movies (this way I can watch 4K content).
Budget. How much are you willing to spend?
$750. Spending less would be nice. I will spend more than $750 if need be.
Where do you live (what country), and what currency do you use?
United States. I live in a big city so I also have plenty of physical stores near by (microcenter, best buy, etc.)
Is there a retailer you prefer?
Newegg/Amazon (I have free 2 day shipping on those sites). I will buy wherever is the cheapest though.
Do you need or already have peripherals? (this can add to costs)
I already have these items:
Three HP ZR24w 1920x1200 monitors
One Asus VH238H 1920x1080 monitor
External hard drive
USB 3.0 Hub
What will you be using your future computer for? Gaming? Rendering? Mix of both? Or is this a home media PC?
Web browsing, photoshop, watching video (not editing video), and programming. I don't game so I won't need as powerful of a computer. I really need something that can push all 4 monitors while Web browsing, photoshop, watching video, and programming at the same time.
Do you overclock or want to get into overclocking?
Overclocking isn't a priority for me. If the CPU and graphics cards can be overclocked then I will if cooling isn't a problem.
Do you plan on going for custom watercooling now, or in the future?
OS. Do you need a new one?
No. I use Ubuntu, Debian, and Arch. I will also be installing Windows 7 Home Premium with a license key I have.
Do you plan on mining bitcoin?
Yes! If cooling isn't a problem I certainly will be mining bitcoin or litecoin.
Do you render movies or photshop pictures?
I edit photos with GIMP but I may move to Abode Photoshop. I don't edit much video. If there are any parts that you must have, and you don't want to be swayed against, such as a particular graphics card cooler, or a certain SSD, case, etc., then please specify that.
I'd like to get a 128gb SSD. I don't need any additonal storage. I'd like to get 8gb of FAST ddr3 ram. 3 of my monitors have displayport which helps for picking a graphics card! I want the motherboard to have USB 3.0. Front or back ports is fine with me. I'd like to get a Fractal Design case. Cheaper black minimal cases work for me as well.
I have these parts from an old desktop I scrapped if they are useful:
Optical Drive: Lite-On LH-18A1P (I may not put this in the machine though so it if is not compatible that's fine.)
HDD: Seagate Barracuda 7200.10 320gb hard drive (if this isn't compatible that is okay too!)
Why is installing peercoin qt in linux live session so hard?
Hi, I'm trying to do a USB Live Session fresh install on my OSX comp, using ubuntu 12.04. I want to install the peercoin client offline to generate an offline wallet which can then be encrypted and moved to a USB key, and later imported to peercoin on my Mac when I want to spend the coins. My question is whether or not I have to connect to the Internet in the liveUSB to actually do this successfully? Because I'm having an amazing amount of trouble doing this (nights and nights of frustration) when I'm not connecting to the internet. In general I don't think that I'm technically disinclined, but this is absolutely stumped me. I'll outline my steps that I've done so far. 1- I've made the USB system and can boot no problem. I always choose to "test ubuntu without installing" since when I tried installing it wanted to overwrite my OSX 2- I unpack the tar.gz and I can't actually follow the install instructions coming with Peercoin (ppcoin-0.3.0-linux.tar.gz is the file I downloaded) below:
First, make sure that the required packages for Qt4 development of your distribution are installed, for Debian and Ubuntu these are: apt-get install qt4-qmake libqt4-dev build-essential libboost-dev libboost-system-dev \ libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev \ libssl-dev libdb4.8++-dev then execute the following: qmake make Alternatively, install Qt Creator and open the `bitcoin-qt.pro` file.
I cant install the required packages in order to unpack everything. All of the threads I read about detail steps AFTER installing, so it seems like I just am braindead and can't even get to the point others start to have difficulty. I also cannot install a QT creator, which the system suggests I try to do to create a graphical user interface. I've also followed the instructions here, as to how to install QT creator, but to absolutely no avail. The command line either says there is no file, or nothing happens. I followed the instructions here, as to how to unpack a file with a .bin extension but when I do that nothing happens either. I guess my question is, why is this so hard for me? Everything that I read suggest that the best kind of off-line wallet is done on a system that is never connected to the Internet. But if I can't install anything without connecting to the Internet, how can I get to the point where I can even generate a Wallet? This link on github suggests I should be connected to the internet Is anybody aware of an ultra descriptive linux/ubuntu 12.04 fresh install set of instructions? Something like this I think would be incredibly valuable to the community, and if I ever figure it out on my own, I will absolutely make it. I feel like this is limiting me from getting completely set up with peercoin. I can just generate private keys offline (I think, honestly I haven't tried running the html files I've downloaded because I'm fighting with ubuntu (bitaddress.org, brainwallet.org, etc)). But since I am using OS X, there doesn't appear for me to be any way to actually import a generated private key/address at this point into the OSX peercoin client to generate a new wallet. Is there? Any help is very very appreciated, thanks very much. Also, should I double post this at peercointalk.org? I'm more familiar with Reddit :) *edit 1 - fixed formatting
I have finally been able to create a secure wallet for myself. I used Electrum on a dedicated Debian installation running from USB, and I backed up the seed using symmetric GPG encryption. My question now is: How can I test it before I spend a couple of hundred Euro on bitcoins? Is there any way got bet a couple of cents in BTC so I can test my wallet?
2x SAPPHIRE 100355OCL Radeon HD 7850 2GB 256-bit GDDR5 PCI Express 3.0 x16 HDCP Ready CrossFireX Support Video Card
LG 24X DVD Burner
LOGISYS Computer CS368RB Red & Black Steel ATX Mid Tower Computer Case
CORSAIR CX Series CX750 750W ATX12V / EPS12V SLI Ready CrossFire Ready 80 PLUS BRONZE Certified Active PFC
Microsoft Windows 7 Professional 64-bit - OEM
Western Digital WD Blue WD5000AAKX 500GB 7200 RPM 16MB Cache SATA 6.0Gb/s
SOLD Both rigs runs Windows and comes with the installation disc (Dell branded), but I was running a live Debian-based OS from a USB drive that will be included (4gb). It supports litecoin and bitcoin, and even the USB ASIC block erupters. It has remote monitoring support, which is mainly why I used it. Will accept litecoin, bitcoin, Paypal, Dwolla, or Wells Fargo transfers. I would rather not ship outside the USA or part out. If no one is interested here, I will likely just list them on eBay.
Durch Bitcoins Mining können Sie Einheiten der virtuellen Bitcoin-Währung erhalten. Mit entsprechendem finanziellen Aufwand kann so jeder Computer-Besitzer nebenbei Geld verdienen. Wie das geht und was Sie dabei beachten sollten, erklären wir Ihnen in unserem Ratgeber. Install the binaries in /usr/local/bin directory $ sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-0.14.2/bin/* Run Bitcoin node By now we are going to run only Bitcoin node with no graphical interface: I create a new user to run the Bitcoin node $ sudo adduser bitcoin_user Then we log in with the new user $ sudo login bitcoin ... Debian 10 also comes with awesome new artworks. In this article, I am going to show you how to install Debian 10 Buster on your computer. Downloading Debian 10 ISO and Making Bootable USB Thumb Drive: Now, you have to download the Debian 10 ISO image and make a bootable USB thumb drive out of it. Install the cgminer inside debian and make it compatible with a asicminer. This is the best setup for a debian USB bitcoin miner. How to install Debian from USB. Close. 1. Posted by. u/how_to_bitcoin. 6 years ago. Archived. How to install Debian from USB . I installed Chrubuntu on the Acer C720. Now I want to try Debian. What steps do I start at to put Debian on here? Can I just Ctrl + Alt + => and go through the steps until I get to the protip, or do I need to repartition the drive back into the configuration that is ...
If you enjoyed this video, please click the like button, and share it on your favorite social networking platform (Facebook, Twitter, etc) ☁️ Get $100 in cre... In this videos, I am going to show how to install Linux without CD or USB. To install any type of Linux base OS, No need any USB, CD, DVD. Just use internal ... In this video we will create a bootable USB disk , but it can also be a bootable SD card if you have a device that can boot from SD .. This is for devices without a dvd or cd drive , and only have ... Detailed Debian 10 Linux installation guide, covering UEFI / BIOS setup, bootable DVD or USB flash drive preparation, the non-free image with proprietary dri... This is Part three of a 5-part series which takes you through the complete installation process of the Debian Linux operating system with full-disk encryption. We also place the boot partition on ...