JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for TB-SUPPORT Archives


TB-SUPPORT Archives

TB-SUPPORT Archives


TB-SUPPORT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TB-SUPPORT Home

TB-SUPPORT Home

TB-SUPPORT  November 2007

TB-SUPPORT November 2007

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Heinz' Challenge

From:

"Coles, J (Jeremy)" <[log in to unmask]>

Reply-To:

Testbed Support for GridPP member institutes <[log in to unmask]>

Date:

Thu, 1 Nov 2007 10:37:34 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (159 lines)

Dear All

I have further information on the code use and why the user thought
biomed an appropriate VO for it:

" The main idea is to factor prime numbers in order to show how long it 
 would take to break a 768-bit code (also referred to as "sieving"). 
 Since PKI certificates use 1024 or 2048 bit codes, and biomed has 
 typically the most severe security, I thought it would be fine to use 
 the VO for that. However, if people do not agree with that opinion, 
 I'm happy to explore other solutions.
 
 Seems that some people were concerned since they thought that there
 might be a price in USD awarded if a code is cracked. This is _not_ the

 case, and the sieving exercise is pure computer science research."

For this work Heinz has been working with Proj. Lenstra from the EPFL,
one of the most well-known persons in the field of cryptography and
number sieving.

And on the method employed:

" ... one more point on number sieving. It is not "brute force" but it 
involves complex algorithms that reduces the actual run time of the 
overall "challenge". One result of the work can be new more efficient 
sieving algorithms: important for PKI and GSI".

The question now coming from within the biomed VO is whether based on
this explanation sites would re-authorise the user or whether an
alternative route needs to be found for the activity - such as the
setting up of a new VO. Though I can probably guess your replies you
should let me know your opinions. Since we are not working in isolation,
once I've got a feel for the response here I will push the matter to the
ROC manager's for further discussion. 

Jeremy



> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of Alessandra Forti
> Sent: 01 November 2007 09:33
> To: [log in to unmask]
> Subject: Re: Heinz' Challenge
> 
> Hi Jeremy,
> 
> I'm not sure biomed was aware of this.  I don't have those jobs on my
> cluster and I was keen to give Heinz the benefit of the doubt as I met
> him and seemed a reasonable guy. But this is even worst than I
expected.
> Since it comes from the management and violates all the rules of trust
> that this grid is built upon. I mean so long for policies and AUPs.
They
> couldn't do more damage.
> 
> I also agree with Kostas that "Sorry" is not enough.
> 
> cheers
> alessandra
> 
> Coles, J (Jeremy) wrote:
> > Hi Kostas/Graeme/All
> >
> > I agree that this needs to be escalated and it will be. First though
I
> > would like biomed representatives and Heinz to explain/respond - I
can
> > not think of a justification on their side but that does not mean
there
> > isn't one. Once everyone has responded directly (or if the ticket
goes
> > without a proper response) then it can be taken further.
Tier-2s/sites
> > are of course able to decide themselves if they wish to take more
> > immediate action as some have already done.
> >
> > Regards,
> > Jeremy
> >
> >
> >
> >> -----Original Message-----
> >> From: Testbed Support for GridPP member institutes [mailto:TB-
> >> [log in to unmask]] On Behalf Of Kostas Georgiou
> >> Sent: 01 November 2007 02:19
> >> To: [log in to unmask]
> >> Subject: Re: Heinz' Challenge
> >>
> >> On Thu, Nov 01, 2007 at 12:19:26AM +0000, Graeme Stewart wrote:
> >>
> >>> From the CIC portal, biomed described itself as:
> >>>
> >>> "These VO covers the areas related to health sciences. Currently,
it
> >>> is divided in 3 sectors: medical imaging, bioinformatics and drug
> >>> discovery."
> >>>
> >>> We support the VO for it to engage in _that_ work, and we're happy
> > to
> >>> have done work related to malaria, avian flu, etc. However, I
don't
> >>> see anything about rsa768 factorisation.
> >>>
> >>> So, this is, to my mind, even worse. This is not just Heinz being
a
> >>> loose cannon, but sites being conned by top level EGEE management
> >>> into running jobs to which they had in no way agreed to run.
> >>>
> >>> The problem was then exacerbated by the way that Heinz wrote the
> >>> code, which resulted in biomed being able to grab far more of
many,
> >>> many clusters in the UK than was reasonable. (And so much for EGEE
> >>> promoting push model RBs - just send in the pilots and watch our
> >>> fairsharing go all to hell.)
> >> This is exactly what I was going to say (better worded and probably
> > far
> >> more polite though).
> >>
> >>> Frankly, as the UK, I think we should give them a bloody rocket
for
> >>> this. They've shown huge disrespect to sites - and how on earth
can
> >>> they expect other EGEE users and VOs to play by the rules when
then
> >>> engage in such a gross violation of our trust?
> >> ...
> >>> We haven't banned biomed - we've banned Heinz. And I am in no
hurry
> >>> to unban him. I'd expect an apology at the very least, as well as
an
> >>> assurance that this will not happen again.
> >> People should keep in mind that we are going to have similar cases
in
> >> the future. If our responce today is going to be "a sorry is
enough"
> >> what is going to stop the next user doing the same thing tomorrow
> >> considering how hard it is for us to spot an abuse? Unless there is
> >> a strong repsonce people will think "If I am not found (quite
likely)
> >> great, if I am found a sorry will solve everything".
> >>
> >> Cheers,
> >> Kostas
> >>
> >> PS> BTW if the management agrees that breaking rsa768 is fine then
> > I'll
> >> have a go as well or is it only Heinz/biomed that can have a go?
> >
> 
> --
> ***********************************
> * Alessandra Forti                *
> * NorthGrid Technical Coordinator *
> * University of Manchester        *
> ***********************************

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager