/silicon/ - technology

http://grugq.github.io/images/blog/jihobbyist_fan_club.jpg

like sayin "sec" huh?

>>71
for those who want to come and say, "Herp derp! Wut's upsex?" It's how to secure your fekkin operation.

This isn't opsec 101 here. We're looking for specific, in depth analysis of opsec practices. Not the inept ramblings of some WSJ Pleb who doesn't even know how to use pgp.

What do you want to talk about? Digital opsec, specifically? Or opsec all around? When dealing with opsec, like with all security, it's a cost-benefit analysis, although it's a bit different for active opsec than for passive opsec. Basically, passive OPSEC is things like: not talking about sensitive information, whereas active OPSEC actually requires you to DO something, rather than NOT DO something (lock up data, whatever).

>retards beginner guide 1.0
>ask specific questions about where you are wanting to go next
>and I will answer them if I can in my next post. (If I can't, I find the answers!)

I should know way more about this considering the amount of time I've spent on it! Anyway, OPSEC is like many things - only as strong as the weakest link! Breaking OPSEC and revealing your most valuable possession - your identity - makes all of the hard work you've done to stay Sushi Roll to that point fruitless. That would be a terrible thing, wouldn't it? Don't ever link to your Google, Facebook, or Twitter accounts from a source where you wouldn't want everyone to know who you are.

1/?

>>239

First, you need to evaluate what level of OPSEC you are wanting to shoot for. Are you a California Roll (I actually think this censoring is fun >.<) just wanting to to stand for liberty and privacy? The steps you take to protect your identity will be different than those you would if you were Edward Snowden! You may just want a VPN paid for with Bitcoin so you can download a car with peace of mind, or maybe you are going to want to be booting TAILS live from a USB using a T60 with Libreboot and no HDD. Start thinking of how deep you will go in the tin-foil hole now. I'm going to begin with some steps everyone can take.

>2016
>not using full disk encryption

There is literally no excuse. Whether it's your laptop or smartphone, full-disk encryption (preferably with near uncrackable AES-256) prevents anyone with physical access to your devices from being able to go through your files. While it's a start, simply encrypting your /home partition doesn't cut it to the same degree. Your logs in /var and installed programs in /opt and /usr can tell so much about you, in and of themselves. Your safest bet is to only leave your /boot partition readable w/o decryption.

2/?

>>240

>encrypting directory/container

So you are wanting to to have an encrypted directory on your external HDD, or perhaps you just want an encrypted container on your Ubuntu install to store GPG keys, passwordz, Bitcoin wallets, etc. What are your options? Well one, you can encrypt tarballs with GPG. This isn't a very quick solution, and requires you to decrypt and untar the directory each time, as well as shred it when you are done. Or (especially if you are on Windows or OS X) you could use Veracrypt (Truecrypt's worthy successor) and easily create an encrypted container. Make sure it is AES-256, though!


>not hiding behind 7 proxies

So great, physical access to your hard drive has been limited by the dank Veracrypt/dm-crypto crap you bricked it with. The NSA is going to only be able to use your drives as a doorstop, should they seize them after you post a photo on Twitter of David Cameron wearing a tiara. But what about your internet activity?

A VPN is one of the simplest ways to go. You can either setup an OpenVPN server yourself on a VPS (Google it.) or you could opt to subscribe to a secure VPN service. You can buy a month of service from a trusted source like Mullvad or AirVPN for ~€5/mo. with Bitcoin, which is a relatively secure and easy way to go. Follow their instructions for your platform, fire it up, and start torrenting/browsing Pixiv. Especially with the larger VPN providers, you have the benefit of using the same IP address as many others, and therefore decreasing the size of your identifiable fingerprint. A key part of this, though, is ensuring that you ARE NOT logged into Google, Facebook, Twitter, Amazon, etc. Otherwise you have blown your cover and can be identified as a member of the VPN service.

>>241

Alternatively, you could buy a VPS with Bitcoin, setup OpenVPN/PPTP, disable logs, and also be able to post to your favorite imageboards or forums that have blocked IPs from major VPNs. The downside is that only you will be posting from this IP, and therefore a larger fingerprint will be created. This is a good choice, though, if you are in public and using your VPN to safely browse Rakuten, Crunchyroll, Twitter, etc.etc. that already know your identity - you are just wanting to hide it from those around you!

I personally use both. A VPS with DigitalOcean on an American server that I run a PTPP server on to access Netflix, my personal banking, imageboards, etc. in places where I am not concerned about my Sushi Rollymity, except from those L337 [email protected]$ around me at the public library or Starbucks who are snooping on my connection. I also have a VPN with a well-rated provider that I paid for with Bitcoin through Tor that I use for torrenting, browsing some imageboards, accessing Tor (I don't do it directly anymore to avoid attracting suspicion from my ISP/Government, although US citizens may be less concerned.) et.al.

>well, that was a crappy summary of things that I already knew

Sorry, senpai ;_; I will post more later, I am just on the subway to work.

EDIT: I derped out and forgot to post it. I'm just getting OFF work and I am on my way home. I have a paper for grad school to work on, though, so I may not be back for some hours.

4/4 (for now)

>>70
>http://grugq.github.io
grugq is a legend. I met him at Hack in the Box 2012; great guy.

Also check his tumblr out,
>grugq.tumblr.com

https://www.youtu.be/9XaYdCdwiWU

>>241
thanks Sushi Roll! I am making a lil moc-up of the guide for future Sushi Rolls.

Here is a jpg version for future reference!

>>251
>>252
Wow! Thank you, Sushi Roll! I feel honored.