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:
see what's in your memory right now... sometimes you find passwords, account numbers and url's that were recently used. Anyone have a safe command to clear the memory without rebooting?
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
Of course access to /dev/mem depends on being root or being in the 'kmem' group (on my ubuntu system). But then when accessing memory raw like that as a user, you have no idea whether a particular physical address is currently in use because you do not have access to the kernel's data structures (even as root) if you're thinking of writing to that memory for the purposes of 'clearing' it. At least that's my understanding.
This memory scrubbing is probably best done at the application level, and many applications where security matters a bit more do take steps to clear memory areas before freeing them.
Also, rebooting doesn't necessarily clear the contents of memory: http://en.wikipedia.org/wiki/Cold_boot_attack
/dev/mem should already be restricted to only root or the wheel group ... and if someone untrusted already has root access, you have worse things to worry about than someone sifting through active memory.