[Cryptography Team] Common Criteria Documentation...

[Kyle Hamilton]

For a wiki, we can try wikia.com... the subject matter may be too
specialized for them, though.

We could fairly easily make the wiki self-hosting, using the wiki
software in the Monticello repositories (I think SqueakSource, but not
entirely sure).

What kind of outlay can the Squeak Foundation afford for wiki hosting,
if necessary?

-Kyle H

On 10/16/06, Krishna Sankar <ksankar at doubleclix.net> wrote:
> I am still figuring out things with the Google project. By tomorrow cob,
> will see how we all can get SVN write access. BTW, for the records, the
> Google project is squeak-cc-validation
> http://code.google.com/p/squeak-cc-validation/.
>
> On the CC side, I think the major tasks are :
>
>         1.      Decide on the protection profile(s) we want to address
>
>         2.      Define the claims and security target
>
>                 Most probably we would need 3-4 configurations
>
>         3.      Start a function List and Test Matrix (Where can we host a
> Wiki?) (This will help us prove our case, so we should start this task ASAP)
>
>         4.      Develop the ToE
>
>         5.      Understand and document the cc process relevant to us. Read
> and mark the cc documents, talk with Labs et al
>
>         6.      Formal cc effort
>
> Kyle,  the cc documentation will help us in these tasks. I will add these
> tasks and will start double-clicking task #1.
>
> Cheers
> <k/>
>
> > -----Original Message-----
> > From: cryptography-bounces at lists.squeakfoundation.org
> > [mailto:cryptography-bounces at lists.squeakfoundation.org] On
> > Behalf Of Kyle Hamilton
> > Sent: Monday, October 16, 2006 8:33 PM
> > To: Cryptography Team Development List
> > Subject: [Cryptography Team] Common Criteria Documentation...
> >
> > I found the Google Code project that Krishna started, and
> > uploaded the Common Criteria documentation I found (in PDF
> > form) to it as an issue.
> >  Unfortunately, I don't have SVN write access, and I don't
> > know how to get it either.
> >
> > After reading it, I realized that it /IS/ a good idea for
> > anyone starting on CC validation to read it before they
> > start.  It's important to realize what it is, and what the
> > goals must be.  (As well, it also helps customers -- that'd
> > include you, Ron -- understand what the various validation
> > levels are, and compare them to regulatory
> > requirement.)
> >
> > --
> >
> > -Kyle H
> > I speak only for myself.  I don't have the faintest clue
> > about anyone else.
> > _______________________________________________
> > Cryptography mailing list
> > Cryptography at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cry
> ptography
> >
>
> _______________________________________________
> Cryptography mailing list
> Cryptography at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cryptography
>


-- 

-Kyle H