Moving to Cloudflare

I moved this site over to Cloudflare.

The previous CDN doesn’t give SSL to free accounts.  I’ve wanted to get SSL on here for many reasons, such as using SSL to  protect my logins.  Additionally the use of SSL is necessary for the SPDY protocol, which should speed up the site.    I”m expecting Cloudflare to migrate to HTTP/2 as that becomes the new standard.   Google reportedly also gives a tiny page ranking boost to encourage the adoption of SSL.

I also like that using Cloudflare means I can have DNSSec (which I haven’t turned on yet).   By hosting my DNS with Cloudflare, I no longer need to pay for a Dyn account as was necessary with the last CDN I was using.  (due to the way my webhost does DNS).

If you notice anything not working let me know in the comments.

Bitlocker encryption bypass

Management types are always trying to push BitLocker rather than third party encryption because its free.   “Free” as in, “included in Windows Professional/Enterprise”.   They never consider the less obvious costs in usability and to the helpdesk.  The Windows guys would even team up with the management types complaining that non-Microsoft full disk encryption products made system deployment difficult.   (There are of course ways to work with things like MDT in McAfee encryption.   I don’t know about the other versions.)

For me it always came down to two main things.

  1.  It’s not acceptable security to me to use Bitlocker without pre-boot authentication.
  2. Using Bitlocker with pre-boot authentication is kind of annoying.

a. Bitlocker preboot authentication requires a per machine password.  Users would need to know this additional password rather than the single signon used by non-Microsoft alternatives.

b.  The password recovery options available are kind of cumbersome.

This month, Microsoft released security bulletin MS15-122 to patch a vulnerability in Bitlocker when used without pre-boot authentication.  This attack involves spoofing a domain controller.


LinkedIn Spearphishing

Dell Secureworks has identified targeted attacks occurring through LinkedIn.

In this attack, a fake user with a network of connections is created.   Under the guise of a recruiter, they contact targets of opportunity, think sysadmins at a target company.   The victim is enticed to go to a purported resume submission website.  And then you have malware.

  • As always, on LinkedIn be aware that people may not be who they claim to be.
  • If you are going to apply for a job, go the known, established website of a company, and click on something like “Careers” to find a link to their jobsite.   Where it’s an external recruiter contacting you, take care in establishing their bona fides.
  • Dont be part of the problem.  Only accept connections from people you know and trust.   Your connection is an implicit endorsement to other people.



LogMeIn Buys LastPass

I was just recommending LastPass on a corporate Chatter.  Then I read that LogMeIn has bought LastPass.

LogMeIn isn’t one of my favorite companies IIRC it is quite impossible to block LogMeIn’s enterprise security circumventing product without blocking remote support sessions also.  This is becuase they use the same servers for each.  GoToMyPC on the other hand provided a ways specifically to block its use in an enterprise, and kept their gotoassist/gotomypc servers separate.  This was a few years ago so perhaps things have changed.

Since that time LogMeIn annoyed people by doing away with their free product (making my need to block it much less).   And also engaged in rampant price hikes for those foolish enough to pay for the service.

Even if none of the above were true, our passwords make a huge target.   LastPass was believed to be a security company who realized they’d lose everything if they failed to protect our encrypted passwords.   Even then twice now we’ve all had to change our master password out of an abundance of caution.    Now they’re being bought by a company that doesn’t seem to have the same drive for security.

It is very disappointing.

FBI Investigates the Cardinals

The FBI is investigating the St Louis Cardinals for a hack of the Houston Astros.

The Cardinals reviewed a “master list of passwords” to access the Houston prospect database.   A former employee of the Cardinals now worked for Houston in setting up this system.  The FBI tracked the unauthorized login to the home of Cardinals team officials.

source – NY Times.  (if the link is paywalled, do a search on google to find the article or add a google refer to your request.)

This illustrates why password reuse is a problem.  Additionally if passwords were routinely changed, even with an admin using the same password initially,  they would be forced to change it to something else.  One does wonder about this “master list of passwords”.   I’m guessing these were service or admin account passwords rather than the organization knowing individual user passwords.  At least I hope so.

You wouldn’t grow your own electricity

I’m going through RackSpace’s free CloudU training.

They use the analogy of infrastructure a couple of times.

  It would be bizarre, given widespread availability of electricity on tap, that an organization would create their own electricity plant to power their factory, so too is it becoming more bizarre to host one’s own software or buy one’s own hardware.

It sounds great.  I suppose we shouldn’t look at it too much though.

What business of any size doesn’t have battery backups on the data center and network gear?  Who doesn’t have a generator to keep the servers running if the outage is more than a flicker?

How many data centers have the windfarm and solar panels storing energy in batteries for use later?

Its rare but people do go off grid (on homes, not data centers as far as I know).  The Telsa battery announcement may make this even more common.

Why would they choose to undertake this capital expense?

Infrastructure may free you to focus on your prime business, but it also makes you dependent.   I’m not arguing against the cloud, I just was thinking about whether their analogy is breaking apart already as battery and green technology improve.

Setting up RT-AC68P for Tunnelbroker

In the past, I had a iPad Mini through work.  It was on Verizon, and I could tether to it to get and IPv6 address when I wanted to test.    I can’t really justify the monthly data plan cost, and the upfront hardware cost to get that on my own.  So I finally set out to set up tunnelbroker from Hurricane Electric to proxy IPv6 traffic over IPv4.   This task was made easier by having a newer router/accesspoint from ASUS, the RT-AC68P.

I found a number of setup examples on the internet, the best for me was a thread on the Hurricane Electric forum.

The one issue I had following these instructions is adding tunnelbroker to dnsomatic.

The hostname should be the fqdn assigned by hurricane electric and they now use an update password (on the advanced tab) rather than the password to log into tunnelbroker.

Other than that, piece of cake.

The ASUS RT-AC68P contains an IPv6 firewall for unsolicited inbound traffic so make sure that is enabled.


Not a Phish this time

Last week, I needed to ask my mortgage company a question.   They responded with a Cisco Secure Mail message.  This meant I had to create a Cisco account.  Set up password reset questions.  And eventually I was able to see the message ”

Thank you for your request. We are reviewing your information and will respond as quickly as possible. If we have any questions, we will contact you.

That was a lot of security for a message that essentially says “your call is very important to us, please stay on the line and your call will be answered in the order it was received”.

Additionally, they sent a letter to my home with the same information.

Today, I received an email with subject Regarding Loan Number 325,632,897 (not the actual numbers).  There was nothing in the body of the message.  I did not recognize the sender domain.  There was a PDF attachment.

Other than Gmail allowing it to my inbox, there was every indication this was spam.

I checked out the headers and saw it passed SPF and had a dkim signature.  Turns out the domain is for a company that does technology for mortgage companies.   The file passed virustotal.  It turned out it was a reply from the mortgage company.

Kind of funny that when saying nothing at all, they make me jump through the hoops of Cisco secure mail.   But when sending an actual response it looks like phishing.