Hi, seedit-devel list subscribers.
I am Yuichi, developer of SELinux Policy Editor.
I have not used this list for some months..
I had been busy moving from US to Japan,
so I have forgotten about the list.. I am sorry.
I would like to use this list to announce update, and obtain feedback.
I would like to report current project status.
1) Testing Version 2.1
I am testing seedit 2.1.
Current version is 2.1-b3.
It works on Fedora Core6.
You can download and try it from seedit.sourceforge.net .
Improvement in 2.1 will be..
- Update for kernel 2.6.18.
-Add allowkey to control access to key subsystem.
- Add dummy rules for secmark. Current seedit does not support secmark.
- Minimum MCS support(Only controls file access)
- Generate modulrar policy
- Improved policy generation tool
- Performance improvement
- Policy generation for applications that use chroot system call.
-- In 2.0, policy generation failed for apps using chroot.
- Icon update
2) Added Mr. Shane Martin Coughlan to SELinux Policy Editor team.
I heard from him that he is willing to help SELinux Policy Editor project.
And he contributed to project
by creating homepage,refining language,icons in seedit.
So I add his name to SELinux Policy Editor team.
3) New English website launched
Mr. Coughlan created new web page, so web page was updated.
And I am considering something like project road map..
By the way, I found an interesting post in fedora-selinux-list.
It seems that fedora developper is interested in seedit!
From: Shane Martin Coughlan <shane@op...> - 2006-10-30 09:35:50
Yuichi Nakamura wrote:
> 2) Added Mr. Shane Martin Coughlan to SELinux Policy Editor team.
> I heard from him that he is willing to help SELinux Policy Editor project.
> And he contributed to project
> by creating homepage,refining language,icons in seedit.
> So I add his name to SELinux Policy Editor team.
I'm Shane, and I'm delighted to be part of the project.
My main focus at the moment is in trying to make sure SELinux Policy
Editor is as easy to use as possible.
If anyone has any comments about their usability concerns or ideas it
would be great to hear them.