commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
Also works with files:
cat file
Hello world
base64 file
SGVsbG8gd29ybGQK
To decrypt use the -d option:
echo SGVsbG8gd29ybGQK | base64 -d
Hello world
There are 4 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
Encryption is not the word I would use. Because what you are doing is not by any means creating a difficult-to-read version, since anybody has the tool to "decrypt" it.
I would rather use the word "obfuscation", and I'm not even so sure of that.
It's not encryption. It's hashing. Use gpg for encryption, or some other tool like truecrypt. My fav algo is rijndael
Base64 is not hashing either. it is simply character translation, encoding 8 bit characters into 6 bits. Useful for stuff that cannot handle full ASCII such as email. Use something like md5 for a true hash.
it's called coding. Not encryption
Yes, this is encoding, not encryption. The benefit of base64 encoding, though, is that any arbitrary binary stream may be base64-encoded. (ASCII has nothing to do with it. In fact, to be precise, ASCII is a 7-bit encoding scheme. Anybody remember parity bits?)
Encryption method are not necessarily hard to break. base64 is an encryption method as it turns plaintext into something that you can only read if you have special knowledge. It is not the worst method either; a Cesar cipher like rot13 maps identical characters in the plaintext to identical characters in the ciphertext, base64 does not.
> Yes, this is encoding, not encryption.
Yes, you`re right.
I changed the title from "encryption" into "encoding".
Do not add a line break in your codded string. Use the -n echo's option:
echo -n "Hello world" | base64