Jump to content

mreidiv

Active Members
 View Profile  See their activity

  • Posts

    412

  • Joined

  • Last visited

  • Days Won

    4

 Content Type 

Posts posted by mreidiv

    New Wifi Pineapple (Mark V)?

    in WiFi Pineapple Mark IV

    Posted

    It could be, but I would hope not. A sim card slot would mean a person had to purchase and register a sim card from a mobile carrier (ie AT&T or Verizon). There would no longer be the anonymity of purchasing one at a brick and mortar store with cash and topping it off whenever you need it.

    An SD card would get rid of a USB drive and free up the space for a USB modem or another NIC

    But, you coud purchase a pay as you go phone with a sim card with cash. and some places sell you a sim card and dont check id. But i see your point.

    New Wifi Pineapple (Mark V)?

    in WiFi Pineapple Mark IV

    Posted

    Wondering if the second antenna is just for extra reception, or for a second radio. 2 radios in one case, without the need for an external Alfa? That would be sweet. I did notice that the hakshop recently stopped selling NHA's... very interesting.

    And the video seems to show custom packaging... does that infer a custom board this time?

    not sure but would be neat if it contained an internal battery. Lol Wishfull thinking

    Pineapple sold elsewhere?!

    in Questions

    Posted · Edited by mreidiv

    Alfa is the manufacturer, data-alliance is a distributor. Unless they are the same company.

    Also, directly from the link above.

    "Data Alliance offers this AP with the Hornet-UB board, with Pineapple Mark IV firmware wireless router operating system."

    Yes you are correct that the manufacture is alfa and that Data Alliance is the retailer, Kind of rushe into that one i knew better, But still the hardware is the same but the pineapple firmware is not on the device sold by Data Alliance.

    Show me Yours and I'll show you mine..

    in Classic USB Rubber Ducky

    Red vs Blue

    in Security

    Posted

    I don't know about simulations but here are some tips:

    Red Team

    Before Start of Play
    • Who will be the team organizer? The team organizer documents the networks, system names, OS versions, IP addresses, open ports, passwords, and updates configuration changes for everyone to see (such as on a whiteboard); helps to prioritize tasks; ensures that no systems are forgotten; monitors the functioning of the fictional production application(s) and otherwise maintains the “big picture” and a calm head while others are absorbed in the details and chaos of gameplay.
    • Exactly which port numbers must be available on which systems for the scorebot? Try DoS attacks on these.
    • How will the scorebot confirm that your other target application(s) are still running? Don’t block the scorebot.
    • Which target systems are running the most vulnerable operating systems and/or services (such as IIS, RPC, SMB, and/or older unpatched software versions with known exploits)? Important to prioritize.
    • What special tools will be available? Nmap, Nessus, Metasploit? Best to ask.
    • Does everyone on the team know how to view live ports and established sessions? Does everyone know how to reset a password from the command line? Does everyone know how to escalate privileges on different architectures?
    • Compile a list of default passwords (eg. the ones on your system, the opposing team may forget to change these)
    • Who are you permitted to ask for help if necessary? What can or can’t they do for you?

    When Play Begin

    • Full TCP & UDP Portscans
    • Perform Service Enumeration and Software Version Enumeration on open ports.
    • Interrogate each open port manually with netcat.
    • Don't add new accounts, stay stealthy and use compromised accounts.
    • Don't upload common files that trip Anti-Virus alerts (e.g cain and able).
    • Dump local hashes
    • Dump domain hashes
    • Dump LSA secrets (windows)
    • Dump cached passwords (windows)
    • Snarf session tokens (windows)
    • Finally, focus on your plan and don’t panic!

    Blue Team

    Before Start of Play
    • Who will be the team organizer? The team organizer documents the networks, system names, OS versions, IP addresses, open ports, passwords, and updates configuration changes for everyone to see (such as on a whiteboard); helps to prioritize tasks; ensures that no systems are forgotten; reminds players to periodically check for compromise; monitors the functioning of the fictional production application(s) and otherwise maintains the “big picture” and a calm head while others are absorbed in the details and chaos of gameplay.
    • Exactly which port numbers must be available on which systems for the scorebot? Can’t block these.
    • How will the scorebot confirm that your other target applications are still running? Don’t block the scorebot.
    • Which target systems are running the most vulnerable operating systems and/or services (such as IIS, RPC, SMB, and/or older unpatched software versions with known exploits)? Important to prioritize.
    • What special tools will be available? Process Explorer? WireShark? Tripwire? PowerShell? Best to ask.
    • Does everyone on the team know how to view listening ports and established sessions? Does everyone know how to reset a password from the command line? Does everyone know how to kill a process? Does everyone know how to configure IPSec, the Windows Firewall and/or iptables for packet filtering?
    • Who are you permitted to ask for help if necessary? What can or can’t they do for you?

    When Play Begin

    • Block all non-scorebot-required ports on all systems using IPSec/Windows Firewall/iptables.
    • Assign a different 15+ character long passphrase to every administrative account on every system.
    • Change all default application and service passwords to a different 15+ character passphrase.
    • Remove all accounts from all administrative groups on each system except for one.
    • Delete or disable all user accounts, including Guest, except for the one administrative account on each system.
    • Establish a baseline by saving lists of your current processes, listening ports, services, device drivers, user accounts, and all files (“dir /s /b” or “ls –lARt”) to text files on each machine. If possible, generate a checksum database using a tool like Tripwire (or just md5sum). Use this information to detect compromise.
    • Enable useful audit policies, clear all logs, and keep Event Viewer open (Windows) or “tail –f” critical log files (Linux). When you look at a log, if you notice that the only new events are of no security consequence, clear that log to reduce clutter during the games (it’s not real life).
    • Continuously watch your list of established sessions, running processes, target applications and logs to try to detect malicious changes. Write scripts or use command history (up-arrow or F7) to help automate this work. Detect changes and respond: kill offensive processes, delete new user accounts, delete new binaries, etc.
    • Finally, focus on your plan and don’t panic!

    Thanks man Great info.

    Red vs Blue

    in Security

    Posted

    Me and some fellow clasmates are going to enter a red vs blue competition. Can any one suggest and good simulations that we can practice with to help us out.

    I am looking for some help as i have never entered a contest like this and am new to security. I know alot of the basics. But any help from anyone that has done this befor would be greatly appreciated.

    Thanks

    #4

    DDoS

    in Questions

    Posted · Edited by mreidiv

    I've heard that the anonymous are going to attack **REMOVED** (don't check it out is like a top 100 of porn sites)

    Is that true?

    I’m sure this site as well as many others do not condone illegal activity and that is what anonymous does. There ideology may seem right but their methods are in fact illegal.

    CSS 3.0 Display

    in WiFi Pineapple Mark IV

    Posted · Edited by mreidiv

    My CSS not the best but it works

    .statusBar {
    text-align: center;

    margin: 0 auto;
    padding: 2px;
    width: 95%;

    border: 3px solid red;
    }

    .tiles {
    text-align: center;
    width: 100%;
    margin-top: 2%;
    height: 90%;
    }

    .tiles_wrapper {
    margin: 0 auto;
    overflow-y: auto;
    height: 100%;
    text-align: center;
    }

    .tile {
    text-align: left;
    margin: 1%;

    vertical-align: top;
    display: inline-block;

    width: 22%;
    min-width: 250px;
    height: 250px;
    height: 30%;
    overflow: hidden;

    border: 3px solid blue;
    }

    .tile_title {
    text-align: center;
    text-decoration: underline;
    padding-bottom: 5px;
    cursor: pointer;
    background: green; /*#FC0101*/

    }

    .tile_expanded {
    margin: auto;
    text-align: left;
    color: white;
    background: green;

    position: absolute;
    right: -50%;
    left: -50%;
    border: 3px solid green;
    width: 93.25%;
    height: 85%;
    /*padding: 10px;*/

    overflow-y: auto;
    overflow-x: hidden;
    visibility: hidden;
    }

    .tile_content {
    padding: 10px;
    }

    .tile_content a{
    color: yellow;
    }

    .tile_stretch {
    width: 100%;
    display: inline-block;
    font-size: 0;
    line-height: 0;
    }

    #close {
    position: absolute;
    top: 0.5em;
    right: 0.5em;
    text-decoration: none;
    color: white;
    }

    .popup {
    visibility: hidden;
    position: absolute;
    top: 7%;
    left: 50%;
    min-height: 15em;
    width: 50em;
    ;
    border: solid 2px green;
    background-color: black;
    padding: 1em;
    z-index: 99;
    }

    .entropy {
    color: gray;
    }

    input[type=text], textarea, input[type=password] {
    border: 1px;
    background-color:black;
    color:white;
    border-style:dotted;
    resize: none;
    }


    a {
    color: yellow;
    }

    body {
    background: black;
    color: white;
    font-family: monospace;
    overflow-x: hidden;
    }

    ::-webkit-scrollbar {
    width: 8px;
    padding-right: 10px;
    visibility: visible;
    }

    ::-webkit-scrollbar-track {
    border-radius: 10px;
    padding-right: 10px;
    visibility: visible;

    }

    ::-webkit-scrollbar-thumb {
    border-radius: 10px;
    background: green;
    padding-right: 10px;
    visibility: visible;
    }

    post-38368-0-38527500-1376512637_thumb.p

×
×
  • Create New...