Nmap Development mailing list archives

Re: Sriharsha Karamchati Kicked Out of Nmap GSoC for Cheating


From: Ron Bowes <ron () skullsecurity net>
Date: Wed, 2 Jul 2014 18:07:44 -0700

There's also a word for taking direct actions the first time something happens:

http://signalvnoise.com/archives2/dont_scar_on_the_first_cut.php

They have some good advice there. Learn the lesson, be wary, but don't
jump to making new policies for one-off events.

Anyway, it's ultimately up to Fyodor. My opinion is just one.

(Moving Nmap-dev to BCC... not sure if that works the way I expect it,
but I don't think this conversation needs to continue on the public
list)

On Wed, Jul 2, 2014 at 3:11 PM, Barry Allard <barry.allard () gmail com> wrote:
There's a word for doing nothing and expecting a different result.  If
you're wrong and if it happens again, losing GSoC will be the least concern.
If it doesn't happen again because candidates are more of known quantities,
better candidates might be selected and Nmap will look better and it's extra
paperwork to help prevent the former.   Nothing with people is 100%, but
it's better than the alternative.

On Wednesday, July 2, 2014, Ron Bowes <ron () skullsecurity net> wrote:

I'm always the kind of person that thinks knee-jerk reactions to
one-off problems looks worse than solving the rare problem if and when
it pops up.

But, it's a non-trivial discussion and this is hardly the right place
for it. And ultimately, it's up to Fyodor and/or the GSoC admins.

Ron

On Wed, Jul 2, 2014 at 12:49 PM, Barry Allard <barry.allard () gmail com>
wrote:
It makes all concerned look bad, and not taking measures, even for
appearances' sake, looks even worse.
—
Sent from Mailbox


On Wed, Jul 2, 2014 at 11:20 AM, Ron Bowes <ron () skullsecurity net>
wrote:

Fyodor can speak to it better, but realistically in all the students
that have come through, this is the first time it's been an issue. I
don't suspect it's a big enough problem to try solving just yet. :)

On Wed, Jul 2, 2014 at 11:00 AM, Barry Allard <barry.allard () gmail com>
wrote:
PS not that it would stop plagiarism, but maybe ask some FOSS ethics
questions.
—
Sent from Mailbox


On Wed, Jul 2, 2014 at 10:59 AM, Barry Allard
<barry.allard () gmail com>
wrote:

Maybe require a tech phone screen for all candidates and have a
short
waiting list should a selected candidate/s drop for any reason.
Otherwise,
it may make the sponsors / sponsors' org look bad.


Barry

—
Sent from Mailbox


On Wed, Jul 2, 2014 at 9:41 AM, Ron Bowes <ron () skullsecurity net>
wrote:

Robin - I believe the 'cheating' was on the application itself, not
to
Nmap code. When it came to actually writing code, I don't believe
he
contributed much if anything.

Ron

On Tue, Jul 1, 2014 at 11:53 PM, Robin Wood <robin@digi.ninja>
wrote:
I've not followed what he submitted but is there any way to use
any
of
it
if the original authors are OK with it?

May as well salvage what we can.

Robin
On 2 Jul 2014 04:10, "Fyodor" <fyodor () nmap org> wrote:

Hi folks. I'm sorry to report that we had to remove Sriharsha
Karamchati
from the Nmap GSoC program after he was caught cheating :(. It
turns
out
that most of his coding samples were blatantly plagiarized from
others
and
he apparently can't program at more than a very elementary
level.
Sriharsha even convinced a real IPv6 researcher to send him
pre-publication research, which Sriharsha then submitted to us
as
his
own
work after removing the true author's name from every single
slide.
The
saddest part is that we had to reject many worthy, talented and
honest
applicants who could have done great things with the position.

The only good news is that, of the 68 students we've mentored
during
our
decade in the GSoC program, Sriharsha is the first one we had to
remove for
cheating. Let's hope he is also the last!

Cheers,
Fyodor
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/








--
Barry
--
Barry Allard

Schedule an office-hours meeting barryallard.youcanbook.me

LinkedIn

_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

Current thread: