Comment WTF (Score 1) 1
WTF is this shit?
WTF is this shit?
And it would be trivial to keep any "clean" account(s) they have on a separate IP,
Trivial, perhaps... but over time it's easy to slip and use an IP that's more traceable to you, which is why I said to publish all of the IP's that handle has posted from.
I can see some appeal to that, but surely any sane leaker will post using a restaurant's free wifi or similar - meaning their doxing gets associated with any other innocent user who happens to have posted updates from that restaurant, with no apparent link to their own isolated accounts?
Personally, I'd probably use the free wifi at the railway station on my daily commute - indeed, I do use it most days, for innocent purposes - or if I wanted to do something that might be traced, ride an hour or so on one of the lines and use another station on the network, using a randomised MAC address on a laptop. Anyone who was identified as associated with me then is completely uninvolved. Yes, maybe you'd catch a few low-level trolls, but you'd be falsely smearing a whole lot of innocent third parties - making the identification worthless anyway.
You are a prohibitionist. As such you are illogical, irrational, arrogant, and totally unreasonable.
Most people do not have a problem with the jackboot of authority, so long as it is on their feet rather than their neck.
Once again you are proving pudge right
This is the worst crime of all.
What about up-conversion to handle 2.4Ghz and 5.8Ghz ranges?
Something I'd like to see is a R/C transmitter that can handle all protocols without having to change out radio modules.
I agree that Apache web server support is vital if HTTP/2 is to get much use. That said, the mod_spdy plug-in for Apache supports SPDY, and has been accepted into Apache trunk. See: http://googledevelopers.blogsp... https://svn.apache.org/viewvc/...
Since HTTP/2 is based on SPDY, it seems likely that this plug-in will be tweaked to support HTTP/2. That said, I suspect the Apache Foundation would say something like, "patches welcome".
What exactly is coding talent?
I'm being a bit coy but mostly to spur discussion: I've been coding since the late 70's, and I think of coding like playing guitar: just about anyone can do it to a reasonable level, most people think they are rockstars, but only a handful really are.
When I was first interviewing for jobs circa 1990 there weren't many people who knew x86 protected mode, so there was always work writing hardware drivers. I was mediocre, I'll admit it, and so were most of my peers, but we got the job done.
Today there are literally thousands of languages, frameworks and tools depending on the application. Ironically, "talent" seems largely the same today as it was in the 80's: if you understand the unique collection (and versions!) of tools a company uses, you're in.
When I hired programmers in the 90's and 00's it was clear some folks got it, and some folks didn't. But even the folks that didn't still got high-paying jobs.
So it really begs the question, "What is talent?" and how do you measure it, and how much do you need? Finding talent means rating talent, and therein is a loaded debate.
The vast majority of people who use the term "open source software" use it with roughly the same meaning as OSI does, which is all that matters. You can confirm this with a quick Google search. Also, note that many organizations that require something to be be "open source software" will point to the OSI definition.
By the commonly-used definition of "open source software", you MUST be able to fork the project and maintain your own version. You cannot legally do that with TrueCrypt, therefore, by definition it is not open source software. Case closed.
TrueCrypt isn't open source software, in spite of the author incorrectly claiming it is. More detail is here, which the author could have learned in 2 minutes of Googling: http://en.wikipedia.org/wiki/T...
TrueCrypt was released under the "TrueCrypt License" which is unique to the TrueCrypt software. It is not part of the pantheon of widely used open source licenses and is not a free software license according to the Free Software Foundation (FSF) license list, as it contains distribution and copyright-liability restrictions. As of version 7.1a (the last full version of the software, released Feb 2012), the TrueCrypt License was Version 3.0.
Discussion of the licensing terms on the Open Source Initiative (OSI)'s license-discuss mailing list in October 2013 suggests that the TrueCrypt License has made progress towards compliance with the Open Source Definition but would not yet pass if proposed for certification as Open Source software.
According to current OSI president Simon Phipps:
As a result of its questionable status with regard to copyright restrictions and other potential legal issues, the TrueCrypt License is not considered "free" by several major Linux distributions and is therefore not included in Debian, Ubuntu, Fedora, openSUSE, or Gentoo.
The wording of the license raises doubts whether those who use it have the right to modify it and use it within other projects. Cryptographer Matthew Green noted that "There are a lot of things [the developers] could have done to make it easier for people to take over this code, including fixing the licensing situation", and speculates that since they didn't do those things (including making the license more friendly), their intent was to prevent anyone from building on their code in the future.
End of life and license version 3.1
The 28 May 2014 announcement of discontinuation of TrueCrypt also came with a new version 7.2 of the software. Among the many changes to the source code from the previous release were changes to the TrueCrypt License — including removal of specific language that required attribution of TrueCrypt as well as a link to the official website to be included on any derivative products — forming a license version 3.1.
On 16 June 2014, the only alleged TrueCrypt developer still answering emails, replied to an email by Matthew Green about the licensing situation. He is not willing to change the license to an open source one, believes that Truecrypt should not be forked, and that if someone wants to create a new version they should start from scratch.
Way back in the day when early digital anything had gobs of TTL and CMOS gate chips I would use a telephone pickup coil to hunt down dead chips.
The hacker community is primarily a male dominated space, therefore it must be hostile and problematic, shitlord!
Perhaps we should start marketing the term "hackette", and include a pen-test ISO image with every Barbie Thumb Drive.
Seems to be the desperate approach in CS-land.
Those Barbie thumb drives already have them. Not my fault you haven't discovered it yet.
Go work for a contractor. Get to know the feds. Then your resume magically moves to the top in usajobs.gov.
Elliptic paraboloids for sale.
