Topic: The KRACK Wi-Fi attack...precautions? - page 2. (Read 2176 times)

Crypto isn’t the only thing that these types of hackers are after/give value to. I would think every password, sensitive financial information (SSN, account number etc.), and credit card number has some amount of value, especially if it was obtained in a non-mass hack way (as passwords stolen via the yahoo hack for example are known to be compromised and other business know to either force a reset or use extra caution when accepting said passwords).

If you live in that densely populated area then you will want to use a VPN to connect to any website you need to login to if you are using WiFi.

The primary risk to crypto users is MITM attacks when depositing crypto (and to a lesser extent withdrawing crypto- many businesses use certain precautions that make these attacks more difficult). Assuming you aren’t using a web wallet, your private keys are safe and any transaction you sign can’t be changed (although you can be tricked into sending to an incorrect address), and unconfirmed transactions are no longer safe to accept due to the fee market, and faking a block would be very expensive and would not be guaranteed to work.

That depends where you live and how committed the attackers are- if they can narrow you down, they will. For example, here in NYC- I can probably see 50, 60 home wifi networks from desk in my home office (I live in a big building but not that high up)- that get's worse as I walk around, and there are known areas where people are more likely to be in the Crypto scene. A VPN is definitely a pre-req (generally in life IMO, but people don't like losing speed)- another alternative is put your wallets in an encrypted VM (encrypt the disk, and encrypt booting it up), have that always spin up a VPN on network connect, that allows a lot of separation, encryption and traffic obsfucation so they can't see random DNS queries going to places like 'bitcointalk.org' and know you're into Crypto thus making you a more interesting target.

I think this would be more of an attack done by location, verses by specific person.

The complexity of the attack makes it unlikely that a single person would potentially allow someone to steal enough for them alone to be targeted. So I would anticipate an attacker use a more public location in which many people could get attacked in a short period of time.

Using a VPN would solve being subject to this attack provided you configure your computer to not connect to the internet outside of the VPN. Although this may subject you to other issues/attacks.

Microsoft already pushed a patch to protect it's users, so you should just do the latest updates if you have set it to manual

updates. I also heard that some routers will need a firmware update to path this exploit and Linux users are the most

vulnerable. I use Tails for most of my Bitcoin stuff, so I will have to look into that. 

You dont have to worry about the Key Reinstallation AttaCK (KRACK).
This vulnerability gives attacker the possibility of reusing keys gathered in Handshake. This can be used to decrypt WiFi Traffic. This is not an exploit which allows to compromise a Network. There is no was of finding Out the WLan passwords or whatever.
Traffic should be encrypted with TLS (https) to not b vulnerable to an focused attack.
In Addition to that your priv key does never leave your PC. Only your Transaction will be broadcasted.
If you want to make sure noone recognizes your transaction you should always Connect via https to Push tx's.

For full nodes, the only reason you would be concerned about this attack is its ability for the attacker to isolate you from the rest of the network. With the MITM attack, they can control who you can connect to and might connect you to a network that is separate from the actual Bitcoin network. The transaction's existence and confirmation can be faked.

For SPV nodes, the problem with it is that it doesn't verify the network rules. Due to that, anyone can broadcast blocks to your client and your client would accept it as long as it is the longest chain difficultywise.

For exchanges and Bitcoin services, as long as they use HTTPS, there is no cause for concern.

All in all, the attack does not really affect Bitcoin that much, given the difficulty of exploiting the exploit.

It's possible to do that manually: disconnect from the internet, sign transaction, connect to the internet, push transaction. But maybe I'm missing something here. I prefer the offline signing method: Store your wallet on an air-gapped machine (does not network at all, no internet). Generate the wallet in an offline environment. Sign transactions in the offline environment, then transfer them via USB flash drive or other medium to an online computer. Push the transactions from there. Rinse and repeat.

The downside is that you can't automatically sync the wallet. You can transfer block data the same way you transfer transactions out. Or you can have a watch-only wallet on the online PC for the offline wallet, to know exactly the amounts of the UTXOs, to manually manipulate future transactions.

I guess this will.help

And don't use WPA either. There's a reason why it was replaced by WPA2. You don't really need to use a wired connection because if you're using a PC, it's highly likely your operating system already has a patch out for it. The first thing you should do is search for updates and install them. Client side patches are effective enough. You only really need to worry if you're using an old-ish Android device which doesn't get updates anymore. Don't use those for Bitcoin transactions unless you take proper precautions, such as a VPN.

Do not use WEP. WEP has been known to be insecure since more than a decade. Unfortunately WPA2 is so far the best we got. Use wire, if you must, but don't use WEP.

I don't know about iOS but this probably will apply there as well.
On Android, for the time being and until your vendor/google do not release decent patches, USE mobile data via VPN when you need to use your bitcoin wallet there. Do not use wi-fi as we speak until you are certain of receiving a patch.

For your everyday browsing life, as others have said, turn HTTPS EVERYWHERE on, block third-party cookies, remove sending referrer info and if that's not enough use NoScript. Or turn to TOR Bundle which has everyhting built-in or get a good VPN.
I personally use Avira Phantom Pro

It is things like this, that will increase the paranoia of users, not to use Crypto currencies. Yes, you might have control over your private key, but do you have full control over the data that are transferred when you use third party services to move those coins. Most people use third party services over Wi-Fi connections to manage and use their coins. The Man-in-the-middle attack, will always be a risk factor and this bothers the online banking and other financial sectors too.

We need methods to transfer coins in a offline environment, that can be updated once you go online again. While you access those coins or sweep those private keys, you should not be connected to the internet. < most likely impossible, but it would be the perfect solution >

OP, if you are really that paranoid, turn off your wifi card in your PC and connect to the internet through a wired, ethernet connection.

But from what I have read, Krack exploits the vulnerability in WPA2 wifi standard. I assume other protocols and encryption are safe, so it might be best to start using WEP instead.

Basically this. If you want extra precautions, though, you have extra options. The most obvious one would be to update your device. Windows, several Linux flavors, and macOS have already released patches. I have no idea about iOS, but Android would be a little tricky because of patchy updates. Do not rely on router firmware updates, as it could still leave unpatched devices vulnerable. Next, you should look into VPNs. Free ones are generally hit or miss, and paid ones are cheap. As for your regular browsing, https sites should be safe from eavesdropping, but you could look into installing the Https Everywhere add-on to force https connections when available.

You should also take note that potential hackers cannot exploit this remotely. They will need to be within range of your wireless network, but they could break in without knowing your SSID password through MAC spoofing. If your wireless network is accessible to lots of other people, make sure you take steps to secure yourself as soon as possible.

yup, correct.
It becomes a discussion of trust (again).
Cloudflare is MITM. And yet they are here to protect websites (e.g. prevent DOS, and similiar).
I wanted to stay in the scope of the KRACK WiFi attack, so this would happen in your home environment or e.g. in public hotspots.

IMHO security is always a trade off - like how much do you need to invest to protect.
Small values (e.g. less than 100 Euros): you are ok with today's technology.
Values below 1000 Euros need some thoughts, and values above need proper investments in security (and even consulting, if unknown to you). There you want to talk about proper cold storage, but this exceeds certainly the scope of the discussion here - in this forum there are already exising threads.

Just wondering what is best answer to OP: KRACK and Bitcoin. For little values, I don't see immedeate action, as it requires high efforts to gain access.

When using a wallet (on desktop and iPhone), it's anyhow ok to use the wallet software. When using wallet via service provier or when doing trades, make sure Operating system is up to date, look for latest patches that include fix for this KRACK.

comments?

None of which is an issue if the site is correctly configured. Heartbleed is not an issue anymore if your server is even remotely up to date. SSL downgrade attacks are defused by simply not allowing deprecated SSL connections. Modern browsers immediately scream in your face if there's even something remotely fishy with the SSL certificate of a visited site.

If you're paranoid, run an SSL check of the exchange or online wallet of your choice:
https://www.ssllabs.com/ssltest/

You'll get a wonderful summary of which potential MitM attack vectors are still open. You'll see that Blockchain.info for example doesn't even allow SSLv3 connections anymore, which lies at the heart of downgrade attacks. Of course there's always a chance of 0-days, but that's a different issue.

If you want to feed your paranoia, think about how many crypto related sides use Cloudflare. There's your MitM right there in plain sight. Look up Cloudbleed for extra fun. Cloudflare offers an incredible service and handled Cloudbleed fairly well. But if you just focus on your front door, you might forget that you left the back door wide open.

no, not really. In the past we have seen "heartbleed", and today tools like SSLstrip and MITMf allow to bypass SSL, by "downgrading" a connection to a standard HTTP session, then injecting JAVASCRIPT code etc ... and who is looking "all the time" to the green escrow in the top line of the browser?
I would like to add, that this is already a very sophisticated approach to hijack a connection. It certainly depends on "your value", if someone is ready to play with it. If you have less than 10 bitcoins, I'd be not in fear. But if you are "rich" and paranoid ...

Man-in-the-middle attacks are not necessarily a risk, given that the exchange or online wallet is using a properly configured SSL / HTTPS connection -- which should be the common case nowadays -- and you, the user, watch out for SSL certificate warnings and make sure that your browser is highlighting the connection as secure. So short of badly configured servers and yet-to-be-found security bugs your SSL / HTTPS connections should be somewhat safe from man-in-the-middle-attacks -- that's what SSL / HTTPS is for.

based on the document here, it mainly drills down to update client software, and also the routers.
The traffic can be intercepted, and code could be injected.

Now to bitcoin: I have four use cases in mind, I describe below. Perhaps this can be worked out more and more by the audience :-)

using a full node:
===========
you can download up to latest block, "stay" offline, craft the tx, and sign it. Only when sending it, you can go online. If someone messes with your tx, then the signature and hashes will be invalid, and it will simply not be accepted by the network.

using an SPV wallet:
=============
It is difficult to create a tx offline. So you have to be online. I don't see, that electrum wallet would be affected, you'd have to inject code in the communication channel, to fetch tx and build them up locally. Don't know, which attack vector exists, to get "down" to the priv keys. Hoping to get more info from SPV wallet providers (same accounts for Bread and AirBitz).

using an online wallet:
==============
Here is a risk, i.e. if the software is just a "html" based wallet. Code could be injected. Any attack vector through "man-in-the-middle" is thinkable 

online trading:
=========
same as online wallets.

If you are paranoid, connect your PC with Ethernet cable to your router.

Can anyone weigh in on the security implications of the recently disclosed KRACK attack for Bitcoin wallet usage on PCs that connect via Wi-fi? My initial reaction is that nothing is pushed until broadcasting the signed transaction, so nothing of concern should be exposed to a potential attacker.

But I'm a complete layman here, so I'd love for someone with more expertise to opine. I'm getting so paranoid that I'm tempted to stick to using an air-gapped PC to sign all transactions, then pushing them from a connected computer. Or I guess I could dig out the old ethernet cables...