I'd like to submit the Unofficial Security Spin concept on behalf of both Luke Macken and myself. It was Luke's original idea and a large amount of the work is to be attributed to him, I came into the project late in the game and did some cleanup work to bring the kickstart up to date to compose against current repositories as well as package and add a couple of packages. As Luke is quite busy with many other aspects of the Fedora Project I am the one submitting the work for review.
Summary: The Fedora Security Spin is geared towards the security and digital forensics crowd with the goal of providing a fully functional livecd based on Fedora for use in security auditing, forensics, and penetration testing.
The Spin features a custom Openbox menu in order to group together different tools for use by the end user based on category, which can be seen from the screenshot on the page listed on the wiki page (listed below).
SecuritySpin Wiki page: https://fedoraproject.org/wiki/SecuritySpin Kickstart: http://maxamillion.fedorapeople.org/fedora-livecd-security.ks
-Adam
On Mon, Jul 20, 2009 at 05:24:03PM -0500, Adam Miller wrote:
I'd like to submit the Unofficial Security Spin concept on behalf of both Luke Macken and myself. It was Luke's original idea and a large amount of the work is to be attributed to him, I came into the project late in the game and did some cleanup work to bring the kickstart up to date to compose against current repositories as well as package and add a couple of packages. As Luke is quite busy with many other aspects of the Fedora Project I am the one submitting the work for review.
Summary: The Fedora Security Spin is geared towards the security and digital forensics crowd with the goal of providing a fully functional livecd based on Fedora for use in security auditing, forensics, and penetration testing.
The Spin features a custom Openbox menu in order to group together different tools for use by the end user based on category, which can be seen from the screenshot on the page listed on the wiki page (listed below).
SecuritySpin Wiki page: https://fedoraproject.org/wiki/SecuritySpin Kickstart: http://maxamillion.fedorapeople.org/fedora-livecd-security.ks
I'm really pleased to see this spin proposal making its way out into the world at long last! In accordance with the usual process, I'm looking forward to seeing this on the Board's docket for trademark approval so we can make it part of the F12 release if possible.
Adam Miller (maxamillion@gmail.com) said:
The Spin features a custom Openbox menu in order to group together different tools for use by the end user based on category, which can be seen from the screenshot on the page listed on the wiki page (listed below).
Not that it's a blocker, but is there a reason you're using OpenBox? Is it simply space?
Bill
On Tue, Jul 21, 2009 at 9:49 AM, Bill Nottinghamnotting@redhat.com wrote:
Not that it's a blocker, but is there a reason you're using OpenBox? Is it simply space?
<SNIP>
Preference really, we discussed using Xfce but decided to stick with OpenBox.
-Adam
On Tue, Jul 21, 2009 at 10:49:01AM -0400, Bill Nottingham wrote:
Adam Miller (maxamillion@gmail.com) said:
The Spin features a custom Openbox menu in order to group together different tools for use by the end user based on category, which can be seen from the screenshot on the page listed on the wiki page (listed below).
Not that it's a blocker, but is there a reason you're using OpenBox? Is it simply space?
No, it's not simply space, although that is a convenient benefit. When performing a security audit, forensic analysis, pentest, etc, you do not usually need or want full desktop environment. Therefore, we wanted to keep this spin as minimal as possible. Openbox solves this for us, and also made it simple to create a custom right-click menu containing all of the tools that we ship.
luke
On 07/21/2009 04:49 PM, Bill Nottingham wrote:
Adam Miller (maxamillion@gmail.com) said:
The Spin features a custom Openbox menu in order to group together different tools for use by the end user based on category, which can be seen from the screenshot on the page listed on the wiki page (listed below).
Not that it's a blocker, but is there a reason you're using OpenBox?
Concerning the use of OpenBox (for which the reasons seem obvious as explained elsewhere in this thread);
- How robust is OpenBox in rawhide, given the various commands in %post? Does any of this fail every once in a while or not at all?
Kind regards,
Jeroen van Meeuwen -kanarip
Am Mittwoch, den 22.07.2009, 14:57 +0200 schrieb Jeroen van Meeuwen:
On 07/21/2009 04:49 PM, Bill Nottingham wrote:
Adam Miller (maxamillion@gmail.com) said:
The Spin features a custom Openbox menu in order to group together different tools for use by the end user based on category, which can be seen from the screenshot on the page listed on the wiki page (listed below).
Not that it's a blocker, but is there a reason you're using OpenBox?
Concerning the use of OpenBox (for which the reasons seem obvious as explained elsewhere in this thread);
- How robust is OpenBox in rawhide, given the various commands in %post?
The commands look ugly to me. IMO the way to go is:
1. create a security-menus package (just like electronics-menus or multimedia-menus) 2. use openbox's xdg-menu commend to generate a menu from the package on the fly.
Sounds reasonable?
Kind regards,
Jeroen van Meeuwen -kanarip
Regards, Christoph
On 07/22/2009 06:54 PM, Christoph Wickert wrote:
Am Mittwoch, den 22.07.2009, 14:57 +0200 schrieb Jeroen van Meeuwen:
On 07/21/2009 04:49 PM, Bill Nottingham wrote:
Adam Miller (maxamillion@gmail.com) said:
The Spin features a custom Openbox menu in order to group together different tools for use by the end user based on category, which can be seen from the screenshot on the page listed on the wiki page (listed below).
Not that it's a blocker, but is there a reason you're using OpenBox?
Concerning the use of OpenBox (for which the reasons seem obvious as explained elsewhere in this thread);
- How robust is OpenBox in rawhide, given the various commands in %post?
The commands look ugly to me. IMO the way to go is:
1. create a security-menus package (just like electronics-menus or multimedia-menus) 2. use openbox's xdg-menu commend to generate a menu from the package on the fly.
Sounds reasonable?
That would be way better than WM specific hacks.
Rahul
On Wed, Jul 22, 2009 at 8:24 AM, Christoph Wickertchristoph.wickert@googlemail.com wrote: How robust is OpenBox in rawhide, given the various commands in %post?
The commands look ugly to me. IMO the way to go is:
1. create a security-menus package (just like electronics-menus or multimedia-menus) 2. use openbox's xdg-menu commend to generate a menu from the package on the fly.
Sounds reasonable?
<snip>
Would there really be much need for a package that would contain some menu entries that would only be used in the spin when its easily just put in the kickstart for the WM that is planned to be used for the spin?
I just don't see the benefit of creating and maintaining a separate package that is probably only going to be used for this spin since the menus will be specific to the packages shipped in the spin anyway.
-Adam
On Fri, 2009-07-24 at 08:49 -0500, Adam Miller wrote:
Would there really be much need for a package that would contain some menu entries that would only be used in the spin when its easily just put in the kickstart for the WM that is planned to be used for the spin?
I just don't see the benefit of creating and maintaining a separate package that is probably only going to be used for this spin since the menus will be specific to the packages shipped in the spin anyway.
Stuffing configuration in the ks is really a last ditch effort. Your spin should be usable if it were installed as part of a normal install process, rather than just from a live image. You should keep as much configuration as possible in packages rather than the kickstart.