|
View:
New views
16 Messages
—
Rating Filter:
Alert me
|
|
|
crypto statement revisitedFellow researchers,
I'd like to pick up again a previous thread started by Stefano[1] about export declarations. Two labs use crypto libs ATM AFAIK, BaDCA and Vysper. So the following should probably be added to https://svn.apache.org/repos/asf/infrastructure/site/trunk/xdocs/licenses/exports/index.xml with the details for BaDCA to be done: <Project href="http://james.apache.org/"> <Name>Apache Labs Project</Name> <Contact><Name>Stefano Mazzocchi</Name></Contact> <Product> <Name>Apache Vysper</Name> <Version> <Names>development</Names> <ECCN>5D002</ECCN> <ControlledSource href="http://svn.apache.org/repos/asf/labs/vysper/"> <Manufacturer>ASF</Manufacturer> <Why>includes bcprov encryption library</Why> </ControlledSource> <ControlledSource href="http://www.bouncycastle.org/download/bcprov-jdk15-135.tar.gz"> <Manufacturer>Bouncy Castle</Manufacturer> <Why>general-purpose encryption library</Why> </ControlledSource> </Version> </Product> <Product> <Name>Apache BaDCA</Name> <Version> <Names>development</Names> <ECCN>5D002</ECCN> <ControlledSource href="http://svn.apache.org/repos/asf/labs/badca/"> <Manufacturer>ASF</Manufacturer> <Why> *TBD* </Why> </ControlledSource> <ControlledSource > * TBD: reference(s) to external crypto lib * </ControlledSource> </Version> </Product> </Project> Bernd [1] http://mail-archives.apache.org/mod_mbox/labs-labs/200803.mbox/%3c47D846D7.1040605@...%3e --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedAdditionally an email must be sent somewhere to tell about the fact. I
sent it for shindig, so I can look into the details if needed, but I don't have it to check right now. Regards Santiago El mar, 29-04-2008 a las 08:01 +0200, Bernd Fondermann escribió: > Fellow researchers, > > I'd like to pick up again a previous thread started by Stefano[1] about > export declarations. > > Two labs use crypto libs ATM AFAIK, BaDCA and Vysper. > > So the following should probably be added to > https://svn.apache.org/repos/asf/infrastructure/site/trunk/xdocs/licenses/exports/index.xml > with the details for BaDCA to be done: > > <Project href="http://james.apache.org/"> > <Name>Apache Labs Project</Name> > <Contact><Name>Stefano Mazzocchi</Name></Contact> > <Product> > <Name>Apache Vysper</Name> > <Version> > <Names>development</Names> > <ECCN>5D002</ECCN> > <ControlledSource > href="http://svn.apache.org/repos/asf/labs/vysper/"> > <Manufacturer>ASF</Manufacturer> > <Why>includes bcprov encryption library</Why> > </ControlledSource> > <ControlledSource > href="http://www.bouncycastle.org/download/bcprov-jdk15-135.tar.gz"> > <Manufacturer>Bouncy Castle</Manufacturer> > <Why>general-purpose encryption library</Why> > </ControlledSource> > </Version> > </Product> > > <Product> > <Name>Apache BaDCA</Name> > <Version> > <Names>development</Names> > <ECCN>5D002</ECCN> > <ControlledSource href="http://svn.apache.org/repos/asf/labs/badca/"> > <Manufacturer>ASF</Manufacturer> > <Why> *TBD* </Why> > </ControlledSource> > <ControlledSource > > * TBD: reference(s) to external crypto lib * > </ControlledSource> > </Version> > </Product> > > </Project> > > > Bernd > > [1] > http://mail-archives.apache.org/mod_mbox/labs-labs/200803.mbox/%3c47D846D7.1040605@...%3e > > --------------------------------------------------------------------- > To unsubscribe, e-mail: labs-unsubscribe@... > For additional commands, e-mail: labs-help@... -- Santiago Gala http://memojo.com/~sgala/blog/ --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedOn 4/29/08, Santiago Gala <sgala@...> wrote:
> Additionally an email must be sent somewhere to tell about the fact. I > sent it for shindig, so I can look into the details if needed, but I > don't have it to check right now. The chair needs to send the mail > > Regards > Santiago > > El mar, 29-04-2008 a las 08:01 +0200, Bernd Fondermann escribió: > > Fellow researchers, > > > > I'd like to pick up again a previous thread started by Stefano[1] about > > export declarations. > > > > Two labs use crypto libs ATM AFAIK, BaDCA and Vysper. > > > > So the following should probably be added to > > > https://svn.apache.org/repos/asf/infrastructure/site/trunk/xdocs/licenses/exports/index.xml > > with the details for BaDCA to be done: > > > > <Project href="http://james.apache.org/"> > > <Name>Apache Labs Project</Name> > > <Contact><Name>Stefano Mazzocchi</Name></Contact> > > <Product> > > <Name>Apache Vysper</Name> > > <Version> > > <Names>development</Names> > > <ECCN>5D002</ECCN> > > <ControlledSource > > href="http://svn.apache.org/repos/asf/labs/vysper/"> > > <Manufacturer>ASF</Manufacturer> > > <Why>includes bcprov encryption library</Why> > > </ControlledSource> > > <ControlledSource > > href="http://www.bouncycastle.org/download/bcprov-jdk15-135.tar.gz"> > > <Manufacturer>Bouncy Castle</Manufacturer> > > <Why>general-purpose encryption library</Why> > > </ControlledSource> > > </Version> > > </Product> > > > > <Product> > > <Name>Apache BaDCA</Name> > > <Version> > > <Names>development</Names> > > <ECCN>5D002</ECCN> > > <ControlledSource > href="http://svn.apache.org/repos/asf/labs/badca/"> > > <Manufacturer>ASF</Manufacturer> > > <Why> *TBD* </Why> > > </ControlledSource> > > <ControlledSource > > > * TBD: reference(s) to external crypto lib * > > </ControlledSource> > > </Version> > > </Product> > > > > </Project> > > > > > > Bernd > > > > [1] > > > http://mail-archives.apache.org/mod_mbox/labs-labs/200803.mbox/%3c47D846D7.1040605@...%3e > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: labs-unsubscribe@... > > For additional commands, e-mail: labs-help@... > > -- > Santiago Gala > http://memojo.com/~sgala/blog/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: labs-unsubscribe@... > For additional commands, e-mail: labs-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedOn Tue, Apr 29, 2008 at 8:13 AM, Santiago Gala <sgala@...> wrote:
> ...Additionally an email must be sent somewhere to tell about the fact. I > sent it for shindig, so I can look into the details if needed, but I > don't have it to check right now.... https://issues.apache.org/jira/browse/TIKA-118 documents what was done for Tika, that might help. -Bertrand --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedEl mar, 29-04-2008 a las 07:45 +0100, Robert Burrell Donkin escribió:
> On 4/29/08, Santiago Gala <sgala@...> wrote: > > Additionally an email must be sent somewhere to tell about the fact. I > > sent it for shindig, so I can look into the details if needed, but I > > don't have it to check right now. > > The chair needs to send the mail Yeah, I think it is different for incubator; because of the number of podlings it is done by mentors instead. Not sure about labs, which is somehow similar to incubator. Regards Santiago > > > > > Regards > > Santiago > > > > El mar, 29-04-2008 a las 08:01 +0200, Bernd Fondermann escribió: > > > Fellow researchers, > > > > > > I'd like to pick up again a previous thread started by Stefano[1] about > > > export declarations. > > > > > > Two labs use crypto libs ATM AFAIK, BaDCA and Vysper. > > > > > > So the following should probably be added to > > > > > https://svn.apache.org/repos/asf/infrastructure/site/trunk/xdocs/licenses/exports/index.xml > > > with the details for BaDCA to be done: > > > > > > <Project href="http://james.apache.org/"> > > > <Name>Apache Labs Project</Name> > > > <Contact><Name>Stefano Mazzocchi</Name></Contact> > > > <Product> > > > <Name>Apache Vysper</Name> > > > <Version> > > > <Names>development</Names> > > > <ECCN>5D002</ECCN> > > > <ControlledSource > > > href="http://svn.apache.org/repos/asf/labs/vysper/"> > > > <Manufacturer>ASF</Manufacturer> > > > <Why>includes bcprov encryption library</Why> > > > </ControlledSource> > > > <ControlledSource > > > href="http://www.bouncycastle.org/download/bcprov-jdk15-135.tar.gz"> > > > <Manufacturer>Bouncy Castle</Manufacturer> > > > <Why>general-purpose encryption library</Why> > > > </ControlledSource> > > > </Version> > > > </Product> > > > > > > <Product> > > > <Name>Apache BaDCA</Name> > > > <Version> > > > <Names>development</Names> > > > <ECCN>5D002</ECCN> > > > <ControlledSource > > href="http://svn.apache.org/repos/asf/labs/badca/"> > > > <Manufacturer>ASF</Manufacturer> > > > <Why> *TBD* </Why> > > > </ControlledSource> > > > <ControlledSource > > > > * TBD: reference(s) to external crypto lib * > > > </ControlledSource> > > > </Version> > > > </Product> > > > > > > </Project> > > > > > > > > > Bernd > > > > > > [1] > > > > > http://mail-archives.apache.org/mod_mbox/labs-labs/200803.mbox/%3c47D846D7.1040605@...%3e > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: labs-unsubscribe@... > > > For additional commands, e-mail: labs-help@... > > > > -- > > Santiago Gala > > http://memojo.com/~sgala/blog/ > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: labs-unsubscribe@... > > For additional commands, e-mail: labs-help@... > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: labs-unsubscribe@... > For additional commands, e-mail: labs-help@... -- Santiago Gala http://memojo.com/~sgala/blog/ --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedSantiago Gala wrote:
> El mar, 29-04-2008 a las 07:45 +0100, Robert Burrell Donkin escribió: >> On 4/29/08, Santiago Gala <sgala@...> wrote: >>> Additionally an email must be sent somewhere to tell about the fact. I >>> sent it for shindig, so I can look into the details if needed, but I >>> don't have it to check right now. >> The chair needs to send the mail > > Yeah, I think it is different for incubator; because of the number of > podlings it is done by mentors instead. Not sure about labs, which is > somehow similar to incubator. No, the chair should always send that email. Think about 'good crypto' vs something the BIX determines to be 'bad crypto' (wtf that would be). The chair has additional support of and protection from being a corporate officer of the ASF. But it's simplest for all if others can help the chair by updating license/exports/index.html. That entry provides the chair with everything they need to know to fire off that notice. Bill --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedWilliam A. Rowe, Jr. wrote:
> Santiago Gala wrote: >> El mar, 29-04-2008 a las 07:45 +0100, Robert Burrell Donkin escribió: >>> On 4/29/08, Santiago Gala <sgala@...> wrote: >>>> Additionally an email must be sent somewhere to tell about the fact. I >>>> sent it for shindig, so I can look into the details if needed, but I >>>> don't have it to check right now. >>> The chair needs to send the mail >> >> Yeah, I think it is different for incubator; because of the number of >> podlings it is done by mentors instead. Not sure about labs, which is >> somehow similar to incubator. > > No, the chair should always send that email. Think about 'good crypto' > vs something the BIX determines to be 'bad crypto' (wtf that would be). > The chair has additional support of and protection from being a corporate > officer of the ASF. But it's simplest for all if others can help the > chair by updating license/exports/index.html. That entry provides the > chair with everything they need to know to fire off that notice. Hmm, the chair just got back from his honeymoon and lab's crypto was not exactly very high on his priority list. So, what email are we talking about? -- Stefano. --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedOn Tue, May 13, 2008 at 2:53 PM, Stefano Mazzocchi <stefano@...> wrote:
<snip/> > > Hmm, the chair just got back from his honeymoon and lab's crypto was not > exactly very high on his priority list. > Hey! Congratulations! Hadn't heard that project was under way..... :-) -- Peter Hunsberger --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedStefano Mazzocchi wrote:
> William A. Rowe, Jr. wrote: >> Santiago Gala wrote: >>> El mar, 29-04-2008 a las 07:45 +0100, Robert Burrell Donkin escribió: >>>> On 4/29/08, Santiago Gala <sgala@...> wrote: >>>>> Additionally an email must be sent somewhere to tell about the fact. I >>>>> sent it for shindig, so I can look into the details if needed, but I >>>>> don't have it to check right now. >>>> The chair needs to send the mail >>> >>> Yeah, I think it is different for incubator; because of the number of >>> podlings it is done by mentors instead. Not sure about labs, which is >>> somehow similar to incubator. >> >> No, the chair should always send that email. Think about 'good crypto' >> vs something the BIX determines to be 'bad crypto' (wtf that would be). >> The chair has additional support of and protection from being a corporate >> officer of the ASF. But it's simplest for all if others can help the >> chair by updating license/exports/index.html. That entry provides the >> chair with everything they need to know to fire off that notice. > > Hmm, the chair just got back from his honeymoon and lab's crypto was not > exactly very high on his priority list. > > So, what email are we talking about? Not only an email, but following a whole process described here http://www.apache.org/dev/crypto Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedBernd Fondermann wrote:
> Stefano Mazzocchi wrote: >> So, what email are we talking about? > > Not only an email, but following a whole process described here > > http://www.apache.org/dev/crypto Although it's Stefano's job to email the official notice, and to oversee the labs, it is not his responsibility to avoid committing crypto-encumbered code. It's up to each of the folk who *are prepared to add* such code in labs' svn repository to communicate this to Stefano *in advance* of committing the code. The exercise over the past four months was first and foremost to educate all the PMC's on this policy. So if those of you who mistakenly committed crypto code would be kind enough to put together these details and pass on the appropriate diffs for the https://svn.apache.org/repos/asf/infrastructure/site/trunk/xdocs/licenses/exports/index.xml file and the appropriate notice under that policy, you will spare Stefano the headache and heartache of purging those repositories from svn. Bill --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedWilliam A. Rowe, Jr. wrote:
> Bernd Fondermann wrote: >> Stefano Mazzocchi wrote: >>> So, what email are we talking about? >> >> Not only an email, but following a whole process described here >> >> http://www.apache.org/dev/crypto > > Although it's Stefano's job to email the official notice, and to oversee > the labs, it is not his responsibility to avoid committing > crypto-encumbered > code. It's up to each of the folk who *are prepared to add* such code > in labs' svn repository to communicate this to Stefano *in advance* of > committing the code. The exercise over the past four months was first and > foremost to educate all the PMC's on this policy. > > So if those of you who mistakenly committed crypto code would be kind > enough > to put together these details and pass on the appropriate diffs for the > https://svn.apache.org/repos/asf/infrastructure/site/trunk/xdocs/licenses/exports/index.xml > > file and the appropriate notice under that policy, you will spare Stefano > the headache and heartache of purging those repositories from svn. Agreed. I previously asked if we should remove crypto code from Vysper, and it was agreed that no, we can live with it for now as long as the export notification is added. So here we go. At the beginning of this thread one will find the proposed - yet incomplete - XML to be added to index.xml. (Oops, I notice right now that the very first line should not read "james.apache.org" but "labs....") I will try to ping BaDCA for the missing information and post an update. I am not on the Labs PMC, but if I there is anything I can do to move this forward, please give me a little hint. Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedEl mar, 13-05-2008 a las 12:53 -0700, Stefano Mazzocchi escribió:
> William A. Rowe, Jr. wrote: > > Santiago Gala wrote: > >> El mar, 29-04-2008 a las 07:45 +0100, Robert Burrell Donkin escribió: > >>> On 4/29/08, Santiago Gala <sgala@...> wrote: > >>>> Additionally an email must be sent somewhere to tell about the fact. I > >>>> sent it for shindig, so I can look into the details if needed, but I > >>>> don't have it to check right now. > >>> The chair needs to send the mail > >> > >> Yeah, I think it is different for incubator; because of the number of > >> podlings it is done by mentors instead. Not sure about labs, which is > >> somehow similar to incubator. > > > > No, the chair should always send that email. Think about 'good crypto' > > vs something the BIX determines to be 'bad crypto' (wtf that would be). > > The chair has additional support of and protection from being a corporate > > officer of the ASF. But it's simplest for all if others can help the > > chair by updating license/exports/index.html. That entry provides the > > chair with everything they need to know to fire off that notice. > > Hmm, the chair just got back from his honeymoon and lab's crypto was not > exactly very high on his priority list. :) congrats! I understand about priorities... > > So, what email are we talking about? > I was asking for specifics about incubator, in the email you quote. But in the case being discussed here, BadCA and vysper are using encryption technologies, so the procedure at https://svn.apache.org/repos/asf/infrastructure/site/trunk/xdocs/licenses/exports/index.xml should be followed, as Bernd Fondermann pointed Apr 29th in the email that started this thread. Bertrand Delacretaz pointed at https://issues.apache.org/jira/browse/TIKA-118 to see the whole procedure outlined. Basically the work involved is: * assessment of the crypto used * NOTICE in the lab code with the details * adding notes to the first URL (Bernd's email) * the chair sending an email to whatever authority pointing them to the URLs. Regards Santiago -- Santiago Gala http://memojo.com/~sgala/blog/ --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedOn 14/05/2008, Santiago Gala <santiago.gala@...> wrote:
> El mar, 13-05-2008 a las 12:53 -0700, Stefano Mazzocchi escribió: > > > William A. Rowe, Jr. wrote: > > > Santiago Gala wrote: > > >> El mar, 29-04-2008 a las 07:45 +0100, Robert Burrell Donkin escribió: > > >>> On 4/29/08, Santiago Gala <sgala@...> wrote: > > >>>> Additionally an email must be sent somewhere to tell about the fact. I > > >>>> sent it for shindig, so I can look into the details if needed, but I > > >>>> don't have it to check right now. > > >>> The chair needs to send the mail > > >> > > >> Yeah, I think it is different for incubator; because of the number of > > >> podlings it is done by mentors instead. Not sure about labs, which is > > >> somehow similar to incubator. > > > > > > No, the chair should always send that email. Think about 'good crypto' > > > vs something the BIX determines to be 'bad crypto' (wtf that would be). > > > The chair has additional support of and protection from being a corporate > > > officer of the ASF. But it's simplest for all if others can help the > > > chair by updating license/exports/index.html. That entry provides the > > > chair with everything they need to know to fire off that notice. > > > > Hmm, the chair just got back from his honeymoon and lab's crypto was not > > exactly very high on his priority list. > > > :) congrats! I understand about priorities... > > > > > > So, what email are we talking about? > > > > > I was asking for specifics about incubator, in the email you quote. But > in the case being discussed here, BadCA and vysper are using encryption > technologies, so the procedure at > > https://svn.apache.org/repos/asf/infrastructure/site/trunk/xdocs/licenses/exports/index.xml > > should be followed, as Bernd Fondermann pointed Apr 29th in the email > that started this thread. > > Bertrand Delacretaz pointed at > > https://issues.apache.org/jira/browse/TIKA-118 > > to see the whole procedure outlined. > > Basically the work involved is: > * assessment of the crypto used > * NOTICE in the lab code with the details AFAIK, the notice does not normally go in the NOTICE file (which is for attributions only), but in a README file. > * adding notes to the first URL (Bernd's email) > * the chair sending an email to whatever authority pointing them to the > URLs. > > Regards > Santiago > > -- > > Santiago Gala > http://memojo.com/~sgala/blog/ > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: labs-unsubscribe@... > For additional commands, e-mail: labs-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisitedI understood it went to the NOTICE file because it was a mandatory
Notice (under the US export laws), akin to a mandatory attribution under copyright laws. I'm using the distinction that Roy said: all that should go into an About... dialog box belongs to NOTICE. And the export notification looks like the prototypical About... stuff. I might be wrong, meaning I need to move the shindig NOTICE if it is the case. Anybody knows for certain? Regards Santiago On Wed, May 14, 2008 at 11:17 AM, sebb <sebbaz@...> wrote: > > On 14/05/2008, Santiago Gala <santiago.gala@...> wrote: > > El mar, 13-05-2008 a las 12:53 -0700, Stefano Mazzocchi escribió: > > > > > William A. Rowe, Jr. wrote: > > > > Santiago Gala wrote: > > > >> El mar, 29-04-2008 a las 07:45 +0100, Robert Burrell Donkin escribió: > > > >>> On 4/29/08, Santiago Gala <sgala@...> wrote: > > > >>>> Additionally an email must be sent somewhere to tell about the fact. I > > > >>>> sent it for shindig, so I can look into the details if needed, but I > > > >>>> don't have it to check right now. > > > >>> The chair needs to send the mail > > > >> > > > >> Yeah, I think it is different for incubator; because of the number of > > > >> podlings it is done by mentors instead. Not sure about labs, which is > > > >> somehow similar to incubator. > > > > > > > > No, the chair should always send that email. Think about 'good crypto' > > > > vs something the BIX determines to be 'bad crypto' (wtf that would be). > > > > The chair has additional support of and protection from being a corporate > > > > officer of the ASF. But it's simplest for all if others can help the > > > > chair by updating license/exports/index.html. That entry provides the > > > > chair with everything they need to know to fire off that notice. > > > > > > Hmm, the chair just got back from his honeymoon and lab's crypto was not > > > exactly very high on his priority list. > > > > > > :) congrats! I understand about priorities... > > > > > > > > > > So, what email are we talking about? > > > > > > > > > I was asking for specifics about incubator, in the email you quote. But > > in the case being discussed here, BadCA and vysper are using encryption > > technologies, so the procedure at > > > > https://svn.apache.org/repos/asf/infrastructure/site/trunk/xdocs/licenses/exports/index.xml > > > > should be followed, as Bernd Fondermann pointed Apr 29th in the email > > that started this thread. > > > > Bertrand Delacretaz pointed at > > > > https://issues.apache.org/jira/browse/TIKA-118 > > > > to see the whole procedure outlined. > > > > Basically the work involved is: > > * assessment of the crypto used > > * NOTICE in the lab code with the details > > AFAIK, the notice does not normally go in the NOTICE file (which is > for attributions only), but in a README file. > > > > * adding notes to the first URL (Bernd's email) > > * the chair sending an email to whatever authority pointing them to the > > URLs. > > > > Regards > > Santiago > > > > -- > > > > Santiago Gala > > http://memojo.com/~sgala/blog/ > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: labs-unsubscribe@... > > For additional commands, e-mail: labs-help@... > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: labs-unsubscribe@... > For additional commands, e-mail: labs-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
Re: crypto statement revisited |