lids
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 7
LIDS 2.2.3 RC1 (for kernel 2.6.21)
LIDS (Linux Intrusion Detection System) is a kernel patch and admin tools which enhances the kernels security. more>>
LIDS (Linux Intrusion Detection System) is a kernel patch and admin tools which enhances the kernels security by implementing Mandatory Access Control (MAC).
When it is in effect, chosen file access, all system network administration operations, any capability use, raw device, memory, and I/O access can be made impossible even for root. You can define which programs can access specific files.
It uses and extends the system capabilities bounding set to control the whole system and adds some network and filesystem security features to the kernel to enhance the security.
You can finely tune the security protections online, hide sensitive processes, receive security alerts through the network, and more. LIDS currently support kernel 2.6, 2.4.
<<lessWhen it is in effect, chosen file access, all system network administration operations, any capability use, raw device, memory, and I/O access can be made impossible even for root. You can define which programs can access specific files.
It uses and extends the system capabilities bounding set to control the whole system and adds some network and filesystem security features to the kernel to enhance the security.
You can finely tune the security protections online, hide sensitive processes, receive security alerts through the network, and more. LIDS currently support kernel 2.6, 2.4.
Download (0.30MB)
Added: 2007-08-15 License: GPL (GNU General Public License) Price:
801 downloads
ADIOSKIDS 1.0
ADIOSKIDSADIOS boot CD is a Fedora-based live and installation CD with support for User Mode Linux (UML) virtual machines. more>>
ADIOSKIDS is a Fedora-based live and installation CD with support for User Mode Linux (UML) virtual machines, further enhanced by Linux Intrusion Detection System (LIDS) and SELinux (Security Enhanced Linux). The live CD, which includes the KDE desktop environment, uses a compressed loopback filesystem.
The objective of the ADIOS project is to quickly and easily download a consistent operating system environment onto laboratory PCs. The ADIOS environment provides students with administrative privileges required to perform advanced exercises in Network and Systems Administration.
We needed a way to download a pre-installed version of the operating system onto the PC in the laboratory. There are many tools available to do this, but the ADIOS project uses a web server to deliver the Operating System images.
The ADIOS setup image is used to install operating systems onto disk partitions. It also copies the OS images from disk to disk to reduce network traffic. The ADIOS image was ported onto CDROM for students to use at home.
ADIOS-SELinux is a separate boot CD for running NSA Security Enhanced Linux. Additional software is available on the DVD version of ADIOS.
<<lessThe objective of the ADIOS project is to quickly and easily download a consistent operating system environment onto laboratory PCs. The ADIOS environment provides students with administrative privileges required to perform advanced exercises in Network and Systems Administration.
We needed a way to download a pre-installed version of the operating system onto the PC in the laboratory. There are many tools available to do this, but the ADIOS project uses a web server to deliver the Operating System images.
The ADIOS setup image is used to install operating systems onto disk partitions. It also copies the OS images from disk to disk to reduce network traffic. The ADIOS image was ported onto CDROM for students to use at home.
ADIOS-SELinux is a separate boot CD for running NSA Security Enhanced Linux. Additional software is available on the DVD version of ADIOS.
Download (687.8MB)
Added: 2006-12-18 License: GPL (GNU General Public License) Price:
1040 downloads
XML User Profiles 0.2.3
XML User Profiles is a system that allows for remote and transferable user accounts. more>>
XUP is an attempt to replace static per-site user accounts, which most present dynamic web sites use in absence of an easy to use and open/shared user account system. It allows people to use a single account or profile with many sites, or one of their existing user profiles on multiple other web sites.
It is best suited to so called "community" sites, where the account serves mainly for lax identification of people among each other. It does not stipulate strong authentication (while OpenID or LID can be used) and is therefore only useful for applications with mediocre security and privacy demands.
Chat and discussion sites are the main target, but profiles in different applications can often also be enriched with them. They are meant to get used secondarily (as alternative) to static/local user accounts.
The XML format of user profiles is extremely simple, as is the associated login service API. Both are outlined and explained in the introduction (HTML). The format is basically an XMLified vCard with a few additions targetted at online/web communities. It is easy to parse and generate and therefore also suitable for profile exchange or import.
Theres also a more authoritative RFC-style text version of the current proposal, which provides further hints and explanations for implementors. Future extensions will get listed in the project Wiki however (field names in the XUP format are not regulated).
This effort is quite new, and therefore only very few actual (real-world) implementations are known so far.
Some software, like discussion boards (which mostly suffer from spaghetti code), are of course hard to extent with XML User Profiles. Even those that abstract their internal user database and UI logic reasonably well can often be difficult to adapt. It is however expected that the more professional systems will sooner than later be XUP compatible.
<<lessIt is best suited to so called "community" sites, where the account serves mainly for lax identification of people among each other. It does not stipulate strong authentication (while OpenID or LID can be used) and is therefore only useful for applications with mediocre security and privacy demands.
Chat and discussion sites are the main target, but profiles in different applications can often also be enriched with them. They are meant to get used secondarily (as alternative) to static/local user accounts.
The XML format of user profiles is extremely simple, as is the associated login service API. Both are outlined and explained in the introduction (HTML). The format is basically an XMLified vCard with a few additions targetted at online/web communities. It is easy to parse and generate and therefore also suitable for profile exchange or import.
Theres also a more authoritative RFC-style text version of the current proposal, which provides further hints and explanations for implementors. Future extensions will get listed in the project Wiki however (field names in the XUP format are not regulated).
This effort is quite new, and therefore only very few actual (real-world) implementations are known so far.
Some software, like discussion boards (which mostly suffer from spaghetti code), are of course hard to extent with XML User Profiles. Even those that abstract their internal user database and UI logic reasonably well can often be difficult to adapt. It is however expected that the more professional systems will sooner than later be XUP compatible.
Download (0.23MB)
Added: 2005-07-08 License: GPL (GNU General Public License) Price:
1570 downloads
IO::Util 1.5
IO::Util is a selection of general-utility IO function. more>>
IO::Util is a selection of general-utility IO function.
SYNOPSIS
use IO::Util qw(capture slurp Tid Lid Uid load_mml);
capture()
# captures the selected filehandle
$output_ref = capture { any_printing_code() } ;
# now $$output_ref eq something
# captures FILEHANDLE
$output_ref = capture { any_special_printing_code() } *FILEHEANDLER ;
# append the output to $captured
capture { any_printing_code() } *FILEHEANDLER , $captured
# now $captured eq something
# use another class to tie the handler
use IO::Scalar ;
$IO::Util::TIE_HANDLE_CLASS = IO::Scalar
slurp()
$_ = /path/to/file ;
$content_ref = slurp ;
$content_ref = slurp /path/to/file ;
$content_ref = slurp *FILEHANDLE ;
# append the file content to $content
$_ = /path/to/file ;
slurp $content;
slurp /path/to/file, $content ;
slurp *FILEHANDLE, $content ;
Tid(), Lid(), Uid()
$temporarily_unique_id = Tid ; # Q9MU1N_NVRM
$locally_unique_id = Lid ; # 2MS_Q9MU1N_P5F6
$universally_unique_id = Uid ; # MGJFSBTK_2MS_Q9MU1N_PWES
A MML file (Minimal Markup Language)
< opt >
< !-- a multi line
comment-- >
< parA >
< optA >01< /optA >
< optA >02< /optA >
< optA >03< /optA >
< /parA >
< parB >
< optA >04< /optA >
< optA >05< /optA >
< optA >06< /optA >
< optB >
< key >any key< /key >
< /optB >
< /parB >
< /opt >
load_mml()
$struct = load_mml path/to/mml_file ;
$struct = load_mml $mml_string ;
$struct = load_mml *MMLFILE ;
$struct = load_mml ..., %options ;
# $struct = {
# parA => {
# optA => [
# 01,
# 02,
# 03
# ]
# },
# parB => {
# optA => [
# 04,
# 05,
# 06
# ],
# optB => {
# key => any key
# }
# }
# }
<<lessSYNOPSIS
use IO::Util qw(capture slurp Tid Lid Uid load_mml);
capture()
# captures the selected filehandle
$output_ref = capture { any_printing_code() } ;
# now $$output_ref eq something
# captures FILEHANDLE
$output_ref = capture { any_special_printing_code() } *FILEHEANDLER ;
# append the output to $captured
capture { any_printing_code() } *FILEHEANDLER , $captured
# now $captured eq something
# use another class to tie the handler
use IO::Scalar ;
$IO::Util::TIE_HANDLE_CLASS = IO::Scalar
slurp()
$_ = /path/to/file ;
$content_ref = slurp ;
$content_ref = slurp /path/to/file ;
$content_ref = slurp *FILEHANDLE ;
# append the file content to $content
$_ = /path/to/file ;
slurp $content;
slurp /path/to/file, $content ;
slurp *FILEHANDLE, $content ;
Tid(), Lid(), Uid()
$temporarily_unique_id = Tid ; # Q9MU1N_NVRM
$locally_unique_id = Lid ; # 2MS_Q9MU1N_P5F6
$universally_unique_id = Uid ; # MGJFSBTK_2MS_Q9MU1N_PWES
A MML file (Minimal Markup Language)
< opt >
< !-- a multi line
comment-- >
< parA >
< optA >01< /optA >
< optA >02< /optA >
< optA >03< /optA >
< /parA >
< parB >
< optA >04< /optA >
< optA >05< /optA >
< optA >06< /optA >
< optB >
< key >any key< /key >
< /optB >
< /parB >
< /opt >
load_mml()
$struct = load_mml path/to/mml_file ;
$struct = load_mml $mml_string ;
$struct = load_mml *MMLFILE ;
$struct = load_mml ..., %options ;
# $struct = {
# parA => {
# optA => [
# 01,
# 02,
# 03
# ]
# },
# parB => {
# optA => [
# 04,
# 05,
# 06
# ],
# optB => {
# key => any key
# }
# }
# }
Download (0.014MB)
Added: 2006-09-12 License: Perl Artistic License Price:
1137 downloads
tclkeymon 0.52
tclkeymon is a Toshiba TCL Key and button monitor. more>>
Tclkeymon is a daemon for Toshiba laptops that use ACPI and the Toshiba ACPI extensions.
The project monitors function keys and Toshiba-specific buttons (including the CD player buttons and the state of the laptop lid) and responds appropriately.
<<lessThe project monitors function keys and Toshiba-specific buttons (including the CD player buttons and the state of the laptop lid) and responds appropriately.
Download (0.022MB)
Added: 2006-12-04 License: GPL (GNU General Public License) Price:
1054 downloads
POE::Component::Audio::Mad::Dispatch 0.3
POE::Component::Audio::Mad::Dispatch is a POE::Component::Audio::Mad frontend implementing listener based message dispatch. more>>
POE::Component::Audio::Mad::Dispatch is a POE::Component::Audio::Mad frontend implementing listener based message dispatch.
SYNOPSIS
use POE;
use POE::Component::Audio::Mad::Dispatch;
## we print some stuff below, and we dont want it
## to get buffered.. so turn on autoflush.
$| = 1;
## create our frontend session, which will create a decoder and
## forward its messages to all interested listeners..
create POE::Component::Audio::Mad::Dispatch({
decoder_play_on_open => 1,
alias => mad-decoder
});
POE::Session->create(inline_states => {
_start => &ex_start,
mad_decoder_input => &ex_input
});
sub ex_start {
my ($kernel, $heap, $session) = @_[KERNEL, HEAP, SESSION];
## add ourself in as a listener, and register for the DECODER_FRAME_DATA and
## IPC_SHUTDOWN_SUCCESS events. The decoder core will then call the
## mad_decoder_input state in the current session when these
## events arrive..
## this also has the added benefit of keeping a reference to our
## session alive in the event notification list. Our session will
## remain alive as long as we are a registered listener..
$heap->{lid} = $kernel->call(mad-decoder, add_listener, $session, mad_decoder_input, [
DECODER_FRAME_DATA, INPUT_EOF_WARNING
]);
## tell our decoder to start playing a stream..
$kernel->post(mad-decoder, decoder_open, { filename => /path/to/stream.mp3, play => 1 });
}
sub ex_input {
my ($kernel, $heap, $msg) = @_[KERNEL, HEAP, ARG0];
## this is called when the decoder has generated an event
## that we have registered for. the message packet is
## contained in ARG0, and is a hashref with two
## fields ->{id} and ->{data}. id specifies the name
## of the event, and data contains a reference to
## the data included in this event..
if ($msg->{id} eq DECODER_FRAME_DATA) {
## we got a message updating us as to player
## progress, the data part of the event will
## contain two values: ->{played} and ->{progress},
## played is the number of seconds of stream
## played..
print "rplayed: $msg->{data}->{played}" if (defined($msg->{data}->{played}));
} elsif ($msg->{id} eq INPUT_EOF_WARNING) {
## we got a message telling us that the
## decoder system has come to the end of
## the current stream, use it as a queue
## to shutdown..
print "nshutting down..n";
$kernel->post(mad-decoder, decoder_shutdown);
} else {
## unknown messages should never happen, but
## we could do something interesting with them
## here.. for simplicity, we just ignore it.
return;
}
}
## start this thing..
$poe_kernel->run();
exit();
POE::Component::Audio::Mad::Dispatch implements a multiple dispatch front end component for the POE::Wheel::Audio::Mad mpeg decoder. It receieves status messages from the decoder and dispatches them to other registered "listener" sessions. All of the states listed in POE::Wheel::Audio::Mad(3) under STATES will be defined within this components session. To control the decoder, simply post the appropriate POE::Wheel::Audio::Mad STATE to this session.
If you intend to implement a decoder that will be controlled and/or monitored by other POE::Sessions, then this is the module you want to be using. If you wish to implement a decoder through an IPC bridge, you want POE::Component::Audio::Mad::Handle.
<<lessSYNOPSIS
use POE;
use POE::Component::Audio::Mad::Dispatch;
## we print some stuff below, and we dont want it
## to get buffered.. so turn on autoflush.
$| = 1;
## create our frontend session, which will create a decoder and
## forward its messages to all interested listeners..
create POE::Component::Audio::Mad::Dispatch({
decoder_play_on_open => 1,
alias => mad-decoder
});
POE::Session->create(inline_states => {
_start => &ex_start,
mad_decoder_input => &ex_input
});
sub ex_start {
my ($kernel, $heap, $session) = @_[KERNEL, HEAP, SESSION];
## add ourself in as a listener, and register for the DECODER_FRAME_DATA and
## IPC_SHUTDOWN_SUCCESS events. The decoder core will then call the
## mad_decoder_input state in the current session when these
## events arrive..
## this also has the added benefit of keeping a reference to our
## session alive in the event notification list. Our session will
## remain alive as long as we are a registered listener..
$heap->{lid} = $kernel->call(mad-decoder, add_listener, $session, mad_decoder_input, [
DECODER_FRAME_DATA, INPUT_EOF_WARNING
]);
## tell our decoder to start playing a stream..
$kernel->post(mad-decoder, decoder_open, { filename => /path/to/stream.mp3, play => 1 });
}
sub ex_input {
my ($kernel, $heap, $msg) = @_[KERNEL, HEAP, ARG0];
## this is called when the decoder has generated an event
## that we have registered for. the message packet is
## contained in ARG0, and is a hashref with two
## fields ->{id} and ->{data}. id specifies the name
## of the event, and data contains a reference to
## the data included in this event..
if ($msg->{id} eq DECODER_FRAME_DATA) {
## we got a message updating us as to player
## progress, the data part of the event will
## contain two values: ->{played} and ->{progress},
## played is the number of seconds of stream
## played..
print "rplayed: $msg->{data}->{played}" if (defined($msg->{data}->{played}));
} elsif ($msg->{id} eq INPUT_EOF_WARNING) {
## we got a message telling us that the
## decoder system has come to the end of
## the current stream, use it as a queue
## to shutdown..
print "nshutting down..n";
$kernel->post(mad-decoder, decoder_shutdown);
} else {
## unknown messages should never happen, but
## we could do something interesting with them
## here.. for simplicity, we just ignore it.
return;
}
}
## start this thing..
$poe_kernel->run();
exit();
POE::Component::Audio::Mad::Dispatch implements a multiple dispatch front end component for the POE::Wheel::Audio::Mad mpeg decoder. It receieves status messages from the decoder and dispatches them to other registered "listener" sessions. All of the states listed in POE::Wheel::Audio::Mad(3) under STATES will be defined within this components session. To control the decoder, simply post the appropriate POE::Wheel::Audio::Mad STATE to this session.
If you intend to implement a decoder that will be controlled and/or monitored by other POE::Sessions, then this is the module you want to be using. If you wish to implement a decoder through an IPC bridge, you want POE::Component::Audio::Mad::Handle.
Download (0.022MB)
Added: 2006-11-17 License: Perl Artistic License Price:
1071 downloads
GNOME Power Manager 2.18.3 / 2.19.6
GNOME Power Manager is a session daemon that takes care of power management. more>>
GNOME Power Manager gets all information from HAL using information from org.freedesktop.Hal. GNOME Power Manager does not do independent probing for data, it relies on HAL, in this way it can stay very lightweight and uncomplicated. GNOME Power Manager goal is to be architecture neutral and free of polling and other hacks.
Power management in Linux sucks. Depending if you are running a PPC or i386 PC the different power management facilities are vastly different. To get your machine to suspend on lid press is already possible, but is difficult to know what config files to modify.
To get your LCD screen brightness set to 50% when you remove the AC Adapter of your laptop is probably possible with a clever little Perl script, but is not something that comes ready configured on a standard Linux distro.
Any of these things need the user to become the super-user to do the action. This needs to change before Linux is accepted as a contender for the corporate desktop.
Main features:
- Laptop batteries
- AC Adapters
- APC UPSs
- SynCE PDAs
- Logitech Wireless Mice
- Logitech Wireless Keyboards
GNOME Power Manager owns the session D-BUS service net.sf.GnomePower and runs a session daemon (i.e. once per logged in user) and optionally displays battery status and low battery notifications.
The session daemon is very resource friendly. Other than the initial coldplug, it uses internal caching for all the power devices, so no additional lookups are needed for each update event. It will only update the displayed icon on a powerState change, but will update the tooltip on every percentage change. It should use *very little* CPU and memory.
<<lessPower management in Linux sucks. Depending if you are running a PPC or i386 PC the different power management facilities are vastly different. To get your machine to suspend on lid press is already possible, but is difficult to know what config files to modify.
To get your LCD screen brightness set to 50% when you remove the AC Adapter of your laptop is probably possible with a clever little Perl script, but is not something that comes ready configured on a standard Linux distro.
Any of these things need the user to become the super-user to do the action. This needs to change before Linux is accepted as a contender for the corporate desktop.
Main features:
- Laptop batteries
- AC Adapters
- APC UPSs
- SynCE PDAs
- Logitech Wireless Mice
- Logitech Wireless Keyboards
GNOME Power Manager owns the session D-BUS service net.sf.GnomePower and runs a session daemon (i.e. once per logged in user) and optionally displays battery status and low battery notifications.
The session daemon is very resource friendly. Other than the initial coldplug, it uses internal caching for all the power devices, so no additional lookups are needed for each update event. It will only update the displayed icon on a powerState change, but will update the tooltip on every percentage change. It should use *very little* CPU and memory.
Download (2.6MB)
Added: 2007-07-30 License: GPL (GNU General Public License) Price:
819 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above lids search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed