Free iv software for linux

IV is a simple image viewer with pan and zoom viewing and many editing features.

Image Viewer (often refered to as IV) allows you to; view convert, grab (screenshot), print, rotate, crop, resize, display on desktop, add text, add comments, and open/edit/save animated images.

Additional viewing features include pan & zoom with just a click and a drag.

Currently, IV supports direct opening and saving with the image libraries:

libungif - Uncompressed GIF images
libjpeg - JPEG images
libpng - PNG & MNG images
libtga (internal) - TGA images
libXpm - XPM images

In addition, binary and text files can also be displayed with IVs internal File View and Hex View windows.

Linvpn is a secure socket layer for pppd. Linvpn project allows creation of virtual private networks by using an IP routing system between PPP network interfaces.

Cryptography is done by libgcrypts 3DES or blowfish, and Initialization Vector (IV) is changed in each packet transmission.

As linvpn works as client and server, and communication is a single TCP connection, it allows creation of secure tunnels even in complex network layouts, when one or both endpoints are behind a firewall or NAT, with or without dynamic IP addresses.
Linvpn has been tested under Linux, FreeBSD, NetBSD and OpenBSD.

SiSU is a Serialized information, Structured Units for Electronic Documents, is a document creation and management framework.
Main features:
- (i) markup syntax: (a) simpler than html, (b) mnemonic, influenced by mail/messaging/wiki markup practices, (c) human readable, and easily writable,
- (ii) (a) minimal markup requirement, (b) single file marked up for multiple outputs,
- (iii) (a) multiple outputs include amongst others: html; pdf via LaTeX; (structured) XML; sql - currently PostgreSQL (and SQLite); ascii, (also texinfo), (b) takes advantage of the strengths implicit in these very different output types,
- (iv) provides a common object positioning and citation system for all outputs, which is human relevant and machine usable: object citation numbering, all objects (paragraphs, headings, verse, tables etc. and images) are numbered identically, for citation purposes, in all outputs (html, pdf, sql etc.),
- (v) use of Dublin Core and other meta-tags to permit the addition of some semantic information on documents, and making easy integration of rdf/rss feeds etc.,
- (vi) creates organised directory/file structure for (file-system) output, easily mapped with its clearly defined structure, with all text objects numbered, you know in advance where in each document output type, a bit of text will be found (eg. from an sql search, you know where to go to find the prepared html output or pdf etc.)... there is more; easy directory management and document associations, the document preparation (sub-)directory may be used to determine output (sub-)directory, the skin used, and the sql database used,
- (vii) search of document sets, the relational database retains information on the document structure, and citation numbering makes it possible for example to present search matches as an index of documents and locations within the document where the match is found,
- (viii) "word maps" rudimentary index, consisting of all the words in a document and their (text/ object) locations within the text, (and the possibility of adding vocabularies),
- (ix) easily skinnable, document appearance on a project/site wide, directory wide, or document instance level easily controlled/changed,
- (x) in many cases a regular expression may be used (once in the document header) to define all or part of a documents structure obviating or reducing the need to provide structural markup within the document,
- (xi) is a batch processor for handling large document sets, ... though once generated they need not be re-generated, unless changes are made to the desired presentation of a particular output type,
- (xii) possible to pre-process, which permits: the easy creation of standard form documents, and templates/term-sheets, or; building of composite documents (master documents) from other sisu marked up documents, or marked up parts, i.e. import documents or parts of text into a main document should this be desired
- (xiii) future proofing, a framework for adding further capability or updating existing capability as required: (a) modular, (thanks in no small part to Ruby) another output format required, write another module....(b) easy to update output formats (eg html, xhtml, latex/pdf produced can be updated in program and run against whole document set), (c) easy to add, modify, or have alternative syntax rules for input, should you need to,
- (xiv) scalability, dependent on your file-system (in my case Reiserfs) and on the relational database used (currently Postgresql and SQLite), and your hardware,
- (xv) only marked up files need be backed up, to secure the larger document set produced,
- (xvi) document version and comparison considerations (a) possibility to easily check or guarantee that the substantive content of a document is unchanged, through md5 (or other) hash keys, (b) version control, documents integrated with time based version control system, default CVS with use of $Id$ tag, which SiSU checks (c) SiSUs minimalist markup makes for meaningful "diffing" of the substantive content of markup-files,
- (xvii) document management,
- (xviii) use your favourite editor, syntax highlighting files for markup, primarily (g)vim so far,
- (xviv) remote operations: (a) run SiSU on a remote server, (having prepared sisu markup documents locally or on that server, i.e. this solution where sisu is installed on the remote server, would work whatever type of machine you chose to prepare your markup documents on), (b) alternatively, (assuming sisu is available to you locally but not installed on the remote server) configure sisu to securely copy (scp) its output to your remote host and run sisu locally, (c) request a remotely located sisu markup file and process it locally by identifying it by its url.

IsForth is a direct threaded Linux-only x86 Forth implementation coded in pure assembly using NASM macros to create forth high-level definitions.
All I/O is done with syscalls. IsForth is almost a complete replacement for both libc and libncurses.
To use the debugger say debug xyzzy and from within the debugger..
Space - single steps
Enter - enters into words that nest
Escape - exits debugger
Cursor - move cursor within current definition
h - run to cursor location
H - auto step to current location
While auto stepping + and - change the step speed
Enhancements:
- The finishing touches were put on the keyboard handling for special keys.

iTMS-4-ALL is a Perl CGI script that allows you to search Apples iTunes Music Store from any Web browser.

First of all, you can try the live script. Thanks to the people at Downhill Battle for hosting the script---they have also posted some interesting ideas about how the iTunes database can be used. Jason Terk has released a version of the script that uses CSS/XHTML, and you can try his live script.

You can also download the latest iTMS-4-ALL script package (v0.2, which works with Apples v4.5 server, thanks to nand). Three non-standard Perl modules are needed, but they are included (INET.pm and CBC.pm are pure Perl; Rijndael.pm needs to be compiled for your system). Extract the package, then run installRijndaelLocal.sh to build the Rijndael module. Copy the itms4all.pl script, the Crypt directory, the IO directory, and the auto directory into your servers cgi-bin directory. Make sure the itms4all.pl script is executable by your web server.

The script has been released under the GNU GPL.

You can can browse the store and access previews, but you cannot log in or purchase iTunes. David Hammerton has been working on logging in to iTunes.

Here is what I know about the iTunes Music Store Protocol so far:

1. iTunes communicates with Apple almost exclusively through HTTP [browsing the store and playing preview clips works through a web proxy, even with no direct connection to the Internet].
2. iTunes authentication (logging in so you can actually buy something) is not happening through HTTP [no requests hit my web proxy when iTunes tries to log in; logging in fails without a direct Internet connection].
3. iTunes fetches gzipped XML files from Apple to lay out its GUI (to display the store front, genre pages, and search results).
4. Every gzipped XML file is encrypted with AES-128 (Rijndael) in CBC mode. The CBC initialization vector is included in the HTTP header (x-apple-crypto-iv).
5. The AES key is 8a9dad399fb014c131be611820d78895. This key is hard-coded somehow in iTunes.

phpHtmllib is a set of PHP classes and library functions to help facilitate building, debugging, and rendering of XML, HTML, XHTML WAP/WML Documents, and SVG (Scalable Vector Graphics) images as well as complex html widgets.
It provides a mechanism to output perfectly indented/readable XML/HTML/XHTML/WML/SVG source, and a programmatic API to generating XML/HTML/XHTML/WML/SVG on the fly.
Enhancements:
- fixed a problem with the ADODBDataListSource not doing count() properly.
- fixed a problem with the MessageBoxWidget::add_button() not working when an action contained a .html url
- Got the FormWizard to work. It should be useable now. It requires a child of the StandardFormContent.
- Changed FormValidation::is_name() to allow a second parameter to specify the max allowable length.
- Added ordering capability to the FEComboListBox
- Added 3rd parameter to DefaultGUIDataList::action_button() to support extra js prior to the submit being called.
- changed the order in which the content for the head are rendered for the HTMLPageClass. All external links are now built first before the inline js and css is added.
- changed the css class name of the DefaultGUIDataList column header links to resolve a conflict with the FERadioGroup text links
- changed FECheckBox clickable text to use the same css class name as the FERadioGroup clickable text. form_link
- Added a new optional parameter to the FormElement::get_element_name() so it can be called statically to discover an elements name that is used in the form, based on a string.
- First pass at a working FormWizard. Its still combersome a bit.
- Added an index parameter to FormElement::build_id_name() for building consistent ID strings for complex FormElement children.
- Added new FEColorPicker with some used JS code from http://www.mattkruse.com/javascript/colorpicker
- Fixed an issue with the FEComboListBox when manually calling set_value().
- The right hand side data wasnt being merged properly with the left hand data.
- Brian Laird added code to have a list of required selected values for the FEComboListBox.
- added XMLTagClass::get_tag_attribute()
- Fixed a problem of the DefaultGUIDataList missing the wrapping form tag when someone has added an action column.
- Fixed a minor issue with the FEHidden element with a value of 0 and php5
- Fixed a small issue with the FormProcessor building a hidden element that wasnt W3C compliant.
- Fixed a potential problem with the FEDate element being used more than once in a form.
- Added https support to the FormValidation::is_url().
- Added InfoTable::set_title_css()
- Added Daniel I. Roberts PEARDB_DataObjectDataListSource
- Fixed some validation issues with FEFile

LibTomCrypt is a comprehensive, modular, and portable cryptographic toolkit that provides developers with a vast array of well known published block ciphers, one-way hash functions, chaining modes, pseudo- random number generators, public key cryptography, and a plethora of other routines. It has been designed from the ground up to be very simple to use. It has a modular and standard API that allows new ciphers, hashes, and PRNGs to be added or removed without change to the overall end application. It features functions for easy handling and a complete user manual which has many source snippet examples.
LibTomCrypt is a fairly comprehensive, modular and portable cryptographic toolkit that provides developers with a vast array of well known published block ciphers, one-way hash functions, chaining modes, pseudo-random number generators, public key cryptography and a plethora of other routines.
LibTomCrypt has been designed from the ground up to be very simple to use. It has a modular and standard API that allows new ciphers, hashes and PRNGs to be added or removed without change to the overall end application. It features easy to use functions and a complete user manual which has many source snippet examples.
LibTomCrypt is free for all purposes under the public domain. This includes commercial use, redistribution and even branching.
Main features:
- Public domain and open source.
- Written entirely in portable ISO C source (except for things like RNGs for natural reasons)
- Builds out of the box on virtually every box. All that is required is GCC for the source to build.
- Includes a 90+ page user manual in PDF format (with working examples in it)
- Block Ciphers
- Ciphers come with an ECB encrypt/decrypt, setkey and self-test interfaces.
- All ciphers have the same prototype which facilitates using multiple ciphers at runtime.
- Some of the ciphers are flexible in terms of code size and memory usage.
- Ciphers Supported.
- Blowfish
- XTEA
- RC5
- RC6
- SAFER+
- Rijndael (aka AES)
- Twofish
- SAFER (K64, SK64, K128, SK128)
- RC2
- DES, 3DES
- CAST5
- Noekeon
- Skipjack
- Anubis (with optional tweak as proposed by the developers)
- Khazad
- Changing Modes
- Modes come with a start, encrypt/decrypt and set/get IV interfaces.
- Mode supported.
- ECB
- CBC
- OFB
- CFB
- CTR
- One-Way Hash Functions
- Hashes come with init, process, done and self-test interfaces.
- All hashes use the same prototypes for the interfaces.
- Hashes supported.
- MD2
- MD4
- MD5
- SHA-1
- SHA-224/256/384/512
- TIGER-192
- RIPE-MD 128/160
- WHIRLPOOL
- Message Authentication
- FIPS-198 HMAC (supports all hashes)
- FIPS pending OMAC1 (supports all ciphers)
- PMAC Authentication
- Message Encrypt+Authenticate Modes
- EAX Mode
- OCB Mode
- Pseudo-Random Number Generators
- Yarrow (based algorithm)
- RC4
- Support for /dev/random, /dev/urandom and the Win32 CSP RNG
- Fortuna
- SOBER-128
- Public Key Algorithms
- RSA (using PKCS #1 v2.1 and PKCS #1 v1.5)
- DH (using ElGamal signatures and simple DH encryption)
- ECC (over Z/pZ, ElGamal Signatures, simple DH style encryption)
- DSA (Users make their own groups)
- Other standards
- PKCS #1 (both v1.5 and v2.0 padding)
- PKCS #5
- ASN.1 DER for INTEGER types.
Enhancements:
- The ECC code was fixed, cleaned, and improved.
- GCM was fixed.
- UTF8 support was added to the ASN1 code.
- The documentation was improved.
- The published version of the manual is included.

view3dscene project is a viewer for 3D scene files.
Main features:
- Two navigation methods are available: Walk (walking like in FPS (Doom, Quake) games, with collision detection, gravity and related features available) and Examine (this allows you to easily rotate and scale the whole model).
- Convertion of 3DS, OBJ and GEO files to VRML 1.0
- You can also simply open and save any VRML 1.0 or 2.0 file and in effect view3dscene will work as a "pretty-printer" for VRML files.
- Built-in ray-tracer (that is also available as a separate command-line program, rayhunter) to generate nice views of the scene (with shadows, mirrors, and transmittance). Classic ray-tracer implements exactly VRML 97 lighting equations.
Supported file formats:
- VRML 1.0 and 2.0. Almost complete VRML 1.0 support is ready. VRML 2.0 (aka VRML 97) support is also done, although some advanced features are missing right now (like prototypes, scripting, interpolators, sensors). VRML files usually have WRL extension.
- See VRML implementation status for detailed list of supported features. See also my extensions to VRML, my VRML test suite, and finally the official VRML specifications.
- Also many OpenInventors 1.0 ASCII files (extension IV) are handled. Mainly its because Inventor 1.0 and VRML 1.0 are very similar formats, but view3dscene handles also some additional Inventor-specific nodes.
- 3d Studio 3DS format. Not every information in 3DS is handled by view3dscene but most important things, like materials, texture coordinates and texture filenames are supported.
- Wavefront OBJ files. Only very basic support : geometry and texture coords. Texture named default_obj_texture.png in the current directory will be used if texture coords are specified in the file.
- GEO. Some simple format; I dont even know what program writes files in this format, it just happened that I had a few files in this format. No, its not Videoscape GEO and its not Houdini GEO.