Quoting Ben Laurie ([EMAIL PROTECTED]):
> Ralf S. Engelschall wrote:
> >
> > In article <[EMAIL PROTECTED]> you wrote:
> > > Josh MacDonald wrote:
> >
> > >> The system will use authentication only, built upon the openssl library,
> > >> which is available from outside the U.S. Though SSL contains support for
> > >> encryption, it will be disabled by selecting a NULL encryption cipher
> > >> (which uses only a MAC, no confidentiality). It is our belief that since
> > >> PRCS will not itself contain any crypto code, and since it is only
> > >> uses authication, it will not be classified as an Encryption Item, and
> > >> it can be freely exported. I will obtain a formal opinion statement from
> > >> another lawyer (my next legal fee) before going too far, for protection in
> > >> case the BXA makes any action.
> > >
> > > I'm sure everyone except me knows, but, errr, what is PRCS?
> >
> > It's a repository system similar to CVS, Ben.
> > You can have a look at it under the following locations:
> > http://www.XCF.Berkeley.EDU/~jmacd/prcs.html
> > ftp://XCF.Berkeley.EDU/pub/prcs/
>
> Ah, yes, I have looked at it before. ETLA overload. I have to say that
> my main reaction was "why?".
If your question is why PRCS, the answer is because there are numerous
fundamental errors in the design of CVS that needed correction. There
is a complete description in ftp://ftp.xcf.berkeley.edu/pub/prcs/scm98.ps.
The new client/server version also features multiple, replicant servers
and hierarchical storage allowing users to create local branches without
sharing them with the entire user community.
-josh
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
