Jump to content

luke

Active Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by luke

  1. Another hint to WASTE in the TXT record of darknet.hak6.org, although I personally couldn't get the zone transfer to work on my machine.

    Edit: NVM, Darren secured it later in the episode.

    Think he's seen your post and un-secured it again!

    $ fierce -dns hak6.org -prefix hosts.txt -ztstop
    Fierce 2.0beta-r406 ( http://trac.assembla.com/fierce )
    
    Starting Fierce Scan at Sun Oct 17 12:15:03 2010
    Args:  -dns hak6.org -ztstop 1 -prefix hosts.txt
    Scanning domain hak6.org at Sun Oct 17 12:15:03 2010 ...
    
    hak6.org - 66.11.227.124
    
    Nameservers for hak6.org:
        ns1.zoneedit.com     69.64.67.242
        ns4.zoneedit.com     216.98.150.236
    ARIN lookup "hak6":
    Zone Transfer:
        ns1.zoneedit.com     Success!
      hak6.org.     7200    IN      SOA     216.98.150.236. soacontact.zoneedit.com. (
                                            2010416360     ; Serial
                                            2400   ; Refresh
                                            360    ; Retry
                                            1209600; Expire
                                            300 )  ; Minimum TTL
    hak6.org.       300     IN      NS      ns4.zoneedit.com.
    hak6.org.       300     IN      NS      ns1.zoneedit.com.
    hak6.org.       300     IN      A       66.11.227.124
    smtp.hak6.org.  300     IN      A       66.11.227.124
    darknet.hak6.org.       300     IN      TXT     "dontWASTEyourtime"
    pop.hak6.org.   300     IN      A       66.11.227.124
    mail.hak6.org.  300     IN      A       66.11.227.124
    www.hak6.org.   300     IN      A       66.11.227.124
    irc.hak6.org.   300     IN      CNAME   irc.secfo.org.
    chat.hak6.org.  300     IN      CNAME   irc.secfo.org.
    beta.hak6.org.  300     IN      A       64.202.189.170
    vpn.hak6.org.   300     IN      A       66.11.227.124
    
         ns4.zoneedit.com    Success!
      hak6.org.     7200    IN      SOA     216.98.150.236. soacontact.zoneedit.com. (
                                            2010416360     ; Serial
                                            2400   ; Refresh
                                            360    ; Retry
                                            1209600; Expire
                                            300 )  ; Minimum TTL
    hak6.org.       300     IN      NS      ns4.zoneedit.com.
    hak6.org.       300     IN      NS      ns1.zoneedit.com.
    hak6.org.       300     IN      A       66.11.227.124
    smtp.hak6.org.  300     IN      A       66.11.227.124
    darknet.hak6.org.       300     IN      TXT     "dontWASTEyourtime"
    pop.hak6.org.   300     IN      A       66.11.227.124
    mail.hak6.org.  300     IN      A       66.11.227.124
    www.hak6.org.   300     IN      A       66.11.227.124
    irc.hak6.org.   300     IN      CNAME   irc.secfo.org.
    chat.hak6.org.  300     IN      CNAME   irc.secfo.org.
    beta.hak6.org.  300     IN      A       64.202.189.170
    vpn.hak6.org.   300     IN      A       66.11.227.124
    
     Ending domain scan at Sun Oct 17 12:15:03 2010
    Elapsed time 3 seconds
    Ending Fierce Scan
    
    End Time: Sun Oct 17 12:15:06 2010
    Total Elapsed Time: 3 seconds

  2. A good counter shouldn't increment if it's the same visitor pressing the refresh button :P

    FWIW, my take on the idea of a Hak5 darknet is that it was/has become a self-fulfilling prophecy. On looking back at the episode that spawned this thread, I think Darren was simply that high that he dropped the AACS key in there for kicks; an easter egg for those with a sharp eye; reliving that period in time when everyone was creatively reposting the key across the internet.

    But then, after seeing it interpreted as a hint to a darknet due to its coincidental placement in the final cut of the episode, the idea of a darknet appeals to Darren so he actually creates one and follows the unintentionally-set precedent of making allusions to it in the episodes, which is ultimately what we have now:

    • an indubitable 10-digit hex number, repeated several times (EEF5204D6A)
    • a TXT DNS record whose content is also this number (darknet.hak5.org)
    • a reference to port 1337
    • the promise that it will all make sense over time

    Possible?

  3. How did you get that address? from fierce or how?

    apache2-linus.tobias.dreamhost.com (69.163.251.47)

    So if we know that he is running waste at apache2-linus.tobias.dreamhost.com (69.163.251.47)

    but do we have any clue what those codes are?

    I'm afraid it's likely a red herring. I explicitly specified port 1337 when nmapping the hosts, all turned up closed except webcam.hak5.org (69.163.251.47), which was filtered. Just a different firewall config on that particular host. :(

  4. Then I also think that darknet.hak5.org is not on port 1337 but it is on port 7331, because Darren writes www.hak5.org in reverse "org.hak5.www" Hi also writes one of the ports in reverse (25 -> 52)

    I assumed Darren wrote the name backwards because that's how DNS lookups are executed. The port looked like a genuine mistake when he wrote it, but that's just the vibe I get. As VoodooTorture points out, WASTE's native port is 1337.

    I ran Fierce (also on a Macbook curiously enough ;) ) - its output is pretty ordinary:

    bbs.hak5.org
    beta.hak5.org
    chat.hak5.org
    cs.hak5.org
    forums.hak5.org
    lists.hak5.org
    mail.hak5.org
    radio.hak5.org
    streaming.hak5.org
    voice.hak5.org
    webcam.hak5.org
    webmail.hak5.org
    wiki.hak5.org
    www.hak5.org

    And then running nmap on the resolved hosts (I've removed closed ports):

    Interesting ports on 66-11-227-124.managemyvps.com (66.11.227.124):
    PORT     STATE    SERVICE
    21/tcp   open     ftp
    22/tcp   open     ssh
    25/tcp   open     smtp
    53/tcp   open     domain
    80/tcp   open     http
    110/tcp  open     pop3
    111/tcp  open     rpcbind
    135/tcp  filtered msrpc
    139/tcp  filtered netbios-ssn
    143/tcp  open     imap
    443/tcp  open     https
    445/tcp  filtered microsoft-ds
    993/tcp  open     imaps
    995/tcp  open     pop3s
    3306/tcp open     mysql
    
    Interesting ports on listserver.dreamhost.com (66.33.216.120):
    PORT     STATE    SERVICE
    21/tcp   open     ftp
    22/tcp   open     ssh
    25/tcp   open     smtp
    80/tcp   open     http
    111/tcp  filtered rpcbind
    135/tcp  filtered msrpc
    139/tcp  filtered netbios-ssn
    445/tcp  filtered microsoft-ds
    587/tcp  open     submission
    
    Interesting ports on sub4.mail.dreamhost.com (208.97.132.231):
    PORT     STATE    SERVICE
    25/tcp   open     smtp
    110/tcp  open     pop3
    135/tcp  filtered msrpc
    139/tcp  filtered netbios-ssn
    143/tcp  open     imap
    445/tcp  filtered microsoft-ds
    587/tcp  open     submission
    993/tcp  open     imaps
    995/tcp  open     pop3s
    
    Interesting ports on webmail.dreamhost.com (208.97.187.139):
    PORT     STATE    SERVICE
    80/tcp   open     http
    135/tcp  filtered msrpc
    139/tcp  filtered netbios-ssn
    443/tcp  open     https
    445/tcp  filtered microsoft-ds
    
    Interesting ports on apache2-linus.tobias.dreamhost.com (69.163.251.47):
    PORT     STATE    SERVICE
    1337/tcp filtered waste

    AFAIK filtered ports are as good as closed, I think the only difference is whether packets are dropped or rejected.

    Remember, the domains Fierce found are only exposed using a wordlist; they aren't comprehensive. I'd be interested to see what Darren wants to show us on the subject of zone transfers...

  5. Consider the implications if the authorities publicly admitted that they had the ability to crack strong encryption?

    At the present time it's purely a question of computational power. The cops can set a whole farm of computers working on cracking an encryption key, but even if they get lucky and find it, they won't have "solved" any real problem - they'd have to start right back at square 1 following the exact same algorithms to crack another key.

    Hypothetically speaking, if the cops were to crack the key in the case of this article they would have to handle the situation very gingerly, as I'm sure the public would expect them to be able to crack the keys of every defiant criminal from then on.

    I've not done my homework on the subject but apparently quantum computing may bring encryption-cracking into the realm of feasibility, the implications of which I can only imagine (HTTPS anyone? :unsure: )

×
×
  • Create New...