AmateurRadio.com

A good day today. Not much operating as I had to install a new PC monitor here in the shack and then a new Freetime Freesat receiver down in the living room. It’s one of the new ones with WiFi support so I don’t need to run a network cable down to the living room which all existing boxes have required.

After that I came up to the shack to see if I had installed any new QRM generators. Switched to 10m PSK31 and heard a single solitary station – TO7BC  from Mayotte!

I’m not a DXer but this signal on its own in the clear was too much to resist. It took about 15 minutes to break the pileup. I couldn’t hear any other callers so I used XIT to dial in 0.5kHz up and hoped for the best. After a while with no success I decided to go up another 100Hz and he came right back! I must have been the only station who received a 579 report.

I shall check the website later to see if I got in the log. I will also have to find out where Mayotte Island is! I don’t often get to work DXpedition stations so I’m quite pleased with this afternoon’s work. I’ll check for QRM generators another time.

It was inevitable this would happen: someone has started a Yahoo! group for the JT9 mode. Pity they couldn’t have made it a Google group like the one for JT65A but I guess more hams have Yahoo! accounts than Google accounts.

There was already a fairly quiet WSJT group but this will keep the discussions about using JT9 on HF separate from the rather esoteric MS and EME stuff.

I only managed 4 QSOs in abour as many hours using JT9-1 this morning. I worked LU8EX whom I recognized having made a JT65A contact with him in the past. Hopefully more operators will make the switch from JT65A to JT9-1. At the moment it feels like I’ve worked everybody. I was spotted many times by VK3AMA even when I was running 5 watts. Pity there is no-one else in Oz using the mode yet.

I switched to PSK31 in the afternoon and my QSO rate immediately improved. A nice catch was Luc PR8EP whose QSL card I picture here.

Another good one was Eric HS0ZJK in Phetchaburi, Thailand. He is only the second Thai station I have worked, and both were on 15m.

Happy April Fool’s Day!

I see that some bloggers have complained that HF propagation today was not too good. My 5W JT9-1 signal on 20m was spotted several times at reasonable strength by VK3AMA so this afternoon I thought I would see how far I could get with 1 watt.

Reception of JT9-1 signal from G4ILO using 1W to attic dipole

If you get the impression that I’m keen on K1JT’s new JT9-1 mode, you’d be right. This morning my signal (25W to an attic dipole) was spotted by Laurie VK3AKA in Australia – the longest distance I’ve been received using JT9-1 yet. A QSO must surely follow.

My signals down under were -18dB. Yes, it seems Laurie is testing some new add-on for WSJT-X that spots to Hamspots with additional info. Exciting stuff! JT9-1 is turning out to be the WSPR QSO mode that many hoped for.

This is not much to do with radio. But I know that many of you have your own websites and will probably find this of interest.

A couple of days ago I discovered that one of my websites had been hacked. Not G4ILO’s Shack, but the other one which still continues to earn us a little bit despite receiving only the barest maintenence in the last two years.

I opened one of the pages and instead of the expected content a server error message appeared. My first thought was that the hosting company had changed some setting so I fired off an urgent support ticket. They responded saying that some of my files had been “compromised”. Sure enough when I looked at one of the files there was some code I didn’t recognize. This code referred to a file that had been added which was zero length, and that was causing a 500 server error. I deleted the file and every access now caused a 404 “file not found” error. Eventually I found that the .htaccess file had been hacked and some code added which was being executed for every single file access.

The timestamp showed that the .htaccess had been modified a week ago on 19th March. Because of the web browser caching we had not noticed the error messages any earlier. Google had visited the site in that time however, and had received a server error for every page it tried to access. So now the site had dropped out of Google. Thanks a lot, hackers.

Further investigation revealed that the hackers had modified almost every .php file on the server. They had inserted some code at the beginning of every file, apparently meant to disable error reporting. They had inserted some other code into one .php file that was included in every page. However, something in what they had done had the effect of disabling PHP processing with the result that the PHP code was sent to the browser instead of being executed.

To cut a long story short, after trying to repair the hacked files individually, I decided to restore the site from the oldest backup the hosting company held. I had a little bit of luck: the oldest backup was taken on 19th March, the day of the attack, but it had run before the attack occurred so I was able to restore the site with every file as it was originally. A day later and that backup would have gone and I would have been unable to restore the site without a lot of manual work. But the damage had been done as far as Google was concerned.

If you are expecting a lesson to be learned as a result of this story, I don’t have one, other than if you want a quiet life stick to blogging, don’t try to run your own website. If you do, visit your site every day and check for changes.

I have no idea how the hacker managed to gain access to the files on my shared web server. If they did it once they could do it again. I don’t believe that my passwords were compromised as they are randomly-generated, but I changed them anyway. Altogether this episode lasted for several stressful hours – time that I would much rather have spent trying out the latest WSJT-X program.