Metasploit provides useful information and tools for penetration
testers, security researchers, and IDS signature developers. This
project was created to provide information on exploit techniques and to
create a functional knowledgebase for exploit developers and security
professionals. The tools and information on this site are provided for
legal security research and testing purposes only.
Subpackages:
mysql - mysql database backend.
postgresql - postgresql database backend.
help from nicm@, benoit@ and jeremy@
ok jasper@ and jeremy@ (of some earlier version)
Native TLS protocol implementation, focusing on purity and more
type-checking.
Currently implement the SSL3.0, TLS1.0 and TLS1.1 protocol. Not yet
properly secure and missing some features. Do not yet use as replacement
to more mature implementation.
Only RSA supported as Key exchange for now.
ok kili@
Certificates and Key reader/writer. At the moment only X509 certificate
and unencrypted private key are supported, but will include PGP
certificate and pkcs8 private keys.
ok kili@
Collection of crypto hashes, with a practical incremental and one-pass,
pure APIs, with performance close to the fastest implementations
available in others languages.
feedback and ok kili@
Generic interface for cryptographic operations, platform independent
quality RNG, property tests and known-answer tests (KATs) for common
algorithms, and a basic benchmark infrastructure. Maintainers of hash
and cipher implementations are encouraged to add instances for the
classes defined in Crypto.Classes. [..]
ok kili@
Previously, we were using ruby->=1.8,<=1.9, instead of
ruby->=1.8,<1.9. While this wouldn't cause an issue, since
our ruby-1.9.2 package isn't included in ruby->=1.8,<=1.9,
it's still wrong and should be fixed. This also fixes the
following minor issues:
Switch from using FLAVOR to MODRUBY_FLAVOR for *_DEPENDS.
Currently we don't have a ruby port that uses FLAVORs that
would differ from MODRUBY_FLAVOR, but it's possible we will
in the future.
Switch from BASE_PKGPATH to BUILD_PKGPATH in a few cases in
REGRESS_DEPENDS. This probably is not strictly necessary, but
BUILD_PKGPATH is used in more cases, so it is good for
consistency.
Switch to new style *_DEPENDS, with the version specification
at the end. The remaining cases where this is not done is
because a specific version is used.
Some FULLPKGNAME added to REGRESS_DEPENDS, to make sure that if
the old version is installed when you run a regress test, it
will install the new version first.
Some conversion of spaces to tabs for consistency.
OK landry@
