Free vnc for solaris software for linux

Sun::Solaris::Ucred is a Perl interface to User Credentials.

SYNOPSIS

use Sun::Solaris::Ucred qw(:ALL);

This module provides wrappers for the Ucred-related system and library calls.

Functions

ucred_get($pid)

This function returns the credential of the process specified by $pid, if the process exists and the calling process is permitted to obtain the credentials of that process.

getpeerucred($fd)

If $fd is a connected connection oriented TLI endpoint, a connected SOCK_STREAM or SOCK_SEQPKT socket, getpeerucred will return the user credential of the peer at the time the connection was established, if availble.
ucred_geteuid($ucred)

This function returns the effective uid of a user credential, if available.
ucred_getruid($ucred)
This function returns the real uid of a user credential, if available.
ucred_getsuid($ucred)
This function returns the saved uid of a user credential, if available.
ucred_getegid($ucred)
This function returns the effective group of a user credential, if available.
ucred_getrgid($ucred)
This function returns the real group of a user credential, if available.
ucred_getsgid($ucred)
This function returns the saved group of a user credential, if available.
ucred_getgroups($ucred)
This function returns the list of supplemental groups of a user credential, if available. An array of groups is returned in ARRAY context; the number of groups is returned in SCALAR context.
ucred_getprivset($ucred, $which)
This function returns the privilege set specified by $which of a user credential, if available.

ucred_getpflags($ucred, $flags)

This function returns the value of a specific process flag of a user credential, if available.

ucred_getpid($ucred)
This function returns the process id of a user credential, if available.
ucred_getzoneid($ucred)

This function returns the zone id of a user credential, if available.

Exports

By default nothing is exported from this module. The following tags can be used to selectively import constants and functions defined in this module:

:SYSCALLS ucred_get(), getpeerucred()

:LIBCALLS ucred_geteuid(), ucred_getruid(), ucred_getsuid(),
ucred_getegid(), ucred_getrgid(), ucred_getsgid(),
ucred_getgroups(), ucred_getprivset(), ucred_getpflags(),
ucred_getpid(), ucred_getzone()

:CONSTANTS

:VARIABLES %PRIVILEGES, %PRIVSETS

:ALL :SYSCALLS, :LIBCALLS, and :CONSTANTS

Solaris::Kstat is a Perl module to access Solaris Kstats from Perl.

SYNOPSIS

use Solaris::Kstat;
my $kstat = Solaris::Kstat->new();
my ($usr1, $sys1, $wio1, $idle1) =
@{$kstat->{cpu_stat}{0}{cpu_stat0}}{qw(user kernel wait idle)};
print("usr sys wio idlen");
while (1)
{
sleep 5;
if ($kstat->update()) { print("Configuration changedn"); }
my ($usr2, $sys2, $wio2, $idle2) =
@{$kstat->{cpu_stat}{0}{cpu_stat0}}{qw(user kernel wait idle)};
printf(" %.2d %.2d %.2d %.2dn",
($usr2 - $usr1) / 5, ($sys2 - $sys1) / 5,
($wio2 - $wio1) / 5, ($idle2 - $idle1) / 5);
$usr1 = $usr2; $sys1 = $sys2; $wio1 = $wio2; $idle1 = $idle2;
}

This module provides a tied hash interface to the Solaris kstats library. The kstats library allows you to get access to all the stats used by sar, iostat, vmstat etc, plus a lot of others that arent accessible through the usual utilities.
Solaris categorises statistics using a 3-part key - module, instance and name. For example, the root disk stats can be found under sd.0.sd0, and the cpu statistics can be found under cpu_stat.0.cpu_stat0, as in the above example. The method Solaris::Kstats-new()> creates a new 3-layer tree of perl hashes with exactly the same structure - i.e. the stats for disk 0 can be accessed as $ks-{sd}{0}{sd0}>. The bottom (4th) layer is a tied hash used to hold the individual statistics values for a particular system resource.

Creating a Solaris::Kstat object doesnt actually read all the possible statistics in, as this would be horribly slow and inefficient. Instead it creates a 3-layer structure as described above, and only reads in the individual statistics as you reference them. For example, accessing $ks-{sd}{0}{sd0}{reads} will read in all the statistics for sd0, including writes, bytes read/written, service times etc. Once you have accessed a bottom level statitics value, calling $ks->update() will automatically update all the individual values of any statistics that you have accessed.

Note that there are two values per bottom-level hash that can be read without causing the full set of statistics to be read from the kernel. These are "class" which is the kstat class of the statistics and "crtime" which is the time that the kstat was created. See kstat(3K) for full details of these fields.

Software::Packager::Solaris is the Software::Packager extension for Solaris 2.5.1 and above.

SYNOPSIS

use Software::Packager;
my $packager = new Software::Packager(solaris);

This module is used to create software packages in a format suitable for installation with pkgadd. The process of creating packages is baised upon the document Application Packaging Developers Guide. Which can be found at http://docs.sun.com/ab2/@LegacyPageView?toc=SUNWab_42_2:/safedir/space3/coll1/SUNWasup/toc/PACKINSTALL:Contents;bt=Application+Packaging+Developer%27s+Guide;ps=ps/SUNWab_42_2/PACKINSTALL/Contents

FUNCTIONS

new()

This method creates and returns a new Software::Packager::Solaris object.

add_item()
$packager->add_item(%object_data);

This method overrides the add_item function in the Software::Packager module.

This method adds a new object to the package.

package()

$packager->packager(); This method overrides the base API in Software::Packager, it controls the process if package creation.

package_name()

This method is used to specify the abbreviated package name.

Sun say: (Application Packaging Developers Guide. Page 32) A valid package abbreviation must the criteria defined below:

It must start with a letter. Additional charaters may be alphanumeric and can be the two special charaters + and -.

It must be nine or fewer charaters.

Reserved names are install, new, and all.

For more details see the pkginfo(4) man page.

program_name()

This is used to specify the full package name.

The program name must be less that 256 charaters.

For more details see the pkginfo(4) man page.

architecture()

The architecture must be a comma seperated list of alphanumeric tokens that indicate the architecture associated with the package. The maximum length of a token is 16 charaters. A token should be in the format "instruction set"."platform group" where: instruction set is the output of `uname -p` platform group is the output of `uname -m`
If the architecture is not set then the current instruction set is used.

For more details see the pkginfo(4) man page.

version()

This method is used to check the format of the version and return it in the format required for Solaris.

The version must be 256 charaters or less.

The first charater cannot be a left parenthesis.

The recommended format isi an arbitrary string of numbers in Dewey-decimal format. For more datails see the pkginfo(4) man page.

install_dir()
$packager->install_dir(/usr/local);
my $base_dir = $packager->install_dir();

This method sets the base directory for the software to be installed. The installation directory must start with a "/".

compatible_version()

$packager->compatible_version(/some/path/file);
or
$packager->compatible_version($compver_stored_in_string);

my $compatible_version = $packager->compatible_version();

This method sets the compatible versions file for the software to be installed.

space()

$packager->space(/some/path/file);
or
$packager->space($space_data_stored_in_string);
my $space = $packager->space();

This method sets the space file for the software to be installed.

request_script()

$packager->request_script(/some/path/file);
or
$packager->request_script($request_script_stored_in_string);
my $request_script = $packager->request_script();

This method sets the space file for the software to be installed.

VNC Spy monitors network traffic to find keystrokes entered into a VNC viewer. Letters the user types are printed to your screen.

So, for example, if an engineer insists on using VNC to log in from his Windows machine into your network whenever he wants from home, try leaving vncspy running for a while. I like to use the command:

sudo vncspy eth0 | tee keylog

Note that you need to run vncspy as root. You can either su root, or sudo.

This will sniff all keystrokes he enters from home to his VNC server. Assuming he has to enter his user name and password to log-on, you should see his user name in the keylog, followed by his password. Its that simple!

When you get his password, try writing it on a sticky-note, and pasting it on his monitor. Ive found showing people their passwords to be very effective at improving their security habits.

Usage:

vncspy must be run as root. It takes only one optional parameter, the interface to sniff on. If left out, it will use the first interface on your system, typically eth0.

Compling:

The only major dependency for vncspy is the pcap development library. On Debian or Ubuntu, you may issue a command like:

sudo apt-get install libpcap0.8-dev

If your system does not have libpcap available, you can install it from source from:

http://www.tcpdump.org.

Once you have libpcap, compiling vncspy is simple. Just type:

make

It should create the vncspy program. Let me know if you need help.

VNC Session Manager provides a disconnected session manager for VNC.

VNC Session Manager adds the necessary glue code between VNCs two execution modes, enabling XDM-based login to disconnected sessions. This gives a Terminal Services-like login for Unix-based VNC servers.