A blog about tech, programming, security, and various other subjects.

Found 6 results for your search query or tag selection. Clear search.
IPv6 adoption  Tags: networking, my blog, my server.
IPv6 adoption is still rather slow. Some Dutch ISPs promised support during "early 2013". I'd say "early" has come and gone by now. They probably were planning for it, then saw the hype drop off after IPv6 day and rescheduled. Some announced to have delayed it, others never said it would happen. The only ISP that I know supporting a full and free IPv6 connection is XS4ALL. Heck, we get a /64 IPv6 subnet by default at no cost! That's more than twice the entire IPv4 space.
So I got hacked  Tags: security, my blog, my server.
I must say well done to Robbert Camps for hacking my website :)

Due to my inattentiveness when writing scripts in the randomprojects folder, I missed a leak which gave him access to my blog and read-only access to any file on the system.

Ironically I was watching the website statistics right the moment before he discovered the leak, and realized there was an issue with a file someone was browsing.
Certificate and private key file problems  Tags: my server.
For other Googlers who have problems enabling HTTPS on their Apache server (or any server I guess), this post.

I was getting this kind of errors:
[Sat Jun 16 01:07:57 2012] [error] Init: Unable to read server certificate from file /ohai/file.crt
[Sat Jun 16 01:07:57 2012] [error] SSL Library Error: 218529960 error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag
[Sat Jun 16 01:07:57 2012] [error] SSL Library Error: 218595386 error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested
hMailServer SSL setup, asio.ssl error  Tags: my server, software.
While setting up SSL on hMailServer, Mozilla Thunderbird was giving me errors when trying if it worked. The first time I forgot to forward my port (ups!). Second time it did ask me if I wanted to accept the certificate, but then it failed to send the e-mail, even before I had accepted the cert.

Looking in the log file of today, I saw the following error:
"TCPIP"	13312	"2012-02-05 14:12:29.652"	"TCPConnection - Posting AcceptEx on"

"TCPIP" 8304 "2012-02-05 14:12:30.057" "TCPConnection - SSL handshake with client failed.
Server uptime  Tags: my server, webhosting.
The past half year of school has mostly been about designing and implementing applications rather than actually building them. This also includes the SLA or Service Level Agreement, in which you should note what uptime a customer can expect. I saw a banner lately on a website which advertised the website's uptime. It said I could monitor my own website for free, which was of course a good marketing trick, but I could get a 12-day professional trial. And I must say, I do like it. The service is great and quite cheap too, it's just that I don't need it at all. (Actually, the name of the service is Site24x7).

But I let it monitor the uptime of my website for nearly two weeks. The final result: 99.96%. Not that bad if I do say so myself, even better than what most common webhosts offer!

Next page / Older posts

Circle on Google+
Follow at Twitter

AI apps chat computers databases datetime e-mail hardware keyboard keyboards lol me music my blog my server networking nostalgia other privacy programming randomthought real life school security social networks software spam tutorials webdevelopment webhosting websites Windows writing
Contact Me (test)