Free dtd software for linux

DTD to XML Schema translator allows you to translate a Document Type Definition (DTD) into an XML Schema.

DTD to XML Schema translator lets you translate a Document Type Definition into an XML Schema (REC-xmlschema-1-20010502).

The translator can map meaningful DTD entities onto XML Schema constructs (simpleType, attributeGroup, group); the XML document model is not anonymized.

In addition, the translator can map DTD comments onto XML Schema documentation nodes in various ways.

Free available as Java class, Standalone application and as Web tool.

DFBPoint project is a presentation program using DirectFB.
It reads an XML file with simple slide descriptions and displays the slides.
Features include antialiased text, background images, images, and video playback.
The slides can be faded/slid in.
Main features:
- Rectangle filling
- Rectangle drawing
- Line drawing
- Blitting
- Stretched Blitting
- Blitting/Drawing
- Colorizing
Enhancements:
- fixed possible issues with filename encodings
- added a DTD provided by Jochen Hein
- misc minor fixes

Embedix::ECD is a Perl module with Embedix Component Descriptions as objects.

SYNOPSIS

instantiate from a file
my $ecd = Embedix::ECD->newFromFile(busybox.ecd);
my $other_ecd = Embedix::ECD->newFromFile(tinylogin.ecd);
access nodes
my $busybox = $ecd->System->Utilities->busybox;
build from scratch
my $server = Embedix::ECD::Group->new(name => Server);
my $www = Embedix::ECD::Group->new(name => WWW);
my $apache = Embedix::ECD::Component->new (
name => apache,
srpm => apache,
prompt => Include apache web server?,
help => The most popular http server on the internet,
);
$ecd->addChild($server);
$ecd->Server->addChild($www);
$ecd->Server->WWW->addChild($apache);
get/set attributes
my $srpm = $busybox->srpm();

$busybox->help(i am busybox of borg -- unix will be assimilated.);

$busybox->requires([
libc.so.6,
ld-linux.so.2,
skellinux,
]);
combine Embedix::ECD objects together
$ecd->mergeWith($other_ecd);
print as text
print $ecd->toString;
print as XML
use Embedix::ECD::XMLv1 qw(xml_from_cons);

print $ecd->toXML(shiftwidth => 4, dtd => yes);

my $cons = Embedix::ECD->consFromFile(minicom.ecd);
print xml_from_cons($cons);

Embedix::ECD allows one to represent ECD files as a tree of perl objects. One can construct objects by parsing an ECD file, or one can build an ECD object from scratch by combining instances of Embedix::ECD and its subclasses. These objects can then be turned back into ECD files via the toString() method.

ECD stands for Embedix Component Description, and its purpose is to contain meta-data regarding packages (aka components) in the Embedix distribution. ECD files contain much of the same data a .spec file does for an RPM. A major difference however is that ECD files do not contain building instructions whereas .spec files do. Another major difference between .spec files and ECD files is the structure. ECD files are hierarchically structured whereas .spec files are comparatively flat.

The ECD format reminds me of the syntax for Apache configuration files. Items are tag-delimited (like in XML) and attributes are found between these tags. Comments are written by prefixing them with /^s*#/. Unlike apache configurations, attribute names and values are separated by an "=" sign, whereas in apache the first token is the attribute name and everything after that (sans leading whitespace) and up to the end of the line is the attributes value. Also, unlike apache configurations, attributes may also be enclosed in tags, whereas in apache tags are used only to describe nodes.

ECD files look like pseudo-XML with shell-styled comments.

XML::Structured is a simple conversion API from XML to perl structures and back.

SYNOPSIS

use XML::Structured;

$dtd = [
element =>
attribute1,
attribute2,
[],
element1,
[ element2 ],
[ element3 =>
...
],
[[ element4 =>
...
]],
];

$hashref = XMLin($dtd, $xmlstring);
$hashref = XMLinfile($dtd, $filename_or_glob);
$xmlstring = XMLout($dtd, $hashref);

The XML::Structured module provides a way to convert xml data into a predefined perl data structure and back to xml. Unlike with modules like XML::Simple it is an error if the xml data does not match the provided skeleton (the "dtd"). Another advantage is that the order of the attributes and elements is taken from the dtd when converting back to xml.

XML::ValidWriter is DOCTYPE driven valid XML output.

SYNOPSIS

## As a normal perl object:
$writer = XML::ValidWriter->new(
DOCTYPE => $xml_doc_type,
OUTPUT => *FH
) ;
$writer->startTag( b1 ) ;
$writer->startTag( c2 ) ;
$writer->end ;

## Writing to a scalar:
$writer = XML::ValidWriter->new(
DOCTYPE => $xml_doc_type,
OUTPUT => $buf
) ;

## Or, in scripting mode:
use XML::Doctype NAME => a, SYSTEM_ID => a.dtd ;
use XML::ValidWriter qw( :all :dtd_tags ) ;
b1 ; # Emits < a >< b1 >
c2( attr=>"val" ) ; # Emits < /b1 >< b2 >< c2 attr="val" >
endAllTags ; # Emits < /c2 >< /b2 >< /a >

## If youve got an XML::Doctype object handy:
use XML::ValidWriter qw( :dtd_tags ), DOCTYPE => $doctype ;

## If youve saved a preparsed DTD as a perl module
use FooML::Doctype::v1_0001 ;
use XML::ValidWriter qw( :dtd_tags ) ;

#
# This all assumes that the DTD contains:
#
# < !ELEMENT a ( b1, b2?, b3* ) >
#
# < !ELEMENT b1 ( c1 ) >
# < !ELEMENT b2 ( c2 ) >
#

STATUS

Alpha. Use and patch, dont depend on things not changing drastically.
Many methods supplied by XML::Writer are not yet supplied here.

GETOX is a project developped by IDEALX. This software aims at giving users the ability to write XML files without having advanced knowledge of XML concepts.
It should also allow users to produce valid documents at any time. GETOX is a free software, and is released under the GNU General Public License.
Main features:
File manipulation:
- Open/Close/Save XML files including parsing of the associated DTD
- Creation of a new XML file generated from a DTD
Text manipulation
- The main goal of GETOX is to manipulate XML file as if it was a simple text file.
Right now, users can:
- Add and remove tags according to the DTD
- Edit text in #pcdata
- Move across the text using arrows
- Cut and Paste text from widgets to X clipboard
- Choose encoding of some XML parameters
- Modify path to DTD
- Modify look & feel of getox_canvas

XML::DOM::DocumentType is an XML document type (DTD) in XML::DOM.

XML::DOM::DocumentType extends XML::DOM::Node.

Each Document has a doctype attribute whose value is either null or a DocumentType object. The DocumentType interface in the DOM Level 1 Core provides an interface to the list of entities that are defined for the document, and little else because the effect of namespaces and the various XML scheme efforts on DTD representation are not clearly understood as of this writing. The DOM Level 1 doesnt support editing DocumentType nodes.

Not In DOM Spec: This implementation has added a lot of extra functionality to the DOM Level 1 interface. To allow editing of the DocumentType nodes, see XML::DOM::ignoreReadOnly.

ETTERLOG is a utility for Network Lan (SWITCH) for file .ECI and .ECP.
(Ettercap program).

Etterlog is the log analyzer for logfiles created by ettercap. It can handle both compressed (created with -Lc) or uncompressed logfiles. With this tool you can manipulate binary files as you like and you can print data in different ways all the times you want (in contrast with the previous logging system which was used to dump in a single static manner).

You will be able to dump traffic from only one connection of your choice, from only one or more hosts, print data in hex, ascii, binary etc... TIP: All unuseful messages are printed to stderr, so you can save the output from etterlog with the following command:

etterlog [options] logfile > outfile Thus you can dump for example a binary file from an ftp connection if you print the data in binary mode, without headers and selecting only the ftp server as the source of the communication.

GENERAL OPTIONS

-a, --analyze Analyze a log file and display some interesting statistics.

-c, --connections Parse the log file and print a table of unique connections (port to port). This option can be used only on LOG_PACKET logfiles. On LOG_INFO logfiles it is useless. TIP: you can search for a particular host by using the following command: etterlog -c logfile.ecp | grep 10.0.0.1

-f, --filter < TARGET > Print only packets coming from or going to TARGET. The TARGET specification is the same as in ettercap.
TARGET is in the form MAC/IPs/PORTs. Omitting one or more of its parts will be equivalent to set them to ANY. If the log type is LOG_INFO the target is used to display hosts matching the mac, ip and having the specified port(s) open. For example the target //80 will display only information about hosts with a running web server.

-r, --reverse Reverse the matching in the TARGET selection. It means not(TARGET). All but the selected TARGET.

-t, --proto < PROTO > Sniff only PROTO packets (default is TCP + UDP). This option is only useful in "simple" mode. If you start ettercap in interactive mode both TCP and UDP are sniffed.
PROTO can be "tcp", "udp" or "all" for both.

-F, --filcon < CONNECTION > Print packets belonging only to this CONNECTION.
CONNECTION is in the form PROTO:SOURCE:DEST. SOURCE and DEST are in the form IP:PORT. example: etterlog -F TCP:10.0.0.23:3318:198.182.196.56:80

-s, --only-source Display only packets that are sent by the source of the selected CONNECTION. This option makes sense only in conjunction with the -F option. TIP: if you want to save a file transferred in an HTTP or FTP connection, you can use the following command: etterlog -B -s -n -F TCP:10.0.0.1:20:10.0.0.2:35426 logfile.ecp > example.tar.gz

-d, --only-dest Same as --only-source but it filters on the destination host.

-n, --no-headers Do not print the header of each packet. This option is useful if you want to save a file in binary format (-B option). Without the headers you can redirect the output to a file and you will get the original stream. NOTE: the time stamp in the header is in the form: Thu Mar 27 23:03:31 2003 [169396], the value in the square brackets is expressed in microseconds

-m, --show-mac In the headers show also the mac addresses corresponding to the ip addresses.

-k, --color If used in conjunction with -F it displays the source and dest of the connection using different colors. If used with a LOG_INFO file it prints LAN hosts in green, REMOTE hosts in blue and GATEWAYS in red.

-l, --only-local Used displaying an INFO file, it displays information only about local hosts.

-L, --only-remote Used displaying an INFO file, it displays information only about remote hosts.

SEARCH OPTIONS

-e, --regex < REGEX > Display only packets matching the regex < REGEX >.
If this option is used agains a LOG_PACKET logfile, the regex is executed on the payload of the packet. If the type is LOG_INFO, the regex is executed on all the fields of the host profile (OS, banners, service and ethernet adapter).
NOTE: the regex is compiled with the REG_ICASE flag (case insensitive).

-u, --user < USER > Display information about this user. The search is performed over all the user/pass couples collected across all hosts.

-p, --passwords Print only the collected account information for each host. This prevents the huge profile output. It can be used in conjunction with the -u option to filter the users. An asterisk * used in front of an account represents a failed login attempt.

-i, --show-client Show the client ip address when displaying the collected users and passwords. It may be useful when ACLs are in place.

-I, --client < IP > Show passwords only coming from a specific < IP >. This is useful to view all the usernames and passwords of a client.


EDITING OPTIONS

-C, --concat Use this option to concatenate two (or more) files into one single file. This is useful if you have collected ettercap log files from multiple sources and want to have an unified report. The output file must be specified with the -o option and the input files are listed as normal arguments. example:
etterlog -C -o outfile input1 input2 input3

-o, --outfile < FILE > specifies the output file for a concatenation.


VISUALIZATION METHOD


-B, --binary Print data as they are, in binary form. Useful to dump binary data to a file (as described above).

-X, --hex Print the packets in hex format. example: the string "HTTP/1.1 304 Not Modified" becomes: 0000: 4854 5450 2f31 2e31 2033 3034 204e 6f74 HTTP/1.1 304 Not
0010: 204d 6f64 6966 6965 64 Modified

-A, --ascii Print only "printable" characters, the others are displayed as dots .

-T, --text Print only the "printable" characters and skip the others.

-E, --ebcdic Convert an EBCDIC text to ASCII.

-H, --html Strip all html tags from the text. A tag is every string between < and >. example: < title >This is the title< /title >, but the following < string > will not be displayed. This is the title, but the following will not be displayed.

-U, --utf8 < encoding > Print the packets in UTF-8 format. The < encoding > parameter specifies the encoding to be used while performing the conversion. Use the `iconv --list` command to obtain a list of all supported encodings.

-Z, --zero Print always the void string. i.e. print only header information and no packet content will be printed.

-x, --xml Print the host information in xml form, so you can parse it with your favourite program. The DTD associated with the xml output is in share/etterlog.dtd

STANDARD OPTIONS

-v, --version Print the version and exit.

-h, --help Print the help screen with a short summary of the available options.


EXAMPLES

Here are some examples of using etterlog.

etterlog -k -l dump.eci
Displays information about local hosts in different colors.

etterlog -X dump.ecp
Prints packets in HEX mode with full headers.

etterlog -c dump.ecp
Displays the list of connections logged in the file.

etterlog -Akn -F TCP:10.0.0.1:13423:213.203.143.52:6666 dump.ecp
Displays the IRC traffic made by 10.0.0.1 in ASCII mode, without headers information and in colored mode.

etterlog -H -t tcp -f //80 dump.ecp
Dumps all HTTP traffic and strips html tags.

etterlog -Z -r -f /10.0.0.2/22 dump.ecp
Displays only the headers of all connections except ssh on host 10.0.0.2

etterlog -A -e user -f //110 dump.ecp
Displays only POP packets containing the user regexp (case insensitive).

etterlog -u root dump.eci
Displays information about all the accounts of the user root.

etterlog -e Apache dump.eci
Displays information about all the hosts running Apache.

etterlog -e Linux dump.eci
Displays information about all the hosts with the Linux operating system.

etterlog -t tcp -f //110 dump.eci
Displays information about all the hosts with the tcp port 110 open.

etterlog -t udp dump.eci
Displays information about all the hosts with at least one UDP port open.

etterlog -B -s -n -F TCP:10.0.0.1:20:10.0.0.2:35426 logfile.ecp > example.tar.gz
Dumps in binary form the data sent by 10.0.0.1 over the data port of FTP. Since the headers are omitted, you will get the file as it was.