Time to start getting hands dirty with code again

Hello

Hopefully everyone had a nice holidays?
Well, it's new year and time to go to next version with CD.

Here's my initial plans what is going for CyberDragon 1.6.1 version:

1)
Linux version. I have now another laptop with Linux installed and have
started porting CyberDragon for it.

I expect it to be mostly trivial with very little changes to code and maybe
even better working in some areas than Windows version.

My first plan is to make completely static,
standalone Linux binary blob so that you can use it no matter what
Linux distro or what system libraries and versions you have installed.
That should be possible with the latest QtCreator and Qt version.

And maybe later I will make a separate RPM version for all RPM based distros
so that they can (if they want to) add it to their own
unofficial/experimental/binary etc. repository.

2)
Add SSL Certificate display to Encrypted tab to show all the little details of
the certificate. Encrypted tab already includes info about currently used ciphers so
it's only natural that this extra information is added there. Besides, it's also
crucial information from security perspective to show and warn users if the currently
viewed pages SSL certificate is forged, too low on security, self-signed or expired.

Checking if it is self-signed, expired or too low on security should be trivial but the
spoofed certificate checking is little bit more complicated because it will need a
database or list of valid certificate fingerprints to compare to.
And althought companies (especially big ones) don't change them that often there still
needs to be a way to keep that list updated.

3)
Add option to spoof PREF cookie. As you probably read from last year NSA is using
Google PREF cookies to locate & target individual computers for their hacking attemps.

http://www.washingtonpost.com/blogs/the-switch/wp/2013/12/10/nsa-uses-google-cookies-to-pinpoint-targets-for-hacking/

There is very little details of the actual content's of the PREF cookie but what I have so far found out while browsing Net is that it just mostly holds settings like how many search results per page to include, language, if SafeSearch is on or off, timestamp and most importantly, some unique identifier string that is probably used to identify your computer.

So mostly, it's a pretty useless tracking cookie and the only reason you would want to allow it is that if you want to disable SafeSearch. I couldn't find any other reason why to enable it (gmail works fine without it)

Of course, if you enable PREF cookie then you can be tracked and we don't want that. So the next obvious step is to block all PREF cookie sent by Google (like is already done by CyberDragon) and send instead our own, forged PREF cookie that will allow you to disable SafeSearch with a bogus identifier.

I have already tried this with some test code and it works. I could use disabled SafeSearch without having any PREF cookies sent by Google stored into my computer memory (CyberDragon does not permanently store enabled cookies but keeps them in memory)

I think that this concept could be usefull for other cookies too ....

4)
Add FTP support. I had totally forgetted the whole FTP stuff and just lately found out
that Qt QNetworkAccessManager does not even handle listing of FTP server files & directories. So FTP listing & browsing support is going to be in 1.6.1

5)
Add HTTPS Everywhere functionality.

6)
Fine tune proxy checking and try to make it faster. And if succeed making it faster then add more proxies when fetching.

So these are the plans. At least the first four features will be 100% sure in next 1.6.1 version.

And if I have time, then the HTTPS everywhere stuff and proxy stuff.

Surf Safe!