Skip to content

Instantly share code, notes, and snippets.

@Bios-Marcel
Last active June 9, 2019 19:41
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Bios-Marcel/b8b8b31715290ba45efea9ce64a98933 to your computer and use it in GitHub Desktop.
Save Bios-Marcel/b8b8b31715290ba45efea9ce64a98933 to your computer and use it in GitHub Desktop.
My document regarding OpSec

OpSec - The definitive guide

Hello there fella. I have written this guide in order to help you, who might be my future self, to maintain operational security while searching for security vulnerabilities and whatever not.

Contents

  • What is operational security
  • Why is this important
  • How to maintain OpSec
    • Behaving correctly
    • Avoiding creation and leakage Metadata

Why is this important

There are basically two kinds of hackers, the black hats and the white hats. The black hats are trying to attack others in order to harm them, gain money or out of political interest. The white hats on the other hand try searching for security vulnerabilities or in rare cases even fix them temporarily. However, to the victim, both kinds seem like a threat. In order to avoid legal consequences or even physical harm to you or your family, you should maintain operational security.

TODO

MISC - Restructure

Disabling your bash history

Since your bash history can reveal a great deal of what you've done during your previous session, it's wise to clear it.

Clearing the history works by either deleting or clearing the file ~/.bash_history, which will leave the history in memory. Or clearing the history via the designated command and flushing it afterwards.

# Clears history from memory
history -c
# Flushes current memory-content to ~/.bash_history
history -w

This can either be done manually or on shutdown by using whatever mechanism your distribution offers.

Alternatively, if you want to do this in a rather distribution independent way, you could that line to your ~/.bashrc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment