Free home remedy software for linux

mod_auth_remedy is an Apache module for HTTP Basic authentication/authorization in the Remedy Action Request System (ARS).

Users of the Remedy Action Request System are organized in groups as in UNIX. Each user may belong to several groups. Users log into server using passwords. ARS stores information in so-called schemas, an analogue of tables in a relational database. Schemas have records.

There is a schema named User storing user information such as Login Name and Password, one record for each user. This schema corresponds to /etc/passwd on UNIX. Another schema named Group stores information about groups - it is for ARS what /etc/group is for UNIX.

On HTTP request to a constrained URL, the browser supplies Apache with username and password typed in the Basic authentication box. The module opens connection to the Remedy server RemedyServer as user RemedyBindName with password RemedyBindPass, and seeks the User schema for record with Login Name equal to the browser-supplied username.

Only if the record exists and contains password that matches the browser-supplied password, the module tells Apache to let the user in. If RemedyBindName directive is < None >, the module attempts to log onto Remedy staighfoward with browser-supplied username/password and if this login succeeds, it lets to access the URL.

The User schema record contains list of groups the user belongs to. This list is compared to the content of the standard Require group directive in the authorization phase.

Directives

The module supports the following run-time configuration directives:

RemedyAuthoritative (On|Off)
whether other modules will attempt authentication (Off) or not (On)
RemedyServer
Remedy Action Request System server machine name
RemedyBindName
Remedy user login under which Apache can connect to the Remedy server. This Remedy user should have read permissions on the Password field in the User schema. When set to , Apache will use the login supplied by browser, i. e. login typed in in the auth box.
RemedyBindPass
password of the Remedy user. Set to when the previous is set to
RemedyAPILog (On|Off)
enables intensive logging of module operations.

Home Insurance Inventory Wizard is an free little program you can upload to your web site to add some extra functionality.
Home Insurance Inventory Wizard makes taking a home inventory for home insurance purposes extremely simple. And installing it is super easy, too. Best of all, its free!
Main features:
- Javascript and PHP-based for maximum compatibility
- The home inventory list expands as new rooms and items are added indefinitely. Can be useful for small apartments or large houses.
- Inventories can be saved by the user and downloaded, no databases needed!
- Home inventory lists can be uploaded by a user later so that they can make adjustments and add new items
- An HTML output option allows the user to create and then print a nicely formatted HTML version of their home inventory. Also includes option to add images of items.
- No adware, spyware or viruses
- The Home Insurance Inventory Wizard is absolutely FREE!

Gentoox Linux is an adaptation of the popular source based Linux distribution called Gentoo. Gentoox Home retains all the features of the original (portage, sysvinit etc...) but has a patch system created from the ground up, by myself, which is specifically designed for Gentoox.

"Magic" (as I have labelled it) allows users to install new software, upgrade their kernel and fix bugs. To learn more about magic, run "magic usage" once you have installed Gentoox.

Gentoox runs along side games - you get 3 choices during installation: E, F and Native. Both E and F create a loopback filesystem meaning that none of your drives are formatted during installation (except for cache partitions). If you choose "Native", then your F: partition is formatted to ReiserFS (making it inaccessible to Xbox applications).

Gentoox can be loaded via a .xbe file, or from a Cromwell based BIOS (which can be flashed to your modchip during installation). When using E or F installations, you are totally risk free - if you dont like Gentoox, simply delete all the files it installs (about 7 in total) and its gone.

There are three versions of Gentoox: Pro Edition, Home Edition and Media Center Edition. All three are 100% free and opensource, the difference between Home and Pro is that the Home Edition has many software packages preinstalled and preconfigured for instant usablity straight out of the box where as Pro doesnt even have a graphical user interface let alone any "useful" applications.

Pro is a bare minimum installation for booting the system, the entire customisation of the OS is left in the users hands with Pro. Media Center edition is more of a "Plugin" than a separate distribution. It allows you to have a Media Center along with Gentoox Home or Pro.

kearone provides icon pack for gnome based on my "kearones icons"
Version restrictions:
- think it could be improved with a more consistent Computer icon, and some black contour around the file type icons (just like the Home and Trash).

Apache Directory Server is an embeddable LDAP server implemented in pure Java.
Our primary vision (others also outlined below) is to build an enterprise directory server platform (and its components) where other Internet services snap in to store their data within the directory so they may be managed using LDAP.
From the image above youll see the architecture is designed so services besides LDAP like DNS, DHCP, SLP and Kerberos will snap in. Other services like UDDI can also be implemented and snapped in. These services will use a common networking layer and each can be toggled on and off according to the needs of the environment.
apseda, mina, or sedang are various frameworks used for the common network layer. These services share the common network layer and back their data within the Apache Directory Servers backing stores without any network latency or going through the LDAP line protocol. NTP btw is the only exception and its there to remedy the need for time sync for replication and other time sensitive protocols like kerberos. Its implementation here is intended to prevent any dependency on external infrastructure.
Main features:
- Designed as an LDAP and X.500 experimentation platform. Plugable components and subsystems make ApacheDS extremely modular and ideal for experiments with various aspects of the LDAP protocol.
- The servers frontend is completely separable from its backend and vice-versa making it very flexible for implementing virtual directories, proxy servers and gateways to X.500.
- Several backends can be implemented and plugged into the servers partition nexus. The server supports a BTree based partition out of the box but any backing store can be used to implement a partition so long as it conforms to interfaces.
- The server exposes aspects of administration via a special system backend. LDAP can be used to manage these concerns through the system naming context at ou=system.
- Java based triggers and stored procedures are being implemented.
- Both the backend subsystem and the frontend are separable and independently embeddable.
- The server contains a server side JNDI LDAP provider as the facade for the entire backend subsystem. JNDI operations are directly translated by this provider into operations against the nexus and the target partitions storing server entries.
- The server will use JNDI as the data access API for stored procedures. This will make stored procedures functional within and outside of the server without requiring recompilation.
- The servers networking code, MINA, Multipurpose Infrastructure for Network Applications was designed for pluggable protocol providers, of all sorts and not just LDAP. MINA gives ApacheDS the ability to handle large amounts of concurrency.
- The server uses the Snickers tools and APIs for ASN.1 BER encoding and decoding. These tools are designed for a very small encoding and decoding footprint as well as for use in non-blocking servers. The chunking nature of the BER codec makes the server very efficient while handling encoding and decoding making it more resistant to DoS attacks. This layer is also pluggable with a new experimental Twix provider which is much more efficient. Of course there is the unsupported Snacc4J provider which is no longer maintained.

File::Save::Home is a Perl module to place file safely under user home directory.

SYNOPSIS

use File::Save::Home qw(
get_home_directory
get_subhome_directory_status
make_subhome_directory
restore_subhome_directory_status
conceal_target_file
reveal_target_file
make_subhome_temp_directory
);

$home_dir = get_home_directory();

$desired_dir_ref = get_subhome_directory_status("desired/directory");

$desired_dir_ref = get_subhome_directory_status(
"desired/directory",
"pseudohome/directory", # two-argument version
);

$desired_dir = make_subhome_directory($desired_dir_ref);

restore_subhome_directory_status($desired_dir_ref);

$target_ref = conceal_target_file( {
dir => $desired_dir,
file => file_to_be_checked,
test => 0,
} );

reveal_target_file($target_ref);

$tmpdir = make_subhome_temp_directory();

$tmpdir = make_subhome_temp_directory(
"pseudohome/directory", # optional argument version
);

In the course of deploying an application on another users system, you sometimes need to place a file in or underneath that users home directory. Can you do so safely?

This Perl extension provides several functions which try to determine whether you can, indeed, safely create directories and files underneath a users home directory. Among other things, if you are placing a file in such a location only temporarily -- say, for testing purposes -- you can temporarily hide any already existing file with the same name and restore it to its original name and timestamps when you are done.