----- "Simone Tripodi" <simonetrip...@apache.org> a écrit :
> Salut Luc!!! > I have to admit my ignorance respect the "export regulations in the > US", that's completely new to me, thanks for notifying! The status of Apache projects with respect to export status can be found here: <http://www.apache.org/licenses/exports/>. This page is intended for our users. The page that developers and PMC should check *even before committing anything* to make sure we are compliant with regulations is here: <http://www.apache.org/dev/crypto.html>. Luc > Simo > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > > > On Sun, Jan 2, 2011 at 8:59 PM, Luc Maisonobe <luc.maison...@free.fr> > wrote: > > Le 02/01/2011 20:52, Simone Tripodi a écrit : > >> Hi all guys, > >> I'm a big fan of how Maven manages passwords (en|de)cription[1] > and > >> found the algorithm implementation[2] on Sonatype's repo. > >> Since the code is released under AFL2.0, what about including this > >> algorithm in codec component? > >> I can provide an implementation but Cipher interface is quite > >> different from existing codec interfaces, since (en|de)cription > >> methods require a master password... > >> Thoughts? > >> Many thanks in advance, have a nice day! > > > > I think implementing this kind of feature would change the status > of > > [codec] with respect to export regulations in the US. As far as I > know, > > no commons component implement anything related to cryptography so > we > > can point people to a generic declaration we have already written > > somewhere when they ask for our components status. > > > > It may be good to add, but we have to think about it thoroughly. > > > > Luc > > > >> Simo > >> > >> [1] http://maven.apache.org/guides/mini/guide-encryption.html > >> [2] http://svn.sonatype.org/spice/trunk/plexus-cipher > >> > >> http://people.apache.org/~simonetripodi/ > >> http://www.99soft.org/ > >> > >> > --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> For additional commands, e-mail: dev-h...@commons.apache.org > >> > >> > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
