Jump to content

iNFERNoN

Active Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

iNFERNoN's Achievements

Newbie

Newbie (1/14)

  1. OK. Thanks guys. I wasn't sure if there was a technique employed by forensics experts that might come in handy here, but that would probably involve an expensive solution. Thanks again.
  2. 'allo everyone. A T-Mobile rep accidentally wiped my brother's SIM card. I wasn't sure if it would be possible to still pull data from the card. I didn't know how SIM memory worked, but I wasn't sure if anyone has tried pulling information from one before.
  3. Gotcha. I was thinking more from a pentesting perspective. If you didn't know anything about your target's network, but were looking for a specific host, how would you go about identifying that box?
  4. I recently went through an awesome artcile in hakin9 magazine that uses a MITM attack to sniff SSL traffic... At any rate, it got me thinking about how you would go about ID'ing your victim. Assuming that you don't have access to the DHCP server and the host names on the network don't resolve to anything worthwhile, how would you figure out which machine belonged to your target? I'm assuming that you can poison the ARP cache so that all traffic on the network is routed through your machine and use deductive reasoning to ID the box, but I'm thinking that there are less detectable and easier ways to accomplish this. Any ideas?
  5. Yep. It says: ssh: connect to host <ip address> port 22: Connection refused If I run ssh in verbose mode, I get the same exact message.
  6. I'm with Joerg. Using apt to install / remove packages will make your life very easy. I know rpm and yum on Fedora / Red Hat are supposed to be nice, but I've never taken the time to learn them.
  7. IP address. I'm sorry. I should have provided these details at first.
  8. My second post is a question?!? I should be ashamed of myself... I'm attempting to VPN into my office and ssh into a Linux box that I have sitting on the network. This is via a typical PPTP connection. If I use my Windows machine, I'm able to VPN in and ssh into the box using putty. The problem arises when I'm on my Ubuntu box. I am able to VPN in, but when I attempt to connect to the box, I receive a message that says connection refused. I've taken a look at the configuration of the VPN connection on my Ubuntu box and I manually added the address range for the office network to the "Only use VPN connection for these addresses' box, but I'm still not getting anywhere. I'm also unable to terminal into any of the Windows boxes on the network. All of this is despite the fact that I'm able to ping each and every machine I'm attempting to communicate with. I'm assuming that the issue is a routing one, but I'm somewhat new to Linux an unsure of how to move forward. Anyone have any ideas?
  9. Greetings everyone. Been lurking for a few days and it looks like this is an awesome community. Looking forward to further lurking and discussion:) Favourite OS: I prefer my Ubuntu Linux box at home, but I still don't have anything against XP (which can be secure if properly configured and maintained, although I wouldn't run it if I didn't need it for games-- what's that really say about it?) and I love my MacBook when I'm on the road. Favourite console: Xbox 360 Age: Under 30 Occupation: Network Engineer Music: Dub, Rock, Electronica, Soul, Jazz... anything really. Currently reading: Beginning Python and Collapse by Jared Diamond Last movie I liked: Iron Man Favorite Hockey Team: Philadelphia Flyers I don't watch TV other than hockey, but my two favorite series are The Sopranos and The Wire
×
×
  • Create New...