|
May 25, 2017, 04:25:01 PM |
|
For that matter I haven't seen any wallets that work on 32-bit systems period, other than Bitcoin Core "supposedly"... I put that word in quotes because upon actually trying it it gave me an error message trying to install it. The reason could be because I don't have .NET Framework installed on that box, and Bitcoin Core requires it? Perhaps all wallets require it, as it appears no wallet will work on any version of Windows after XP, and every version since XP has .NET Framework packaged in with the OS itself.
And before you get sidetracked, disregard any real answer and instead spout off about how one shouldn't use XP to begin with because it doesn't get any updates anymore and is unsafe, allow me a pre-emptive disclaimer: You actually can get updates for XP through at least 2021 via a tweak known as the "POS Ready Tweak". POS Ready was an OS created solely for Enterprise purposes... big businesses that for whatever reason couldn't or just wouldn't update their networks in time for the EOL. It didn't get a lot of press for obvious reasons and wasn't available to the general public, until later on it came on some mobile devices. All it is is essentially an XP Pro SP4, and it's EOL is 2021. And we know EOL's almost always get pushed back at least 1 year, so I'd say April of 2022 is a likely EOL. You can use a simple registry tweak on XP Pro to get updates until then. Not to mention on XP you can really tweak and trim the OS to pretty much eliminate any semblance of attack surface... by disabling services, deleting and tweaking things, and on the Pro version utilize things like Local & Group Policy tweaks to create whitelisting rules, halting things like CryptoLocker dead in it's tracks. Folder permissions + LUA. You can make it so that every port is closed without using any 3'rd party software, not even a router or the integrated Windows FW. And all but immune to any type of exploit without even using DEP, not that that's possible because it's built into the CPU. Once you add some 3'rd party software into the mix, and utilize it properly, like a software FW, HIPS (like Comodo FW with Defense+) with tight rule sets and a whitelisting approach for the HIPS, Sandboxie, with sandboxes for anything facing the internet, Malwarebytes Anti-Exploit, TrueCrypt, a VM, Macrium Reflect for backups. Create isolation by creating partitions for many individual things, like the OS of course isolated, browser, temp folders. Anything new introduced to the box via download, USB port, or removable drive is sandboxed in it's own dedicated partition, scanned with VT Hash Check, MBAM, Hitman Pro or TDSS Killer before getting moved where it belongs. You don't even need to use a real-time AV. Certain things in TrueCrypt encrypted containers, VPN's, TOR on an encrypted USB stick. With all this, whitelisting, hosts/block lists... allowing only what is absolutely needed for everything on your box to work properly, from apps to websites. Well, you get the gist.
IMO it can be made to be the most secure/private OS there is all things considered, though it certainly doesn't come out of the box that way. Every Windows OS since leaks telemetry like a bad faucet, and you don't have to rely on security by obscurity because there's a lack of good 3'rd party support as with alternate OS's. You can get the best of both worlds. But I despise .NET Framework... it is major bloat and also vulnerable attack surface. I have other setups but I like this one the best and wish there were a good wallet for it too. Is Paper Wallet the only choice? Does every wallet require .NET FW?... even if there were one to work on XP would installing that be a neccessity?
How about hardware wallets? Would any of them work with XP Pro SP3?
I'm open to suggestions. Right now I don't own much BTC and what I do have is online, but I don't want that to stay the case as I've become a vendor on a deep web site and expect to be bringing in more BTC in the near future, and I don't trust having it online. I'd prefer a hardware wallet to all of them, but don't know if it's possible with this setup.
I'd greatly appreciate any suggestions...
|