HACKED!

So around January 11th, 2018 I visted my website and was presented with:
OH NO!

I then spent the next day Googling all sorts of things. Besides how to fix it, also why or how it happened.

I found out I’d have to register my site with Google and request a review once I resolved the problem. Through various links and searches, I found that a script was the culprit.

Logging in via FTP and looking around my shared hosting directories I found that this wasn’t just limited to my site, although this was the first site that I received this MALWARE error. PHP files had been updated to load this script with the visitor unaware it was even happening.

The other sites hadn’t been kept up to date and have since become abandoned by their owners for one reason or another. Some were just banner pages that simply pointed their visitors to Facebook or somewhere else. Others had fully blown installations with hopes of a bright future employing all sort of bells and whistles that third-party plugins provide, although left untouched with no updates applied.

So the sites that were beyond an easy quick fix, I simply deleted them. I put HTML Pages in their place. I decided I would only leave those installations that were being maintained on the server. Why have a full-blown CMS run a simple one-page site? The files that had been altered could have been anywhere and my goal was to repair mine and prevent it from just happening again.

So, the sites I myself maintain and monitor have been fixed, updated and protected. If yours was one of those that I replaced with simple HTML, now you know why.

iMessage solved and Jim finds joy with his Hackintosh

So there were a couple things tried to get iMessage working.  This post on tonymacx86.com is where I started.  I will admit, I didn’t follow the instructions completely.  I wanted to fill in the gaps that I didn’t have cause I have a working installation and just installed days worth of software so didn’t want to bork it all up for something I’ve been living without for years now.

But it was this post on reddit that clued me into an essential piece I was apparently missing.  “Board Serial Number” … I got that in there and iMessage now works a treat.  The original post covers this.  I just think the simplicity of the reddit post cleared things up for me.  It also has you delete all your old Messages – maybe they contain something that causes iMessage to regress?

That’s the thing about a Hackintosh.  If you buy the suggested hardware, it should “just work.”  When it doesn’t, there’s something you’re missing and you just don’t know what it is.  I mean if you’re not a systems engineer on Cupertino’s payroll that has all the answers.  And it can be very frustrating.

This brings us to Jim’s solution.  Seems the motherboard series he purchased required the installation of a particular Clover thingamahbob.  Once that was installed, “BOOM” as he said, everything started working.  After that solution, he moved on to his individual problems and fixed them one by one.

Again, if you’ve got the time and patience to work these things out.  Sometimes wait for answers.  It most definitely pays off in the end.

Verizon Sucks

verizonI see I have a lot of Verizon visitors and I figured I would express my displeasure with Verizon just for you. You should be flattered.

#1 reason why Verizon sucks?  I can’t send “verizon.net” people email from my mail server.  I spent an entire day trying to communicate this to Verizon support and I got absolutely nowhere.  The people with the accents kept asking for my Verizon email address or my DSL phone number no matter how many times I told them I wasn’t a Verizon customer.  I asked for the phone number for their NOC who handled their mail server.  Confusion.

Their web interface doesn’t work either.  I am not using my mail server to browse web sites and use their white-listing page.  My mail server is in a dark server room dutifully sending and receiving email 24 hours a day.  Fighting SPAM and Viruses and doing a damn good job of it, but Verizon won’t accept my email.  I receive the email from the nice web interface telling me that everything is okay, and when I reply to that email, my email is returned 7 days later never being able to make an SMTP connection with Verizon.Net’s servers.

I resorted to opening a ticket with my upstream provider, and they had no luck in helping me.  They suggested I reach out to Verizon customers and have them complain that they can’t receive email from me.  Can’t say as I know any Verizon.Net customers, nor could I email them asking them such a favor.  They were able to telnet to Verizon’s listed MX and issue simple telnet commands, so they assume that any of their IPs would be able to do the same.  Well I try from my mail server and other machines, and all I do is time out.  I just sent anther letter to my provider, but it’s Verizon that needs to provide me support.

Anyone from Verizon, please respond to this post and help me deliver mail to your customers from my customers.  Thanks.

#2 reason why Verizon sucks?  They advertise FIOS constantly on my TV, but it isn’t available in my area.  Comcast dominates the Philadelphia area and Verizon finally won against the powers that be to start installing FIOS in the Philadelphia area.  Where do they start?  In the suburbs.  If I could get FIOS to my location, my connection speed will increase 100 times and I will pay absolutely no more money per month for my connection.  That’s substantial for me.

I just got Comcast Internet installed at a new location and it blows away my high priced connection.  It is an eye opener, but Verizon has been teasing me for so long.  I need new copper run for my local loop, but an insider told me that they won’t run new copper, they want to install FIOS – well it’s not available in my area, and I have to deal with outages and bounces … That makes Verizon suck!

Bottom line, hey – Verizon, install me some FIOS and let me deliver email to your mail server, and we’re golden!  Thanks again …