Showing posts with label greg evans. Show all posts
Showing posts with label greg evans. Show all posts

25 July 2014

I fought the law...and won (sort of)

This TechDirt t-shirt seems appropriate.
As you may remember, last month I received an email notification from Blogger (Google) that they had received a DMCA takedown notice for one of my blog posts. Because the blog post was about Gregory Evans, I speculated that he might have been involved in the takedown. Although to be clear, it was Google who received the actual takedown notice, and all I got was a notification about the notice, so at the time I was never actually aware of 1) who sent it; and 2) what content of the blog post was supposed to have been infringing.

You can read the original blog post here (I have since republished it). The entire blog post was authored by me with the exception of two small screenshots from the MIS Training Institute's homepage which reflected substantive changes to their speaker lineup and the comparison screenshots reflected that change. The rest of the blog post was the copy of an email that I wrote to the MIS Training Institute and links to other posts.

Blogger told me that they would post the takedown notice on Chilling Effects. That never happened. Nonetheless, without any evidence of how my blog post might have been infringing, I filled a counter-notice essentially arguing fair use of whatever content I had used.

Yesterday, I received notice that Google had completed processing my counter notification and had reinstated the content in question. What content was that? Of course, they didn't tell me. My best guess is this: in the original blog post, I included the text of an email that I wrote to the MIS Training Institute. In that email, I linked to a CBS Atlanta expose of Evans that was posted on YouTube. That video had subsequently been taken down (you can see if you follow the link here). Linking to infringing content could be considered a DMCA violation. On the other hand, if the infringing content has already been taken down, then I'm not really linking to infringing content anymore, because the content doesn't exist. Again, I have no evidence that this is why my blog post has been restored, but it's my only reasonable guess at this point.

The DMCA process is broken. It is largely automated which means that you can't really expect to ever speak to a human being to help sort out your problem. If your blog is hosted (as mine is), the hoster receives the takedown notice, and you may never see it (as I never did). You might guess that Google receives hundreds or thousands of takedown notices every day. Mine wasn't worth anyone's individual attention. Chilling Effects may be a good idea in theory, but in practice the site is difficult to use. My attempts to contact the site's administrators to help in finding my notice (if perhaps it was posted and I couldn't find it) went unanswered.

In the end, my content is back. Again, I'm not quite sure what content was at question, which is sort of a big deal when you think about it. How can you fight back if you don't even know what you're fighting for (or against)? I may have been lucky. But others might give up more easily.

The DMCA process is broken. If we want content creators to thrive, it's a problem we're going to have to confront.

17 June 2014

I received a DMCA takedown notice for a blog post I made three years ago about Gregory Evans

Yesterday I received a DMCA takedown notice for a blog post I made about three years ago about Gregory Evans. The entire blog post was authored by me with the exception of two small screenshots from the MIS Training Institute's homepage which reflected substantive changes to their speaker lineup and the comparison screenshots reflected that change. The rest of the blog post was the copy of an email that I wrote to the MIS Training Institute and links to other blog posts. I can't actually link you to the post at this point because Google placed the post in a draft status. If I were to republish it without changes, it could be considered a violation and count against my account. So you'll just have to take my word about the content of the post. 

This morning I filed a counter-claim disputing the takedown. In the counter-claim, I argued that the use of the very small screenshots was fair use. To be perfectly clear, the takedown notice itself does not yet appear to be available, and Google's email to me does not say who filed it. Although my counter-claim addresses the screenshots from the MIS Training Institute's homepage, I suspect (although I have no evidence at this point) that it was not MISTI but rather Gregory Evans who actually filed the takedown notice. This would be particularly interesting because there is certainly no content on my blog post created by him. My best guess is that I linked to someone else (perhaps a link to Attrition.org) and he doesn't like that very much. But again, that's just a guess.

At this point, I don't have any more information, but I'll certainly keep you updated. If you do have questions, please feel free to ask.

12 November 2012

Twitter sniff test for fake followers (read: @GregoryDEvans)

There are a number of ways to look at someone's Twitter account to see if they have artificially inflated their followers (i.e., buying follower lists), but I wanted to add one of my own. This isn't a definite test, but should give you a good sense of whether someone's followers are legit.

It's a very simple ratio of followers to lists. In the case of my account, it's 2,295 (as of 11/12/12). Now figure the number of lists the account is on (this isn't displayed directly by number on Twitter, but is displayed on Tweetdeck or other similar Twitter clients). Again, on my account, it's 141 lists. So 2,295:141 reduces to about 16.3:1. In my experience, I have found that a range of 10-25:1 is very common among most people. I don't have enough data to know how well this ratio scales to significantly higher number of followers, but the ratios to tend to be higher; in the range of 40-100:1.


The idea here is that your legitimate, engaged followers are likely to put you on their lists, while fake followers don't actually do anything.

For this blog post, I looked at (an admittedly small sample of) ten people I follow, who have followers from under 100 to over 100,000. In all but one case, the ratio was between 10-25 to 1 (in the one off case, it was 6:1, an argument for more engaged followers, not less).

Now let's take a look at one example, the infamous @GregoryDEvans. He has 42,331 followers but is only on 45 lists. A ratio of 940:1! Realistically, he should be on 2,500-3,000+ lists (and even here, he is on several lists that are unique to his situation). Fake followers, anyone?

Feel free to punch holes in this test. Any ideas?

25 August 2011

LIGATT's Gregory Evans goes down in flames again

Dave Lewis (@gattaca) of Liquidmatrix Security Digest made a post on Tuesday lamenting the fact that Gregory Evans had been tapped to be one of the keynote speakers at MIS Training Institute's 2nd Annual ICT Security Africa Summit in Ghana in September. To those that don't know about Gregory Evans (where have you been hiding, seriously?!), check out his sordid history here and here.

Whether to engage Evans (and potentially give him more publicity) is certainly a worthwhile discussion. Some say to ignore him completely, while others (and I find myself in this camp) tend to want to expose him, even if that gives him some of the publicity he's craving, with the idea that eventually he'll fall. Either way, that's an ongoing discussion and not the subject of this post. Also, I should make it clear that Greg Evans has never done anything to me or even communicated with me. My problem with him is who he portrays himself to be, and how that impacts the way people see our community.

Anyways, I decided that the least I could do was to write a letter to one of the conference organizers and let them know who they were dealing with. My guess was that they bought his story (ex-con hacker now turned ethical hacker) and didn't know about his more recent activities. So I sent this:
Good afternoon,
I noted with particular interest on your homepage (http://www.mistieurope.com) that you have Mr. Gregory Evans listed as one of the keynote speakers for your 2nd Annual ICT Security Africa Summit in September (http://www.mistieurope.com/default.asp?Page=65&ProductID=13227).
Mr. Evans proudly claims his status as an ex-hacker (and ex-felon), but there is a much deeper (and more recent) history that you should consider before allowing Mr. Evans to speak. I would like to point you to a web page (http://attrition.org/errata/charlatan/gregory_evans/) that details multiple issues with Mr. Evans conduct over the past few years, including multiple counts of plagiarism, multiple legal and financial issues, multiple lies about the certifications he holds, and much more. Added to that, Mr. Evans has repeatedly threatened those who criticize him, and frequently claims any criticisms of him are attacks against his race.
Additionally, I would like to point you to the video from CBS News Atlanta, who exposed much of Mr. Evans fraud this past February. This video can be viewed here: (http://www.youtube.com/watch?v=O3Ms8UZnOoA).
I believe that after learning more about Mr. Evans background, you will come to the conclusion that it is not worth the reputation of your conference to extend him an invitation. Mr. Evans is a stain on the computer security industry and that stain goes with everything he touches. Please do not allow your conference to be blighted by Mr. Evans association.
Please note that I have nothing to gain from writing this email except the assurance that I did the right thing in letting you know about Mr. Evans' past.
Yesterday morning I found out that several other people in the community had also written letters to the conference organizers, and that Greg Evans was no longer speaking at the event. I captured the writing on the wall, so to speak, from the conference website:
As I made clear in my letter, I had nothing to gain from doing this except the assurance that I was doing the right thing. Dave deserves kudos for bringing this issue to the community. All I did was write a letter. If that helped the organizers in even a small way, I feel that I succeeded.

Given Greg Evans penchant for lawsuits, I half expect at least the threat of one. And yes, seeing "theprez98" on court documents would indeed be an interesting sight. Hopefully his lawyer talks some sense into him and saves him the time and money.

You might think that I am helping to ruin Greg Evans' reputation by aiding in getting his gigs canceled. Far from it. Greg Evans ruined his own reputation when he decided to lie, cheat and steal. I'm just (one of many people) letting people know. Truth be told, this is a win for the security community. Greg Evans goes down in flames again.