Affordable Quality Hosting with Fast Friendly Service
|This page links to several handy forms you can use to do things like - Generate Random passwords, Create simple 16 bit or 32 bit CRC's, Use the Unix/Perl Crypt function online with a random seed, Generate .htaccess files for *NIX systems, Create MD5 Digest string/Signature for text strings, Blowfish Encrypt or Decrypt strings with a key, Bese64 Encode or decode text, Uuencode and Uudecode text.
|Passwords||Generate Up to 500 Random passwords with the ability to determine the composition. For example, you can generate passwords in only uppercase, only lower case, only numbers or any combination of the above|
|CRC||A simple 16/32 bit CRC algorithm. Bytes are converted to the ordinal value, added and then Exclusive OR'ed with either 2E16 -1 (16 bit) or 2E32 -1|
|One way Ciphers|
|Crypt||crypt() encrypts a string using the crypt function from the operating system's C library. Crypt is non reversible.
The function accepts two arguments: the string to encrypt, and the salt to use during encryption. A salt is a string of characters used to increase the number of encrypted strings that can be generated for a given string with a given encryption method. Salts help increase the effort needed to "crack" encrypted data. This online version uses a random two byte salt and works fine for generating .htpasswd files to be used with .htaccess on most *nix systems.
When verifying an existing encrypted string you should use the encrypted text as the salt with the plaintext.
|MD5||Uses the RSA Data Security Inc. MD5 Message Digest algorithm. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit ``fingerprint'' or ``message digest'' of the input.
A binary digest will be 16 bytes long. A hex digest will be 32 characters long. A base64 digest will be 22 characters long.
|Symmetric and asymmetric Cryptography|
|Blowfish||Blowfish is capable of strong encryption and can use key sizes up to 56 bytes (a 448 bit key). The key must be a multiple of 8 bytes (up to a maximum of 56). This example will automatically pad and un-pad the key to size. Because Blowfish creates blocks of 8 byte encrypted output, the output is also padded and unpadded to multiples of 8 bytes.|
|DES||In 1974 IBM submitted to the National Institute of Standards and Technology - NIST (formerly National Bureau of Standards) what was then called the Lucifer algorithm, and later renamed to DES. NIST enlisted the help of the National Security Agency to evaluate the security of Lucifer. At the time many people distrusted the NSA due to their extremely secretive activities, so there was an initial degree of skepticism regarding the analysis of Lucifer. One of the greatest worries was that the key length, originally 128 bits, was reduced to just 56 bits, weakening it significantly. The NSA was also accused of changing the algorithm to plant a 'back door' in it that would allow NSA agents to decrypt information without having to know the encryption key. But these fears proved unjustified and no such back door was ever discovered.
DES encrypts and decrypts data in 64-bit blocks, using a 64-bit key, although the effective key strength is only 56 bits. It takes a 64-bit block of plaintext as input and outputs a 64-bit block of cipher text. Since it always operates on blocks of equal size and it uses both permutations and substitutions in the algorithm, DES is both a block cipher and a product cipher.
|RSA||RSA is an algorithm for public key encryption. It was the first algorithm known to be suitable for signing as well as encryption, and one of the first big advances in public key cryptography. RSA is still widely used in electronic commerce protocols, and is believed to be secure given sufficiently long keys.|
|Epoch||Convert Epoch seconds to and from dates. Add or subtract epoch seconds and or dates.|
|Encoders and Decoders|
|Base64||base64 is a data encoding scheme whereby binary-encoded data is converted to printable ASCII characters. It is defined as a MIME content transfer encoding for use in internet e-mail. The characters used are A–Z, a–z and 0–9 with the "+" and "/" symbols. The "=" symbol as a special suffix code.
Full specifications for base64 are contained in RFC 1421 and RFC 2045 - MIME (Multipurpose Internet Mail Extensions). The scheme works on 8 bit data. The resultant base64-encoded data has a length that is greater than the original length by the ratio 4:3.
Three bytes are concatenated, then split to form 4 groups of 6-bits each; and each 6-bits gets translated to an encoded printable ASCII character, via a table lookup. An encoded string is therefore longer than the original by about 1/3. The "=" character is used to pad the end out to an even multiple of four.
|HTTP Encode||URL encoding of a character consists of a "%" symbol, followed by the two-digit hexadecimal representation (case-insensitive) of the ISO-Latin code reference for the character. Fr example, a space becomes %20|
|Leet Speak||Leet (meaning 'elite', most commonly represented as 1337) is an online culture or attitude sometimes identified by frequent use of leetspeak (a spelling convention for typed words).
The word itself is derived phonetically from the word "elite", and is a cipher, or cryptic form of English spelling - although, in principle, it could also exist in other languages. The spelling convention is intended primarily to circumvent automatic text parsers, probably because the originators of leet felt they may be under some form of surveillance, or desired for other reasons to have somewhat private conversations in public spaces — hence the term elite, as only those 'in the know' could easily read what is said. Leet is widely used in Chat rooms.
|Uuencode/Decode||A set of algorithms for converting files into a series of 7-bit ASCII characters that can be transmitted over the Internet. Originally, uuencode stood for Unix-to-Unix encode, but it has since become a universal protocol used to transfer files between different platforms such as Unix, Windows, and Macintosh. Uuencode is especially popular for sending e-mail attachments. Nearly all e-mail applications support uuencode for sending attachments and uudecode for receiving attachments.
Another popular encoding algorithm is Bin Hex , which is often used for transferring Macintosh files, such as PICT graphics files.
|Morse||In 1836, Samuel Morse demonstrated the ability of a telegraph system to transmit information over wires. The information was sent as a series of electrical signals. Short signals are referred to as dits (represented as dots). Long signals are referred to as dahs (represented as dashes). With the advent of radio communications, an international version of Morse code became widely used.
The very first message ever sent was on May 24, 1844: "What hath God wrought?"
|Numeric and Text Converters|
|HEX||Convert Numbers to Hexadecimal or HEX to numbers|
|Binary||Convert Numbers to Binary or Binary to Numbers|
|OCTAL||Convert Numbers to Octal or Octal to Numbers|
|UPPERCASE||Convert text to UPPERCASE|
|lowercase||Convert text to lowercase|
|Proper Case||Convert Text to Proper Case|
|Human Number||Convert 123 to "one hundred and twenty three"|
|Roman Numerals||Convert numbers to Roman Numerals and back|
|Miscellaneous stuff that did not fit anywhere else|
|BloodGlucose||Just a bit of fun to convert blood sugar levels between different standards|
|Google Page Rank|
© 2002-2013 All Rights reserved.