Add1son's Blog

A place for pondering, planning and projects


This is a little bit of an offshoot from my normal posts and rather is an idea for a program of sorts that would be a quantification of how time is spent at a computer for better or for worse. This would help identify patterns and provide a single page overview of how a day at a computer was spent. This could be expanded to multiple devices as well as integration with mobile devices that would provide a wide range of telemetry. These devices could be fitness trackers, Smart phones (with integration into people you may have spoken to, places that you could have gone, and potentially even exercise that was carried out. The idea behind this being that you wouldn’t have to turn anything on but you would have a skeleton of what you had done in that given day. Google collects location data, programs like WhatPulse tracks keystrokes and can also do network usage+application usage, Fitness trackers offer daily summaries that show what you have done in a given day. This posits the question of, well why do we need something different than the solutions already offered? Because this data is yours but it isn’t in your possession.┬áThe idea behind this being that the software would be FOSS and give full control over the data as well as the programs to the power of the user.

The beauty of this project would be that it would all be self hosted and could have both local integration and VPS integration with exactly however many modules a person could choose to integrate providing a dashboard or a high level overview of what occurred in a given day. This data is good and useful but the patterns that could be analyzed in combination with changes of habits or general mood tracking / journal keeping could be monumental in achieving goals. The data would be presented in a format that was easy to expand at a whim to see the technical details but also general enough so that it would be nice to look at. Integration with the goal achieving piece could be implementing something like the 5 minute journal alongside this data.

This top level overview offers little insight on how this would happen technically and to be frank my rudimentary understanding of C++, Python and Bash may not make this something that is feasible but the idea behind it is still interesting and ultimately worth exploring. Ideally this application would work on both Windows and GNU/Linux with Android integration planned on the mobile device side. Ideally the data would be aggregated from available open source tools and the front-end or dashboard would be the piece that would need to be developed.

WPA2 is Broken – KRACK

The HOT new trend is to name the vulnerability that was found with a cool catchy name (CVE’s just don’t cut it anymore), this one holds the name “KRACK”. Other notable vulnerabilities that were named other than this one being Heartbleed, Badlock and ImageTragick.

The embargo on this vulnerability broke at 6AM EST, 10/16/2017 and the following eruption and hype up this this point was very interesting. The technicality of this attack lies in the 4 way handshake in authentication with WPA2 and the mechanism is described much better than I would be able to describe in the sources listed at the bottom.

The implications and proposed fixes here are what are interesting. In the paper countermeasures are listed as mitigation of the key installation attacks and changing the way the Pairwise Transient Keys (PTK) is negotiated. The questioning of the 802.11 standards ambiguity continues in part 6.6 of Discussion as well as the way proofs work theoretically and in practice and whether or not these differ. Finally the fact that nonce recuse is present in GCMP and not CCMP and can be mitigated by the use of a nonce misuse-resistant encryption scheme would reduce the total impact. This is all the information from the paper however, I stumbled upon a Github Repo that is a bit dated at the time of writing that addresses other inherent security flaws that are how WPA2 networks were previously compromised in what is called “Call for WPA3 – what’s wrong with WPA2 security and how to fix it”.

Wireless communication isn’t going away and I believe that rolling the call for WPA3 in the form of a restructure of how WPA works as well as questioning the way the 802.11 standard is built are overall beneficial in making wireless networking as secure as possible. The other interesting takeaway is the idea that the way that the general gap between the way things work theoretically or from a design perspective vs actually in a environment is something that academia and practitioners will not soon get away from.

Bleeping Computer Article
Hip Website
PDF Writeup