Free services for the blind software for linux

Secure Storage service for the gLite middleware project provides users with a set of tools to store in a secure way and in an encrypted format confidential data (e.g. medical or financial data) on the grid storage elements.
The data stored using the tools provided will be accessible and readable only by authorized users. Moreover, it solves the insider abuse problem preventing also the administrators of the storage elements to access the confidential data in a clear format.
The service has been designed and developed for the grid Middleware of the EGEE infrastructure, gLite, in the context of the TriGrid VL Project.
Secure Storage documentation generated with Doxygen are available.
Enhancements:
- A minor bug was fixed.

Configuration with no services supported script is for a single host firewall configuration with no services supported by the firewall machine itself.

Sample:

# USER CONFIGURABLE SECTION

# The name and location of the ipchains utility.
IPTABLES=iptables

# The path to the ipchains executable.
PATH="/usr/local/sbin"

# Our internal network address space and its supporting network device.
OURNET="10.5.0.0/24"
OURBCAST="10.5.0.255"
OURDEV="eth0"

# The outside address and the network device that supports it.
ANYADDR="0/0"
ANYDEV="ppp0"

# The TCP services we wish to allow to pass - "" empty means all ports
# note: comma separated
TCPIN="ssh,ftp,ftp-data"
TCPOUT="smtp,www,ssh,telnet,ftp,ftp-data,irc,http"

# The UDP services we wish to allow to pass - "" empty means all ports
# note: comma separated
UDPIN="domain"
UDPOUT="domain"

# The ICMP services we wish to allow to pass - "" empty means all types
# ref: /usr/include/netinet/ip_icmp.h for type numbers
# note: comma separated
ICMPIN="0,3,11"
ICMPOUT="8,3,11"

# Logging; uncomment the following line to enable logging of datagrams
# that are blocked by the firewall.
# LOGGING=1

# END USER CONFIGURABLE SECTION
####################################
# Flush the Input table rules
echo -n Flushing forward... && {
$IPTABLES -F FORWARD
} && echo done

# We want to deny incoming access by default.
# echo -n Denying incoming access... && {
# $IPTABLES -P FORWARD drop
# } && echo done

# Drop all datagrams destined for this host received from outside.
echo -n Dropping incoming datagrams... && {
$IPTABLES -A INPUT -i $ANYDEV -j DROP
} && echo done

# SPOOFING
# We should not accept any datagrams with a source address matching ours
# from the outside, so we deny them.
echo -n Preventing spoofing... && {
$IPTABLES -A FORWARD -s $OURNET -i $ANYDEV -j DROP
} && echo done

# SMURF
# Disallow ICMP to our broadcast address to prevent "Smurf" style attack.
echo -n Preventing SMURFs... && {
$IPTABLES -A FORWARD -p icmp -i $ANYDEV -d $OURNET -j DROP
} && echo done

# We should accept fragments, in iptables we must do this explicitly.
echo -n Accepting fragments... && {
$IPTABLES -A FORWARD -f -j ACCEPT
} && echo done

# TCP
# We will accept all TCP datagrams belonging to an existing connection
# (i.e. having the ACK bit set) for the TCP ports were allowing through.
# This should catch more than 95 % of all valid TCP packets.
echo -n Accepting valid incoming tcp datagrams on existing connections... && {
$IPTABLES -A FORWARD -m multiport -p tcp -d $OURNET --dports $TCPIN ! --tcp-flags SYN,ACK ACK -j ACCEPT
} && echo done
echo -n Accepting valid outgoing tcp datagrams on existing connections... && {
$IPTABLES -A FORWARD -m multiport -p tcp -s $OURNET --sports $TCPIN ! --tcp-flags SYN,ACK ACK -j ACCEPT
} && echo done

# TCP - INCOMING CONNECTIONS
# We will accept connection requests from the outside only on the
# allowed TCP ports.
echo -n Accepting incoming tcp connections on allowed ports... && {
$IPTABLES -A FORWARD -m multiport -p tcp -i $ANYDEV -d $OURNET --dports $TCPIN --syn -j ACCEPT
} && echo done

# TCP - OUTGOING CONNECTIONS
# We will accept all outgoing tcp connection requests on the allowed TCP ports.
echo -n Accepting outgoing traffic on allowed tcp ports... && {
$IPTABLES -A FORWARD -m multiport -p tcp -i $OURDEV -d $ANYADDR --dports $TCPOUT --syn -j ACCEPT
} && echo done

# UDP - INCOMING
# allow UDP datagrams in on the allowed ports and back.
echo -n Allowing UDP datagrams in on the allowed ports and back... && {
$IPTABLES -A FORWARD -m multiport -p udp -i $ANYDEV -d $OURNET --dports $UDPIN -j ACCEPT
$IPTABLES -A FORWARD -m multiport -p udp -i $ANYDEV -s $OURNET --sports $UDPIN -j ACCEPT
} && echo done

# UDP - OUTGOING
# We will allow UDP datagrams out to the allowed ports and back.
echo -n Allowing UDP datagrams out on the allowed ports and back... && {
$IPTABLES -A FORWARD -m multiport -p udp -i $OURDEV -d $ANYADDR --dports $UDPOUT -j ACCEPT
$IPTABLES -A FORWARD -m multiport -p udp -i $OURDEV -s $ANYADDR --sports $UDPOUT -j ACCEPT
} && echo done

# ICMP - INCOMING
# We will allow ICMP datagrams in of the allowed types.
# echo -n Allowing ICMP datagrams in of the allowed types... && {
# $IPTABLES -A FORWARD -p icmp -i $ANYDEV -d $OURNET --icmp-type $ICMPIN -j ACCEPT
# } && echo done

# ICMP - OUTGOING
# We will allow ICMP datagrams out of the allowed types.
# echo -n Allowing ICMP datagrams out of the allowed types... && {
# $IPTABLES -A FORWARD -p icmp -i $OURDEV -d $ANYADDR --icmp-type $ICMPOUT -j ACCEPT
# } && echo done

# DEFAULT and LOGGING
# All remaining datagrams fall through to the default
# rule and are dropped. They will be logged if youve
# configured the LOGGING variable above.
#

# DoS
# enabling Syn-flood protection
echo -n Enabling Syn-flood protection... && {
iptables -A FORWARD -p tcp --syn -m limit --limit 1/s -j ACCEPT
} && echo done
# Enabling Furtive port scanner protection
echo -n Enabling Furtive port scanner protection... && {
iptables -A FORWARD -p tcp --tcp-flags SYN,ACK,FIN,RST RST -m limit --limit 1/s -j ACCEPT
} && echo done
# Enabling ping of death protection
echo -n Enabling ping of death protection... && {
iptables -A FORWARD -p icmp --icmp-type echo-request -m limit --limit 1/s -j ACCEPT
} && echo done


if [ "$LOGGING" ]
then
# Log barred TCP
$IPTABLES -A FORWARD -m tcp -p tcp -j LOG
# Log barred UDP
$IPTABLES -A FORWARD -m udp -p udp -j LOG
# Log barred ICMP
$IPTABLES -A FORWARD -m udp -p icmp -j LOG
fi
#
# end.

Thunderbird Service Menu is a service menu that will allow you to right click on a file and attach it to a new E-mail from Thunderbird.

Just extract the "AttachToThunderbirdMail" config file to "/usr/share/apps/konqueror/servicemenus" and it should work.

epstools service menu is used to create a tiff preview inside an eps file.

If a preview exists, it is replaced by the created one.

Peco::Service is a Perl module with service specifications for Peco IoC containers.

SYNOPSIS

use Peco::Service;

$service = Peco::Service->new( $class, @depends, $create, %attrs );
$service = Peco::Service::Factory->new( ⊂routine, @depends );
$service = Peco::Service::Constant->new( $value );

SERVICE TYPES

Peco::Service

A generic service registration class.

Peco::Service::Factory

Factory service registration class. Takes a coderef which is called each time this service is accessed.

Peco::Service::Constant

For constant or scalar values.

I suggested a kcontrol option for enabling and disabling ACTIONS for different file types. This way, service menus would be installed and managed easier (if that control center window has that function too,it would be nice) aand maybe you will have the option to choose which actions that KIM (kde image service menu)(for example) is capable of is shown in your right click menu when you choose a jpg file...
Also an option to install the service menu just for the user that opened kcontrol (somewhere in /home/~/.kde/.../konqueror/services...) or for all users [the checkbox],requiring a root password (to copy the needed files in the needed by the service menu directories)...
Also the service menu management control center should have the option to move up and down a service menu in the -right-click-ACTIONS> sub menu.
There should be the option to pick selectably the submenus from the installed service menu and add only the ones you would like to have for the file type(for instance you can add kim-resize picture and under it you can take a submenu from a k3b service menu (add to data disc) and put it right under it for the jpg filetype (see the screenshot).
Some service menus,like kims selected "webexport" should have a > sign at the end of their names,showing that they have an included submenu,that cannot be picked/changes sepparatelly.So if web export is added,you dont have the option to pick which webexport options should be included in the web export submenu (we have to have some borders,right?)..
Another suggestion is that if a service menu is installed for all users (using the root password),it should be marked with red fonts in the service list and if promped for uninstallation,it should ofcourse ask for the root password.
And...since the kde service menus were handled the old fashionate way since this idea popped into my mind (with install.sh scripts that coppied a bunch of files,orr by hand with a READme instruction (which is a pain in the neck really)),service menus should be able to be installed the old fashionate way too,but they should be packed in special kde service menu packages,that are handled by kcontrol.This would greatly improve kdes support for service menus.
This will also resolve the clutterness/bloatness that some service menus tend to create,giving the choice in the hands of the user as to what from the service menu he/she would like to be included in the right-click menu.
Enhancements:
- added a new mockup,which is more simple and intuitive

GNOME Interface for YUM is a graphical frame-program for easier use and setup the YUM install program.

Displays the accessible packages on the package service sites with filter. Manage the settings of package services.

Manage the cache used by YUM: free up disk space, manual install and transfer of downloaded packages. Displays detailed package information about the installed packages or package files. Displays the files in the packages with a program chosen by user.