Reddit is a good place to share content, but also a good place to attempt to make some money
on clicks from unsuspecting or indifferent users. Lately I've been seeing a pattern regarding
videos stolen from other YouTube channels, reuploaded and monetized with ads. These videos are
then mass posted on Reddit by bots masquerading as real users.
tl;dr: Spambots are posting links to stolen videos on Reddit, copying comments from others
to masquerade as legitimate users.
In my last post I wrote about StartCom's new StartEncrypt service and its misleading advertisement email. In it I mentioned that they were not using the ACME protocol that Let's Encrypt is using, but their own StartAPI protocol, for which documentation is behind a login. Their client was also not open source.
It didn't take long for the first security issues to be found. Computest found multiple vulnerabilities in the StartEncrypt API and client, the most critical of which allowed the user to fetch certificates for domains outside their control. Domains like google.com, facebook.com etc. The following quotes speak volumes about the security of StartEncrypt:
A malicious client can specify a path to any file on the server for which a certificate is requested. This means that, for example, anyone can obtain a certificate for sites like dropbox.com and github.com where users can upload their own files.
[...]
The client doesn’t check the server’s certificate for validity when connecting to the API, which is pretty ironic for an SSL tool.
As Computest points out, when a certificate authority publishes a service which such problems, they are undermining the thing they are paid for – the trustworthiness of their certificates. Personally, after the latest events with StartEncrypt, I would no longer recommend StartCom to anyone, for neither paid nor free certificates.
Before Let's Encrypt existed, I – like many others – used to use StartSSL, which offered free domain validated TLS sertificates. It was a useful service, but not without its flaws, for example the user interface was very clumsy to use. When Let's Encrypt arrived, the automation made me jump ship immediately. But a couple of days ago I got an email from StartCom, the company behind StartSSL, that piqued my interest.
This is a project that I've been working on for a month or so on my free time (of which there really isn't too much). I started it on my company's 12 hour hackfest, where I didn't get anything worth showing done (it was all backend stuff), but now it's ready to be published. *drumroll* So, it's time for the reveal:
Honestly, some days it feels like web development is the art of building a self-aware network of node.js packages that sort of
does what you need it to do… until someone on the other side of the planet inserts a breaking change in a patch version and
the abomination you have created decides to set your house on fire instead.
NOTE 2016-09-21: It seems whatsapp-purple has been abandoned by its maintainer. So the things in this guide may stop working over time, and your mileage may vary. This guide is left here for posterity.
Perceptive readers may know that I use a Jolla as my phone. This places quite a few restrictions on what programs can be used on it. For WhatsApp I used to use a native application called Mitäkuuluu by coderus. Unfortunately at some point the program was discontinued, the official Android® version did not run well on the phone and the whole thing was a hassle. So I searched for an alternative way of using WhatsApp, since it has some people I would have trouble contacting otherwise. Since my IRC client is always running (on my server) and is something I check often, I looked into what BitlBee had to offer. I got a setup working and decided to document it for others.
Let's Encrypt is the new free, automated and open certificate authority, that
I talked about in a previous post. The part that I'm focusing on in this post is
automated. Let's Encrypt is all about automating the certificate request and renewal process, and they encourage this
to the users by offering a good client – and by only giving out certificates with a maximum of a 3 month validity.
I'm not good at remembering things months down the line, especially if I have to deal with multiple different
subdomains. That's why I wanted to automate my certificate renewal process.