Search the Community

So recently my Amazon account was hacked (my fault due to weak password I guess) and my Steam account attempted to be accessed at the same time along with several of my other accounts as well. So luckily Amazon reversed the transaction made and Steam sent me an email (thank god for multi factor authentication) and Steam also sent me the IP address of the attacker, I have pinned down the location to a residential apartment in Russia, my question is what next as they keep trying to gain access every few months?!?!?

How will I know the contents of a specific https://s3-ap-southeast-1.amazonaws.com bucket, e.g. https://s3-ap-southeast-1.amazonaws.com/cutepuppies? I don't have any access with the site but I'd like to know if I will be able to get some freebies from it, what should I do? How will I be able to see those files which I can freely download for any https://s3-ap-southeast-1.amazonaws.com bucket ? (attach is the image) I should've known about hak5.org earlier. Thank you guys!

I'm trying to configure AutoSSH to connect to my relay server, which happens to be an Ubuntu 12.04 instance hosted by Amazon's EC2 service. They use .pem certificates. I like them; they're easy. I don't have to mess around with public keys and private keys and Bob and Alice. Sadly, though, the MK5's web UI no longer allows me to specify the command line for AutoSSH, where it seems (at least in previous versions of the UI) I would have been able to replace the "-i /etc/dropbear/id_rsa" with "-i key.pem" and have it work all the same. I followed all the instructions in episode 1112 and (the relevant parts of) Chris Haralson's tutorial. I hoped that doing so would obviate the need for the "-i key.pem" argument when autoSSHing with Amazon's EC2. It did not. When I try to test AutoSSH, it does not connect to the EC2 instance. I need your help. As I see it, there are at least three avenues for solutions: 1) Change a config file in the pinapple's bowels to use an "-i key.pem" argument for AutoSSH (such as I have used successfully when setting up manual SSH sessions - no password required). I prefer this option, for what it's worth. 2) Make the EC2 instance accept whatever crypto the pineapple wants to serve it (what do we call it? an RSA key?). This is basically what I've tried to do so far, by following the instructions given in Darren and Chris's tutorials. It hasn't worked so far, but maybe there's more monkeying around in the server's "sshd_config" or "authorized_keys" that I can still do? 3) Convert Amazon's .pem key into an RSA (public?) key (or whatever it's called) format? Then maybe replacing the contents of the some key file deep in the pineapple's bowls with the output of the pem->rsa conversion? I am not sure this can actually be done; results of preliminary googling are all above my head. Can you folks help me work this problem, walk me through steps for solving it? Thanks in advance.