Jump to content

zemsten

Active Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by zemsten

  1. Kung Fu Jesus:

    Get off your damn high horse, I don't see you hosting any shows around here. I think the cast is doing a wonderful job. I also think -- as already stated about 100 times -- that you should focus more on feedback and constructive suggestions, rather than directly insulting the cast. Even if you hate the suggestion because you feel your insults are necessary, just have some class and stop being a douche.

  2. In episode 412, Darren shows how to reroute the network traffic from the wireless clients to the Internet and sniff all their packets. He did this with his Windows laptop.

    Being a die-hard Linux user, I decided to do the same with my Ubuntu laptop.

    Here is a step-by-step tutorial how to do this:

    http://dimitar.me/?p=277

    If you have any questions or suggestions, let me know.

    The only thing I noticed was the misspelling of "Jasager" with a "Y."

    Very well written in my mind otherwise. Cheers.

  3. You can see the mac address of any connected client, and which AP the client is associated to.

    Shit, I'm retarded. I can't believe I overlooked that, I broke my neighbors WEP encryption a few months back and used Kismet and the aircrack-ng suite, so I even knew that. *Brain Fart*

    Thanks for the correction though. :)

  4. This is security also, but it's more backend and doesn't require passwords and such. If you want to have an unsecured network, MAC filtering is a good option. That way you allow only the computers you own to use the network. Although MACs can be spoofed, you can't find out what the allowed MACs are, so it'd be quite a long operation to spoof a correct MAC.

  5. An SSH client won't connect to any open port and allow you to interact with it, telnet will.

    Good point. That was supposed to in reply to the earlier post. I was thinking in a more narrow spectrum, as in remoting in to another computer. And in my opinion, SSH is a perfect utility for that.

  6. I think that having a private exit node pool would defeat the purpose. To make this pool private, it would have to have some sort of security -- such as a password, or security by obscurity. Either way, the user would have to know something about the node(s) and would therefore reduce the amount of anonymity.

    In reply to the other idea, I think that may be possible, but it'd probably have to be a https request on port 443, and because TOR is a tunnel, I'm not sure if it would get to the right port at the end. Each packet sent through TOR has a header with instructions to take it through the hops in the tunnel. Any single node can only read its own part of the header, so that particular node can't tell where the packet came from or where it is going. If you knew about the private exit node, then the hops in the middle would be pointless, because where the traffic was exiting would be known. At least, that is my theory.

  7. Not costing anything also includes having enough bandwidth to run it without interfering with anything else.

    But I wouldnt want the damn FBI or something sitting in front of me looking for people using tor for malicious purposes.

    Running a tor exit node is actually another way to have probable deniability. If you're operating a Tor exit node, you can claim that the traffic participating in illegal activity was not yours. Because the tor "hops" are encrypted, the authorities would have to do some work to find out where it originated. If you have enough bandwidth, it's actually not a bad idea to run an exit node.

    Cheers. :)

×
×
  • Create New...