Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Tor-ramdisk 20090125 (MIPS Port branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Tor-ramdisk 20090125 (MIPS Port branch)
# 1  
Old 01-25-2009
Tor-ramdisk 20090125 (MIPS Port branch)
Tor-ramdisk is an i686 uClibc-based micro Linux distribution whose only purpose is to host a Tor server in an environment that maximizes security and privacy. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. Security is enhanced in tor-ramdisk by employing a monolithically compiled GRSEC/PAX patched kernel and hardened system tools. Privacy is enhanced by turning off logging at all levels so that even the Tor operator only has access to minimal information. Finally, since everything runs in ephemeral memory, no information survives a reboot, except for the Tor configuration file and the private RSA key, which may be exported/imported by FTP. License: GNU General Public License v3 Changes:
This initial port of tor-ramdisk to the MIPS architecture has only been tested in a QEMU emulated environment, but is functional despite known issues. Its is built using tor-0.2.0.33, busybox-1.13.2, and linux-2.6.18.6. Unlike the default branch, binaries are statically linked against glibc, and a vanilla kernel is employed. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT SUNOS

pseudo

pseudo(4)							   File Formats 							 pseudo(4)

NAME

       pseudo - configuration files for pseudo device drivers

DESCRIPTION

       Pseudo devices are devices that are implemented entirely in software. Drivers for pseudo devices must provide driver configuration files to
       inform the system of each pseudo device that should be created.

       Configuration files for pseudo device drivers must identify the parent driver explicitly as pseudo, and must  create  an  integer  property
       called instance which is unique to this entry in the configuration file.

       Each  entry in the configuration file creates a prototype devinfo node. Each node is assigned an instance number which is determined by the
       value of the instance property.	This property is only applicable to children of the pseudo parent, and is required  since  pseudo  devices
       have no hardware address from which to determine the instance number. See driver.conf(4) for further details of configuration file syntax.

EXAMPLES

       Example 1: A sample configuration file.

       Here  is a configuration file called ramdisk.conf for a pseudo device driver that implements a RAM disk. This file creates two nodes called
       "ramdisk". The first entry creates ramdisk node instance 0, and the second creates ramdisk node, instance 1, with the additional  disk-size
       property set to 512.

       #
       # Copyright (c) 1993, by Sun Microsystems, Inc.
       #
       #ident  "@(#)ramdisk.conf       1.3     93/06/04 SMI"
       name="ramdisk" parent="pseudo" instance=0;
       name="ramdisk" parent="pseudo" instance=1 disk-size=512;

SEE ALSO

       driver.conf(4), ddi_prop_op(9F)

       Writing Device Drivers

SunOS 5.10							    15 Jun 1993 							 pseudo(4)