687 karma · joined February 1, 2016
Edit: @jwilk in the comments here pointed to a better article about the security vulnerability [1]. Based on the technical details, there seems to be no reason why Microsoft could not issue a very quick fix loading the DLL from the secure location.
Important quote in my eyes:
“The engineers provided me with an update on this case. They've reviewed the code and were able to reproduce the issue, but have determined that the fix will be implemented in a newer version of the product rather than a security update. The team is planning on shipping a newer version of the client, and this current version will slowly be deprecated. The installer would need a large code revision to prevent DLL injection, but all resources have been put toward development of the new client.”
In other words, it seems Microsoft/Skype doesn’t care about security at all. A couple of lines to fix the bug, in theory, but Microsoft is too busy to do it. Doesn’t make sense, unless a new version would have been released shortly, but it has been 4 months between that email and disclosure.
Edit: Now that I think about it, can see why. I have seen merges where is was good enough to merge, but needed som slight adjustments. Rebase/merge with minor changes would be a good use for this, and would allow for better crediting of both authors.
> I got a strange prompt that Agent wanted to make changes on my computer and needed my admin password
An admin/mod should change the title here, but the concern is still the same.
Example of past availability: https://www.kennedyspacecenter.com/launches-and-events/event...
Most nativity support it now.
I would highly suggest reading Pro Git [0], a well written book on not only how to use git, but also the best practices, common workflows, and some of the internals in to how git works. Many refer to it as the essential book on git.
Also, most games I have played seem to use HTTPS. The only time it is used is when the game does not need an instant result, in which case they use HTTP or HTTPs. Most of the times, this is in the main menu or similar. Doing this makes it even harder (assuming they use certificate pinning) for users to change the values returns to gain any advantage on their client.
Any part of the game that needs speed should be using a UDP based protocol.
Worst case scenario: An Android zero day that can be spread via WiFi or Bluetooth that infects devices in a cryptolocker style. The more versions it can affect, the better.
Shoot. Probably shouldn’t give people ideas, especially when I have an Android device. At least it runs LineageOS and can be updated easily...
Edit: To clarify my idea, imagine the Windows XP crypolocker viruses, but for Android instead, spreading not through cell towers or WiFi routers, but instead spreading via the cellular/WiFi/Bluetooth chips in the devices.
I’m starting to wonder if I should buy a portable Faraday cage for my devices...
https://github.com/Katee/git-bomb/commit/45546f17e5801791d4b... shows:
"Sorry, this diff is taking too long to generate. It may be too large to display on GitHub."
...so they must have some kind of backend limits that may have prevented this for becoming an issue.
I wonder what would happen if it was hosted on a GitLab instance? Might have to try that sometime...
"During the 78rpm era there are no standards for speed, stylus size, or record/playback equalization. Within the trade there is broad agreement that optimizing playback requires both knowledge of the documentation that’s available on these parameters for each label over time, and some amount of judgment. There are many reasons why judgment is necessary. One reason is that the disc may be worn from being played many times with the correct stylus size. Better results may come from using a different (“the wrong”) size stylus because it sits in a portion of the groove that is in better condition. But there’s no free lunch. Using a smaller size may mean a noisier transfer as it plays a less cleanly molded part of the disc. Using a larger size may increase tracing distortion that is the result of the larger size not fitting all the way to the bottom of the smaller grooves of higher frequencies. [...]"
- go unanswered
- get answered by the community with "here is how you do it," without the "here is why" part.
- the question can't be answered by the community and all you see are messages along the lines of "same issue here."
Rarely do I see the "here is how you do it and here is why" answer I am looking for.
[1] Only good source I can find. (Mostly sourced from observation.) http://verdantlabs.com/politics_of_professions/
[2] https://www.wired.com/2015/04/dmca-ownership-john-deere/