Free xml spy software for linux

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.

XML::EasySQL is a two-way SQL/XML base class for Perl.
SYNOPSIS
...
# fetch a database row as hash ref
my $data = $db->selectrow_hashref(select * from users where id = 2);
# init the new EasySQL data object
my $data_object = EasySqlChildClass->new({data=>$data});
# get the root XML element
my $xml = $data_object->getXML();
# make changes to the XML document
$xml->username->setString(curtisleefulton);
$xml->bio->setAttr(age, 22);
$xml->bio->city->setString(Portland);
$xml->history->access->setAttr(last, time());
# output entire XML doc as string to STDOUT
print $xml->getDomObj->toString();
# update the database
my $sql = $data_object->getSQL();
my $q = "update users set ".$sql->{users}." where id = 2";
$db->do($q);
Main features:
- Two-way transforms between XML and SQL data
- smart SQL updates: only altered tables are updated
- unlimited tree depth
- multiple SQL tables can merge intone XML tree, then back again
- precise control over how data is translated
- offers either an easy XML interface or plain DOM
- database independent

XML::RDB is a Perl extension to convert XML files into RDB schemas and populate, and unpopulate them. Works with XML Schemas too.

SYNOPSIS

use XML::RDB;

# Give our DBs DSN & username/password
my $rdb = new XML::RDB(config_file => db_config);

# Generate RDB Schema
$rdb->make_tables("my_xml_file.xml", "db_schema_output_file");

#
# Now import the generated db_schema_output_file into your DB
# (see t/1.t for an automated way to do this)
#

# Now populate our RDB
my($root_table_name, $primary_key) =
$rdb->populate_tables("my_xml_file.xml");

#
# Your XML file is now in your RDB!!!! Play as desired & when ready:
#
$rdb->unpopulate_tables($root_table_name, $primary_key,
new_xml_file.xml);


#
# Thats all fine & dandy but what if youve got an XML Schema???
#
# the first 2 calls are the same:
$rdb->make_tables("my_xsd_file.xsd", "db_schema_output_file");

#
# dont forget to put db_schema_output_file into your DB!
# then:
my($root_table_name, $primary_key) =
$rdb->populate_tables("my_xsd_file.xsd");

# note we only need the primary key for this next call
$rdb->unpopulate_schema($primary_key, fully_formed.xml);

#
# Now youve got fully_formed.xml - pass THAT to make_tables
# & yer golden:
#

$rdb->make_tables("fully_formed.xml", "REAL_RDB_schema");

#
# Now insert REAL_RDB_schema into yer DB & now any XML documents
# conforming to your original XML Schema (my_xsd_file.xsd) can be
# imported into your schema:
my ($rt, $pk) =
$rdb->populate_tables("xml_doc_conforming_to_my_xsd_file.xml");

# See the README file for a LOT more information...

ABSTRACT

XML::RDB - Perl extension to convert XML files into RDB schemas and populate, and unpopulate them. Works with XML Schemas too. Analyzes relationships within either an XML file or an XML Schema to create RDB tables to hold that document (or any XML document that conforms to the XML Schema).

Pod::XML is a Perl module to convert POD to XML.

SYNOPSIS

use Pod::XML;
my $parser = Pod::XML->new();
$parser->parse_from_file("foo.pod");

This module uses Pod::Parser to parse POD and generates XML from the resulting parse stream. It uses its own format, described below.

XML Copy Editor is an XML editor with DTD/XML Schema/RELAX NG validation, XSLT, XPath, pretty-printing, syntax highlighting, folding, tag completion/locking and lossless import/export of Microsoft Word documents.
Enhancements:
- This release fixes a number of bugs and introduces support for CSS.

MARC::XML is a subclass of MARC.pm to provide XML support.

SYNOPSIS

use MARC::XML;

#read in some MARC and output some XML
$myobject = MARC::XML->new("marc.mrc","usmarc");
$myobject->output({file=>">marc.xml",format=>"xml"});

#read in some XML and output some MARC
$myobject = MARC::XML->new("marc.xml","xml");
$myobject->output({file=>">marc.mrc","usmarc");

MARC::XML is a subclass of MARC.pm which provides methods for round-trip conversions between MARC and XML. MARC::XML requires that you have the CPAN modules MARC.pm and XML::Parser installed in your Perl library. Version 1.04 of MARC.pm and 2.27 of XML::Parser (or later) are required. As a subclass of MARC.pm a MARC::XML object will by default have the full functionality of a MARC.pm object. See the MARC.pm documentation for details.

The XML file that is read and generated by MARC::XML is not associated with a Document Type Definition (DTD). This means that your files need to be well-formed, but they will not be validated. When performing XML->MARC conversion it is important that the XML file is structured in a particular way. Fortunately, this is the same format that is generated by the MARC->XML conversion, so you should be able to be able to move your data easily between the two formats.

RPC::XML is a set of classes for core data, message and XML handling.

SYNOPSIS

use RPC::XML;

$req = RPC::XML::request->new(fetch_prime_factors,
RPC::XML::int->new(985120528));
...
$resp = RPC::XML::Parser->new()->parse(STREAM);
if (ref($resp))
{
return $resp->value->value;
}
else
{
die $resp;
}

The RPC::XML package is an implementation of the XML-RPC standard.

The package provides a set of classes for creating values to pass to the constructors for requests and responses. These are lightweight objects, most of which are implemented as tied scalars so as to associate specific type information with the value. Classes are also provided for requests, responses, faults (errors) and a parser based on the XML::Parser package from CPAN.

This module does not actually provide any transport implementation or server basis. For these, see RPC::XML::Client and RPC::XML::Server, respectively.