Free pc private eye serial software for linux

Tiny serial terminal is a simple and dumb tool to access serial ports. Mainly intended for use to access serial consoles of various hardware.

Usage:

Download: com.c
Version : 1.1
Size : 4607 bytes
MD5 : 73a394b6d5ad333c2bf542315e1a0b73
SHA1 : 53c8ea8a1d5450ac4237a20c843e1462acaaa96e

Building: cc -o com com.c
Usage : ./com /dev/device [speed]
Example : ./com /dev/ttyS0 [115200]
Keys : Ctrl-A - exit, Ctrl-X - display control lines status
Darcs : darcs get http://tinyserial.sf.net/
Scr.shot: screenshot.png (8862 bytes)

LibSerial provides a collection of C++ classes that allow one to access serial ports on POSIX systems like standard C++ iostream objects.

Member functions are provided for setting various parameters of the serial ports such as the baud rate, character size, flow control and others. LibSerials idea is to simplify serial port programming on POSIX systems.

When you have installed the above tools, run the following commands:

Installation:

./configure
make
make install

Note: The html documentation will not be installed by "make install". I will fix this in the future release.

Porsche Gemballa is a KDM theme featuring a Porsche Gemballa. Let me know if you like it!

License: You are free to use for personal use. Do not distribute. Do not link directly to the file. All links must point to http://www.knightechnologysolutions.com/downloads/ For any use other than Private/home use, please include this copyright notice.

Xfce 4 Eyes Plugin is a Xfce4 panel plugin that adds eyes which watch your every step.

Portions of the xfce4-eyes code were taken from geyes and are licensed under the terms of the GNU General public license, see the COPYING.GPL file.

Save your home town from three mighty wizards and their insatiable greed sparked by the discovery of an ancient ruin.

Kamyrans Eye is a fantasy-themed "roguelike" role-playing game for Nokia Series60 cellphones and PCs.

With each game, explore a world which is never quite the same - filled with inhabitants both friendly and hostile. Defend cities and villages, conquer wizard towers and raid dens.

A plethora of items, weapons and spells allow for a wide array of tactics to reach one of the multiple endings.

Serial Over IP is a tool for the transport of serial interfaces over UDP/IP. It is very usefull for connecting distant equipment that run via a serial interfaces to a local computer.


One linux will be server and one will be client. On the server you can start the program typing the following command:

bash# serialoverip -d /dev/ttyS0 9600-8n1 -s 127.0.0.1 3000

... and on the client:

bash# serialoverip -c 127.0.0.1 3000 -d /dev/ttyS1 9600-8n1

In both commands the IP address is the server IP. Note that you have to start the server first, and it will be efectively be running only after the first packet received from the client.

Script for a multi-homed firewall is an example IPTables 1.2.1 script for a dual-homed firewall.

This script has not yet been tested thoroughly on a dual-homed firewall. If you find any problems, please drop me an email.

Current versions and documentation are available at http://www.sentry.net/~obsid/IPTables/rc.scripts.dir/current/

## User-defined Chains ##

Chain KEEP_STATE
The KEEP_STATE chain holds a few rules for generic stateful packet filtering.
This chain is called from many of the INPUT/OUTPUT chains to DROP "INVALID"
and perhaps "UNCLEAN" packets and allow other packets from "RELATED" or
"ESTABLISHED" connections.

CHECK_FLAGS
The CHECK_FLAGS chain contains a few rules to filter based on TCP flags.
These rules do indeed filter mainly bogus/malicious traffic(scans, etc). It
would be a good idea to keep an eye on what these rules send to the logs.
Null scans are also logged and dropped, in the mangle table.

DENY_PORTS
The DENY_PORTS chains contains a few rules to DROP and/or LOG packets based
on the source and/or destination port number of the packet.

Packets destined to/from the following ports are dropped by default in the script. These are just some examples of some commonly used ports that certain daemons/trojans/DDoS agents may utilize.

## TCP ##
137:139 SMB
2049 NFS
6000:6063 X
20034 Netbus 2 Pro
12345:12346 Netbus
27374 SubSeven
27665,27444,31335 Trinoo
10498,12754 Mstream

## UDP ##
2049 NFS
31337 BO2k
27444,31335 Trinoo
10498 mstream

These are just examples to stare at. They guarantee no real protection against the associated trojans.

For more common port numbers check out:
http://www.sans.org/newlook/resources/IDFAQ/oddports.htm

ALLOW_PORTS
The ALLOW_PORTS chain simply ACCEPTs packets based on port number. If you have
a default FORWARD policy of DROP, then you would need to utilize a chain like
this if you are DNATing/routing connections behind the firewall or perhaps
running services on(!!!) the firewall.

ALLOW_ICMP
The ALLOW_ICMP chains simply allows packets based on ICMP type. Currently
the firewall allows the flow of the following ICMP types:
Echo Reply (pong)
Destination Unreachable
Echo Request (ping)
TTL Exceeded (traceroute)

SRC_EGRESS && DST_EGRESS
The SRC_EGRESS and DST_EGRESS chains filter packets that have a source or
destination IP address matching an array of private or reserved subnets.

TOS_OUTPUT
The TOS_OUTPUT chain exists in the mangle table and mangles the TOS(Type
of Service) field in the IP header of locally generated, outgoing packets.

TOS_PREROUTING
The TOS_PREROUTING chain exists in the mangle table and mangles the TOS(Type
of Service) field in the IP header of packets being routed through the firewall.

The following user-defined chains are pretty obvious. The firewall script is designed to have a user-defined INPUT and OUTPUT chain for every available interface. From these user-defined chains are called the user-defined chains
mentioned above, which I call "Special Chains". The chains below are then called by the built-in INPUT/OUTPUT/FORWARD chains. This isnt really the rule, of course, alot of the user-defined chains mentioned above are called directly from the built-in INPUT/OUTPUT/FORWARD chains. This is done to assure proper flow of the packets through the filters.

EXTERNAL_INPUT
INTERNAL_INPUT
DMZ_INPUT
LO_INPUT
EXTERNAL_OUTPUT
INTERNAL_OUTPUT
DMZ_OUTPUT
LO_OUTPUT