From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: ltp-list@lists.sf.net, haradats@nttdata.co.jp, sds@tycho.nsa.gov,
casey@schaufler-ca.com, serue@linux.vnet.ibm.com,
zohar@linux.vnet.ibm.com, takedakn@nttdata.co.jp
Subject: Re: [LTP] [003][RFC] [TESTING linux-2.6.30] TOMOYO Linux and pathname-basedsecurity
Date: Tue, 16 Jun 2009 00:46:26 +0530 [thread overview]
Message-ID: <1245093386.4871.49.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <200906142044.ACJ21831.VHOJSFLtFOQOFM@I-love.SAKURA.ne.jp>
On Sun, 2009-06-14 at 20:44 +0900, Tetsuo Handa wrote:
> Hello.
>
> Sorry for late response. I had no internet access for three days.
>
> Subrata Modak wrote:
> > We would like to inform you that we have some robust sets of testcases
> > for both SELinux, SMACK, IMA, etc at
> > http://ltp.cvs.sourceforge.net/viewvc/ltp/ltp/testcases/kernel/security/.
> > And i would express to have TOMYO being tested through LTP. If you agree
> > to contribute some test cases in this regard to LTP under GPLv2, we can
> > make a modest but great beginning. What do you say ?
>
> Yes, we are willing to contribute TOMOYO's test cases to LTP.
Great to hear that.
> Currently, we are using testing programs available at
> http://sourceforge.jp/projects/tomoyo/svn/view/trunk/1.6.x/ccs-tools/ccstools/kernel_test/?root=tomoyo
> But they are not some shell scripting programs.
> Thus, I need to remake these programs to follow LTP conventions.
> Can I have some documentation regarding how to write LTP testing programs?
Sure. Why not. Please see:
http://ltp.sourceforge.net/
http://ltp.sourceforge.net/documentation/how-to/ltp.php
http://ltp.sourceforge.net/documentation/technical_papers/
Regards--
Subrata
>
> Regards.
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-06-15 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 2:53 [LTP] [003][RFC] [TESTING linux-2.6.30] TOMOYO Linux and pathname-based security Subrata Modak
2009-06-14 11:44 ` [LTP] [003][RFC] [TESTING linux-2.6.30] TOMOYO Linux and pathname-basedsecurity Tetsuo Handa
2009-06-15 19:16 ` Subrata Modak [this message]
2009-06-18 17:31 ` Subrata Modak
2009-06-19 6:37 ` Tetsuo Handa
2009-06-23 14:50 ` Subrata Modak
2009-06-23 10:53 ` [LTP] [003][RFC] [TESTING linux-2.6.30] TOMOYO Linux andpathname-basedsecurity Tetsuo Handa
2009-06-23 14:50 ` Subrata Modak
2009-06-24 10:44 ` [LTP] [003][RFC] [TESTING linux-2.6.30] TOMOYO Linuxandpathname-basedsecurity Tetsuo Handa
2009-06-25 9:10 ` Subrata Modak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1245093386.4871.49.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=casey@schaufler-ca.com \
--cc=haradats@nttdata.co.jp \
--cc=ltp-list@lists.sf.net \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sds@tycho.nsa.gov \
--cc=serue@linux.vnet.ibm.com \
--cc=takedakn@nttdata.co.jp \
--cc=zohar@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox