Free bitdefender professional 7 software for linux

NuSphere PhpED IDE is a professional integrated development environment.

NuSphere PhpED is intended mostly for building database-driven web-applications using php scripting language, although a lot of other popular languages such as HTML, XML, CSS, Perl, Javascript, Python are supported.

PhpED is a robust code editor, powerful php debugger, profiler and publisher – all-in-one. It also includes integrated database and CVS clients, SOAP services, HTML validator and Code Formatter tools, Terminal support and much more.

VirtualBox application is a family of powerful x86 virtualization products for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU Public License (GPL). See "About VirtualBox" for an introduction; see "InnoTek" for more about our company.

Presently, VirtualBox runs on Windows and Linux 32-bit hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista), DOS/Windows 3.x, Linux (2.4 and 2.6), and OpenBSD.

VirtualBox is being actively developed with frequent releases and has an ever growing list of features, supported guest operating systems and platforms it runs on. VirtualBox is a community effort backed by a dedicated company: everyone is encouraged to contribute while InnoTek ensures the product always meets professional quality criteria.

eZ publish is a popular open source content management system and development framework. eZ publish project is distributed, developed and supported by eZ systems. eZ systems is a commercial company, founded by experienced and open-minded people. The company builds its business by providing services around the eZ publish system. For more information about eZ systems, read the "What is eZ systems?" section.
eZ publish allows the development of highly professional and customized internet solutions and dynamic web applications. It can be used to build anything from a personal homepage to a multinational corporate website with role based multiuser access, online shopping, discussion forums and other advanced functionality. In addition, because of its nature of openness, eZ publish can be easily plugged into, communicate and coexist with existing IT-solutions.
eZ publish comes with a wide range of advanced built-in features, which make it possible to develop professional, complex, secure and reliable solutions within a short amount of time. In addition to the built-in features, the system allows for extensions and custom modifications in almost any direction. Unlike other content management systems, eZ publish delivers a flexible, generic solution with very few limitations. In other words, this is a scalable and dynamic system that companies and organizations can grow with.
eZ publish is platform independent. It can be used on Windows and several UNIX variants such as OS X, Linux, FreeBSD, Solaris, IRIX, etc. In addition, eZ publish is also database independent; if a specific database isnt supported, it is possible to write a driver without modifying any kernel code.
eZ publish is open software, supporting open standards. The software is constructed following strict development processes in order to ensure high technical quality and usability.
eZ publish is dual licensed. There is a GPL (General Public License) and a professional license. Using the GPL license, people can build their own open source applications and thereby contribute to the development of free and open software. The professional license allows companies to make and sell commercial software that is developed using and/or built upon the eZ publish system.
Enhancements:
- Several bugfixes and enhancements.
- The command line package tool ezpm.php has been updated: list, import, and install commands have been changed to match the admin interface functionality.
- The ezinstallscript and ezextension items are supported by the add command. ezpm is allowed to set the vendor.
- Enhancement #010347 (progress output for correctxmltext.php and updatetypedrelation.php) has been implemented.

BitDefender FE is just a frontend for BitDefender Antivirus Console.
Enhancements:
This version was necessary because of the modifications applied by BitDefender on their Console antivirus.
- Modification of the GUI
- Added Interface settings (for quarantie and log file folder)
- Added automatic antivirus update with the use of cron service.
- Now you can find the license in the application.

RLIB is a reporting engine that makes it possible to easily create professional reports in PDF, HTML, text, and CSV from one simple XML report definition file.

RLIB supports direct input from MySQL, PostgreSQL, ODBC, and programmable pluggable inputs. It is written in C and has PHP and Python language bindings built in.

Glpi_1 is a Linux Professional Institute test Level-1 (101 and 102 exams) for Gnome/GTK+.

Glpi_1 software is written in Free Pascal Compiler (FPC).

sign is a file signing and signature verification utility. Its main purpose is to be a simple and convenient extension to a tar/gz/bzip2 line of tools to check file integrity and authenticity. Its small and simple, it does just one thing and hopefully does it well.

I needed a tool to digitally sign a bunch of .tar.gz and to allow recepients of the files to easily check, unzip, untar and start enjoying the content as quickly and painlessly as possible.

There are OpenSSL, GnuPG, PGP and others and they are of course perfectly capable of file signing. OpenSSL is probably the most widely spread one and best suited for the role of being a universal signing utility. However the state of affairs is such that OpenSSL as an application is not really used for anything more than generating tarball MD5 hashes. The other packages are plain big and complex for a simple task of file integrity checking. Its like getting a professional sound editing suite instead of a dead-simple .mp3 player. The larger crypto-packages also tend to lack modularity in a sense that to get file signing working I would need to configure a handful of core, but otherwise unrelated settings first. Besides if I am not going to use anything but a signing code, the rest will be sitting there collecting dust, creating untrivial shared libraries dependencies and a general feeling of a wasted disk space.

First of all, sign is a file processing tool, it reads from the files (including stdin) and writes to the files (including stdout). It can be used to attach signatures to the files or to verify and/or strip them.

Between signing and verifying latter will account for a bulk of usage. When checking the signature, sign will check for both integrity and authenticity of the file. An integrity check is done by validating SHA-1 hash embedded into the signature, and an authenticity is ensured by checking signers credentials against a trusted list.

sign adopts OpenSSH-style authentication model, where the trust hierarchy is flat (no certificates), an authentication is done with public keys and the list of trusted keys is grown gradually on as-needed basis.

Every trusted key is associated with a file name prefix called the title. The key can be trusted for signing files, whose name start with keys title. The same key may be associated with more than one title, but not vice versa.

The signature is appended at the end of the file and it carries three bits of information - the title, the public key of the signer and the hash of all preceeding data encrypted with signers private key. The verification is performed as follows:

The filename is checked to start with a title
The hash is decrypted using the public key
The hash is compared to the locally computed value (this ensures integrity)
The title is looked up locally; if its known and associated public key is the same as in the signature, the file is deemed authentic.
Otherwise if the title is known, but the key is different, the file is considered to be signed by untrusted, impersonating party and the check fails.
And lastly, if the title is unknown, the authenticity of the file cannot be established. The user is provided with public key fingerprint, which should be manually authenticated. Then the title and the key are added to the trusted list; and subsequent signatures from the this signer for this particular title will be cleared automatically.

In order to sign files, the signing keypair must first be generated. The keypair is maintained on per-user basis and can be created by running sign with a special command-line flag. The signing process itself is as follows (give or take insignificant details):

Run the filename through a list of owned titles and find the best match. Alternately accept explicit title from the user using one of the command-line flags.
Attach the title, attach public signing key
Compute the hash, encrypt it with private signing key
Attach encrypted hash.

For details on command-line syntax and other operating parameters, please refer to a man page; an online version is here.