If you’re trying to calculate a bitmask and your binary is a little rusty, use the Windows Calculator to flip the correct bits.
First open the Calculator and select Programmer Mode. If you’re using Windows 10, select "Bit toggling keypad":
After repeatedly working on a file, hitting save, attaching the file to an email, and realizing I sent the unsaved version of the file; I decided to dig into this odd behavior of Microsoft Word 2013.
My initial workaround was completely closing all Word windows, but I didn’t want to have to close all of my documents to save one.
After a little more digging a simple setting solves this problem. Go to File -> Options -> Advanced. Scroll down to Save and uncheck "Allow background saves".
I had an old hard drive I wanted to use as a secure, cross platform file transfer device, so I thought of TrueCrypt and UDF. Unfortunately, TrueCrypt for MacOS only supports formatting drives as Mac OS Extended and TrueCrypt for Windows only supports NTFS and FAT32. I ended up using TrueCrypt for Mac OS and the Mac’s command line formatting utility.
sudo newfs_udf /dev/disk3to format the TrueCrypt volume with the UDF filesystem
The other day, I was trying to update the driver for my EVGA GeForce GTX460 Video Card, but the download kept stopping at 180MB out of 271MB. After re-starting the download a few times, realized that my ISP or firewall was flagging something malicious and interrupting the download. I figured I had 4 options:
Assuming it worked, I figured option 4 would be the easiest. The default download link too me to
http://us.download.nvidia.com/Windows.... By changing the link to
https://us.download.nvidia.com/Windows..., I received a certificate mismatch message, but the download worked when I overrode the warning. A closer look at the warning, shows the https certificate is for the domain name
a248.e.akamai.net. This seems safe to me, since Akamai is a CDN, so it makes sense that NVIDIA could be using Akamai to distribute their drivers. I would be more cautious if the certificate was not issued to a CDN or NVIDIA itself. Remember to check that the installer was signed by the appropriate company (NVIDIA in this case).
I haven’t tried this on other downloads, but I think it should work on a fair percentage of them.
I’ve been a long time Google Chrome user, but Chrome’s lack of certificate revocation checking persuaded me to switch to Firefox as my secure browser. I’ve relegated Chrome to being my media browser to take advantage of it’s built in and automatically updated Flash player.
After a few days back on Firefox, I’m happy with the switch. Firefox’s certificate revocation checking seems to be faster than Chrome’s (completely subjective) and Firefox’s security is much easier to customize.
under Settings → Add-Ons, I added:
I also installed HTTPS Everywhere. It seems to be more mature and easier to manage than the Chrome version, with the exception of adding custom rules. Custom rules must be added to a folder in the filesystem and cannot be edited from within Firefox.
Under Settings → Add-Ons → Plugins
I set all of my media plugins like Google Talk and Microsoft Silverlight to "Ask to Activate".
I set to Java (it got installed when I was doing some Java development) to "Never Activate".
Under Advanced → Data Choices, I disabled Firefox Health Report and Crash Reporter, because these could inadvertently disclose sensitive information.
Under Advanced → Certificates, click the Validation button and check "When an OCSP server connection fails, treat the certificate as invalid".
Type "about:config" into the address bar.
These configurations give you good control over what runs on each page through NoScript and Ask to Activate.
The most sites use RSA or ECDSA certificates and support AES. I generally find that sites that don’t support AES, only support RC4, so disabling Tripple DES doesn’t reduce compatibility. I use CipherFox to enable RC4 on an as-needed basis, because some sites that support AES, prioritize RC4 (e.g. BarclayCard). Due to Dreamhost’s server configuration, this site only supports RC4.
At this point, I rarely encounter a site that does not support at least TLSv1.0, so I figure it’s time to disable SSLv3.0.