Jump to content

koalamugger

Active Members
  • Posts

    11
  • Joined

  • Last visited

Posts posted by koalamugger

  1. 12 hours ago, PoSHMagiC0de said:

    You might have to apt install python-crypto.  If the pip install did not get it then it is an apt package you will need.

    Yup! my system was grabbing python 3.0 by default, but veil seems to rely on 2.7. I also reinstalled with 32bit instead of 64 Kali and that seems to have alleviated a bunch of the issues. Thanks again man!

  2. On 4/17/2018 at 10:23 AM, Bamse said:

    I am having a problem with fern wifi cracker. 
    The problem is an error message i am getting when selecting a wifi card 

    Here is a picture of the error message
    https://imgur.com/a/OXgcY
     

    Is this a VM? or are you running a machine with a native os? Also, have you made sure that your WLAN0 adapter can sniff?

  3. On 4/30/2018 at 4:34 PM, PoSHMagiC0de said:

    Okay, on my VM I did not have veil-evasion on I did the following and veil works.

    
    dpkg --add-architecture i386
    apt update
    apt upgrade
    apt dist-upgrade
    apt autoremove
    reboot -n
    
    #above I updated everything because my VM was behind but made sure I had the i386 architecture added first.
    #after reboot and logon.
    
    apt update
    apt install wine
    apt install veil-evasion
    veil
    

     

    I told it to install with "Y"

    I reinstalled all the Windows apps for python, ruby, etc...overwriting when I had to.

     

    When done I was in veil and I created a regular https payload using phyperion and default pyinstaller.  It got done with no errors.

    If you have not done so, make veil reinstall/reset so you can reinstall the dependencies.  If having issues resetting. then apt remove --purge veil-evasion and then re apt install it.

    Now if you installed veil from git, well, you will have to figure out how to completely remove it to reinstall it or the one from apt.

    I made progress with the install but now Im getting a runtime error. I checked the directories and made sure that the Crypto folder was upper case as some other forums have mentioed for this issue but not success.

    Here's what I get --

    root@kali:/usr/share/Veil# ./Veil.py
    Traceback (most recent call last):
      File "./Veil.py", line 96, in <module>
        the_conductor = orchestra.Conductor(args)
      File "/usr/share/Veil/lib/common/orchestra.py", line 30, in __init__
        self.load_tools(cli_stuff)
      File "/usr/share/Veil/lib/common/orchestra.py", line 78, in load_tools
        command_line_object)
      File "tools/evasion/tool.py", line 40, in __init__
        self.load_payloads(cli_options)
      File "tools/evasion/tool.py", line 250, in load_payloads
        name.replace("/", ".").rstrip('.py'), name)
      File "/usr/lib/python3.6/imp.py", line 172, in load_source
        module = _load(spec)
      File "<frozen importlib._bootstrap>", line 684, in _load
      File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
      File "<frozen importlib._bootstrap_external>", line 678, in exec_module
      File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
      File "tools/evasion/payloads/auxiliary/pyinstaller_wrapper.py", line 9, in <module>
        from tools.evasion.evasion_common import encryption
      File "/usr/share/Veil/tools/evasion/evasion_common/encryption.py", line 8, in <module>
        from Crypto.Cipher import ARC4
    ModuleNotFoundError: No module named 'Crypto'

     

     

     

  4. On 4/30/2018 at 4:39 PM, PoSHMagiC0de said:

    Oh crap, I didn't see you had ParrotOS installed.

     

    Yeah, prepare for the pain.  I just saw Kali and figured you had Kali.  What is hurting you here is Firejail.  I used to run ParrotOS for about a year and then dropped it because they are really focused on anonymity which a lot of times break the pen tools.  To fix certain pen tools and veil you have two choices.  One, you can run veil tell firejail to not jail it (I forgot the commandline for that, might have to ask on the ParrotSec forums) or do what I did and removed firejail with

    apt remove --purge firejail

     

    Once you do that, you will have to redo veil but I would remove the git one if you got it just because the apt one didn't work.  If you prefer the git one and have it rerun its installer again after you took care of firejail either by running the installer with the commandline to not firejail it or after you removed firejail.

     

    I think I may just grab the new bistro of Kali that was released and run through your first list of instructions. Ill keep you posted. Thanks man! 

    It sucks I have been spending so much time on this lol, all I wanted was a FUD since we have a blind attack parameter for this client. Good times! Thanks again for the help. 

     

  5. 5 hours ago, PoSHMagiC0de said:

    I had issues in the past with Veil.  One thing you have to make sure of is you add the i386 architecture to your apt:

    dpkg --add-architecture i386

     

    Next install wine.  You want to make sure wine64 and win32 installs.  Next, rerun the installer for Veil to make sure everything goes in fine and then try your payload creation again.

    I would also watch the install carefully and look for any errors.  For those I had to install the package myself.  If a pip install failed, you may have to apt-get the package before running pip.

    I will let you know how this goes tomorrow when I test. 

     

    If it works then you are a god, because I've nearly smashed my keyboard 3 times reinstalling everything. This is what I get for losing my image. Thanks! 

  6. Hey Guys!

               I used to run Kali on my pen test workstation, however after a pretty gnarly crash, I moved to Parrot to test out a new flavor of linux (very impressed in some areas, not so much in others). However, I have a test window open with my company where we are going full blind and I need to pull out all the stops for this one. That means I need to create a FUD. Only way I have ever been able to succeed in a FUD is with low level shell script kiddy stuff and Veil-Evasion (sorry, but its just faster) 

    I am having the worst time trying to get Veil to work properly. I have both the previous and curren Gits of Veil, reinstalled, nuked, reimaged, EVERYTHING. At this point i just need some help. (and yes, I have even tried youtube videos, Im not missing anything) 

    The error seems to come up when trying to finalize the payload with Pyinstaller (i fail with Py2EXE as well) 

     

     

  7. hey guys! So I have my new Evil Portal set up and everything works fine on mobile devices, however, for some reason the computers that connect will not get through to the internet even when I try opening all the ports for Auth and pre auth users, heres the config file. I will attach the splash page as well, possibly didnt apply authuser properly.

    #
    # Nodogsplash Configuration File
    #

    # Parameter: GatewayInterface
    # Default: NONE
    #
    # GatewayInterface is not autodetected, has no default, and must be set here.
    # Set GatewayInterface to the interface on your router
    # that is to be managed by Nodogsplash.
    # Typically br-lan for the wired and wireless lan on OpenWrt White Russian.
    # May be br-lan on OpenWrt Kamikaze.
    #
    GatewayInterface br-lan

    # FirewallRuleSet: authenticated-users
    #
    # Control access for users after authentication.
    # These rules are inserted at the beginning of the
    # FORWARD chain of the router's filter table, and
    # apply to packets that have come in to the router
    # over the GatewayInterface from MAC addresses that
    # have authenticated with Nodogsplash, and that are
    # destined to be routed through the router. The rules are
    # considered in order, and the first rule that matches
    # a packet applies to it.
    # If there are any rules in this ruleset, an authenticated
    # packet that does not match any rule is rejected.
    # N.B.: This ruleset is completely independent of
    # the preauthenticated-users ruleset.
    #
    FirewallRuleSet authenticated-users {

    # You may want to open access to a machine on a local
    # subnet that is otherwise blocked (for example, to
    # serve a redirect page; see RedirectURL). If so,
    # allow that explicitly here, e.g:
    FirewallRule allow tcp port 80 to 192.168.254.254

    # Your router may have several interfaces, and you
    # probably want to keep them private from the GatewayInterface.
    # If so, you should block the entire subnets on those interfaces, e.g.:
    FirewallRule block to 192.168.0.0/16
    FirewallRule block to 10.0.0.0/8

    # Typical ports you will probably want to open up include
    # 53 udp and tcp for DNS,
    # 80 for http,
    # 443 for https,
    # 22 for ssh:
    FirewallRule allow tcp port 53
    FirewallRule allow udp port 53
    FirewallRule allow tcp port 80
    FirewallRule allow tcp port 443
    FirewallRule allow tcp port 22
    FirewallRule allow tcp port 1471
    FirewallRule allow tcp port 8080

    }
    # end FirewallRuleSet authenticated-users


    # FirewallRuleSet: preauthenticated-users
    #
    # Control access for users before authentication.
    # These rules are inserted in the PREROUTING chain
    # of the router's nat table, and in the
    # FORWARD chain of the router's filter table.
    # These rules apply to packets that have come in to the
    # router over the GatewayInterface from MAC addresses that
    # are not on the BlockedMACList or TrustedMACList,
    # are *not* authenticated with Nodogsplash. The rules are
    # considered in order, and the first rule that matches
    # a packet applies to it. A packet that does not match
    # any rule here is rejected.
    # N.B.: This ruleset is completely independent of
    # the authenticated-users and users-to-router rulesets.
    #
    FirewallRuleSet preauthenticated-users {
    # For preauthenticated users to resolve IP addresses in their initial
    # request not using the router itself as a DNS server,
    # you probably want to allow port 53 udp and tcp for DNS.
    FirewallRule allow tcp port 53
    FirewallRule allow udp port 53

    # For splash page content not hosted on the router, you
    # will want to allow port 80 tcp to the remote host here.
    # Doing so circumvents the usual capture and redirect of
    # any port 80 request to this remote host.
    # Note that the remote host's numerical IP address must be known
    # and used here.
    # FirewallRule allow tcp port 80 to 123.321.123.321
    }
    # end FirewallRuleSet preauthenticated-users


    # FirewallRuleSet: users-to-router
    #
    # Control access to the router itself from the GatewayInterface.
    # These rules are inserted at the beginning of the
    # INPUT chain of the router's filter table, and
    # apply to packets that have come in to the router
    # over the GatewayInterface from MAC addresses that
    # are not on the TrustedMACList, and are destined for
    # the router itself. The rules are
    # considered in order, and the first rule that matches
    # a packet applies to it.
    # If there are any rules in this ruleset, a
    # packet that does not match any rule is rejected.
    #
    FirewallRuleSet users-to-router {
    # Nodogsplash automatically allows tcp to GatewayPort,
    # at GatewayAddress, to serve the splash page.
    # However you may want to open up other ports, e.g.
    # 53 for DNS and 67 for DHCP if the router itself is
    # providing these services.
    FirewallRule allow udp port 53
    FirewallRule allow tcp port 53
    FirewallRule allow udp port 67
    FirewallRule allow udp port 1471
    FirewallRule allow udp port 8080
    # You may want to allow ssh, http, and https to the router
    # for administration from the GatewayInterface. If not,
    # comment these out.
    FirewallRule allow tcp port 22
    FirewallRule allow tcp port 80
    FirewallRule allow tcp port 443
    FirewallRule allow tcp port 8080
    FirewallRule allow tcp port 1471
    }
    # end FirewallRuleSet users-to-router

    # EmptyRuleSetPolicy directives
    # The FirewallRuleSets that NoDogSplash permits are:
    #
    # authenticated-users
    # preauthenticated-users
    # users-to-router
    # trusted-users
    # trusted-users-to-router
    #
    # For each of these, an EmptyRuleSetPolicy can be specified.
    # An EmptyRuleSet policy applies to a FirewallRuleSet if the
    # FirewallRuleSet is missing from this configuration file,
    # or if it exists but contains no FirewallRules.
    #
    # The possible values of an EmptyRuleSetPolicy are:
    # allow -- packets are accepted
    # block -- packets are rejected
    # passthrough -- packets are passed through to pre-existing firewall rules
    #
    # Default EmptyRuleSetPolicies are set as follows:
    # EmptyRuleSetPolicy authenticated-users passthrough
    # EmptyRuleSetPolicy preauthenticated-users block
    # EmptyRuleSetPolicy users-to-router block
    # EmptyRuleSetPolicy trusted-users allow
    # EmptyRuleSetPolicy trusted-users-to-router allow


    # Parameter: GatewayName
    # Default: NoDogSplash
    #
    # Set GatewayName to the name of your gateway. This value
    # will be available as variable $gatewayname in the splash page source
    # and in status output from ndsctl, but otherwise doesn't matter.
    # If none is supplied, the value "NoDogSplash" is used.
    #
    # GatewayName NoDogSplash

    # Parameter: GatewayAddress
    # Default: Discovered from GatewayInterface
    #
    # This should be autodetected on an OpenWRT system, but if not:
    # Set GatewayAddress to the IP address of the router on
    # the GatewayInterface. This is the address that the Nodogsplash
    # server listens on.
    #
    # GatewayAddress 192.168.1.1

    # Parameter: ExternalInterface
    # Default: Autodetected from /proc/net/route
    #
    # This should be autodetected on a OpenWRT system, but if not:
    # Set ExtrnalInterface to the 'external' interface on your router,
    # i.e. the one which provides the default route to the internet.
    # Typically vlan1 for OpenWRT.
    #
    # ExternalInterface vlan1

    # Parameter: RedirectURL
    # Default: none
    #
    # After authentication, normally a user is redirected
    # to their initially requested page.
    # If RedirectURL is set, the user is redirected to this URL instead.
    #
    # RedirectURL http://www.ilesansfil.org/

    # Parameter: GatewayPort
    # Default: 2050
    #
    # Nodogsplash's own http server uses GatewayAddress as its IP address.
    # The port it listens to at that IP can be set here; default is 2050.
    #
    GatewayPort 80

    # Parameter: MaxClients
    # Default: 20
    #
    # Set MaxClients to the maximum number of users allowed to
    # connect at any time. (Does not include users on the TrustedMACList,
    # who do not authenticate.)
    #
    # MaxClients 20

    # ClientIdleTimeout
    # Parameter: ClientIdleTimeout
    # Default: 10
    #
    # Set ClientIdleTimeout to the desired of number of minutes
    # of inactivity before a user is automatically 'deauthenticated'.
    #
    # ClientIdleTimeout 10

    # Parameter: ClientForceTimeout
    # Default: 360
    #
    # Set ClientForceTimeout to the desired number of minutes before
    # a user is automatically 'deauthenticated', whether active or not
    #
    # ClientForceTimeout 360

    # Parameter: AuthenticateImmediately
    # Default: no
    #
    # Set to yes (or true or 1), to immediately authenticate users
    # who make a http port 80 request on the GatewayInterface (that is,
    # do not serve a splash page, just redirect to the user's request,
    # or to RedirectURL if set).
    #
    # AuthenticateImmediately no

    # Parameter: MACMechanism
    # Default: block
    #
    # Either block or allow.
    # If 'block', MAC addresses on BlockedMACList are blocked from
    # authenticating, and all others are allowed.
    # If 'allow', MAC addresses on AllowedMACList are allowed to
    # authenticate, and all other (non-trusted) MAC's are blocked.
    #
    # MACMechanism block

    # Parameter: BlockedMACList
    # Default: none
    #
    # Comma-separated list of MAC addresses who will be completely blocked
    # from the GatewayInterface. Ignored if MACMechanism is allow.
    # N.B.: weak security, since MAC addresses are easy to spoof.
    #
    # BlockedMACList 00:00:DE:AD:BE:EF,00:00:C0:1D:F0:0D

    # Parameter: AllowedMACList
    # Default: none
    #
    # Comma-separated list of MAC addresses who will not be completely
    # blocked from the GatewayInterface. Ignored if MACMechanism is block.
    # N.B.: weak security, since MAC addresses are easy to spoof.
    #
    # AllowedMACList 00:00:12:34:56:78

    # Parameter: TrustedMACList
    # Default: none
    #
    # Comma-separated list of MAC addresses who are not subject to
    # authentication, and are not restricted by any FirewallRuleSet.
    # N.B.: weak security, since MAC addresses are easy to spoof.
    #
    # TrustedMACList 00:00:CA:FE:BA:BE, 00:00:C0:01:D0:0D


    # Parameter: PasswordAuthentication
    # Default: no
    # Set to yes (or true or 1), to require a password matching
    # the Password parameter to be supplied when authenticating.
    #
    #
    # PasswordAuthentication no

    # Parameter: Password
    # Default: none
    # Whitespace delimited string that is compared to user-supplied
    # password when authenticating.
    #
    #
    # Password nodog

    # Parameter: UsernameAuthentication
    # Default: no
    # Set to yes (or true or 1), to require a username matching
    # the Username parameter to be supplied when authenticating.
    #
    #
    # UsernameAuthentication no

    # Parameter: Username
    # Default: none
    # Whitespace delimited string that is compared to user-supplied
    # username when authenticating.
    #
    #
    # Username guest

    # Parameter: PasswordAttempts
    # Default: 5
    # Integer number of failed password/username entries before
    # a user is forced to reauthenticate.
    #
    #
    # PasswordAttempts 5

    # Parameter: TrafficControl
    # Default: no
    #
    # Set to yes (or true or 1), to enable traffic control in Nodogsplash.
    #
    # TrafficControl no

    # Parameter: DownloadLimit
    # Default: 0
    #
    # If TrafficControl is enabled, this sets the maximum download
    # speed to the GatewayInterface, in kilobits per second.
    # For example if you have an ADSL connection with 768 kbit
    # download speed, and you want to allow about half of that
    # bandwidth for the GatewayInterface, set this to 384.
    # A value of 0 means no download limiting is done.
    #
    # DownloadLimit 384

    # Parameter: UploadLimit
    # Default: 0
    #
    # If TrafficControl is enabled, this sets the maximum upload
    # speed from the GatewayInterface, in kilobits per second.
    # For example if you have an ADSL connection with 128 kbit
    # upload speed, and you want to allow about half of that
    # bandwidth for the GatewayInterface, set this to 64.
    # A value of 0 means no upload limiting is done.
    #
    # UploadLimit 64

    # Paramter: GatewayIPRange
    # Default: 0.0.0.0/0
    #
    # By setting this parameter, you can specify a range of IP addresses
    # on the GatewayInterface that will be responded to and managed by
    # Nodogsplash. Addresses outside this range do not have their packets
    # touched by Nodogsplash at all.
    # Defaults to 0.0.0.0/0, that is, all addresses.
    #
    # GatewayIPRange 0.0.0.0/0

    ---------------------------------------------------------------------------------------------------------------

    Below is the html

    ---------------------------------------------------------------------------------------------------------------\

    <!DOCTYPE html>
    <html>

    <head>
    <meta charset="UTF-8 "HTTP-EQUIV="Pragma" CONTENT="no-cache">

    <title>$gatewayname Entry</title>

    <style>
    * { margin: 0; padding: 0; }

    html {
    background: url($imagesdir/background.jpg) no-repeat center center fixed;
    -webkit-background-size: cover;
    -moz-background-size: cover;
    -o-background-size: cover;
    background-size: cover;
    }

    #page-wrap { width: 400px; margin: 50px auto; padding: 20px; background: white; -moz-box-shadow: 0 0 20px black; -webkit-box-shadow: 0 0 20px black; box-shadow: 0 0 20px black; }
    p { font: 15px/2 Georgia, Serif; margin: 0 0 30px 0; text-indent: 40px; }
    </style>
    </head>

    <body>


    <div id="contact-form">

    <form id="contact" method="post" action="">
    <fieldset>

    <h3>For Free Wifi enter the information below</h3>
    <label for="name">Name</label>
    <input type="text" name="name" placeholder="Full Name" title="Enter your name" class="required">

    <label for="email">E-mail</label>
    <input type="email" name="email" placeholder="yourname@domain.com" title="Enter your e-mail address" class="required email">

    <label for="phone">Phone</label>
    <input type="tel" name="phone" placeholder="ex. (555) 555-5555">

    <div style="overflow:auto;height:100px;">

    This agreement sets out the terms and conditions on which wireless internet access (the Service) is provided free of charge to you, a guest, vendor, board member or employee of The Financial Services Network (Network).

    Your access to the Service is completely at the discretion of the Network. Access to the Service may be blocked, suspended, or terminated at any time for any reason including, but not limited to, violation of this Agreement, actions that may lead to liability for the Network, disruption of access to other users or networks, and violation of applicable laws or regulations. The Network reserves the right to monitor and collect information while you are connected to the Service and that the collected information can be used at discretion of the the Network, including sharing the information with any law enforcement agencies, the Network partners and/or the Network vendors.

    The Network may revise this Agreement at any time. You must accept this Agreement each time you use the Service and it is your responsibility to review it for any changes each time.

    We reserve the right at all times to withdraw the Service, change the specifications or manner of use of the Service, to change access codes, usernames, passwords or other security information necessary to access the service.

    Any transmissions through this wireless router are the property of the Network and may be used for educational purposes. All packets captured by this access point may be used for presentation during our conferences. This is a really bad idea, by connecting to open networks you are broadcasting your transmissions openly to anyone who may want to steal them.

    IF YOU DO NOT AGREE WITH THESE TERMS, INCLUDING CHANGES THERETO, DO NOT ACCESS OR USE THE SERVICE.
    </div>


    <a href="$authtarget">
    <img src="$imagesdir/continue.png" width="280"height="114"border="0"
    alt="Click to enter" title="Click to enter">
    </a>


    </fieldset>

    </form>

    </div><!-- /end #contact-form -->

    <style type="text/css" style="display: none !important;">
    * {
    margin: 0;
    padding: 0;
    }
    body {
    overflow-x: hidden;
    }
    #demo-top-bar {
    text-align: left;
    background: #222;
    position: relative;
    zoom: 1;
    width: 100% !important;
    z-index: 6000;
    padding: 20px 0 20px;
    }
    #demo-bar-inside {
    width: 960px;
    margin: 0 auto;
    position: relative;
    }
    #demo-bar-buttons {
    padding-top: 10px;
    float: right;
    }
    #demo-bar-buttons a {
    font-size: 12px;
    margin-left: 20px;
    color: white;
    margin: 2px 0;
    text-decoration: none;
    font: 14px "Lucida Grande", Sans-Serif !important;
    }
    #demo-bar-buttons a:hover,
    #demo-bar-buttons a:focus {
    text-decoration: underline;
    }
    #demo-bar-badge {
    display: inline-block;
    width: 302px;
    padding: 0 !important;
    margin: 0 !important;
    background-color: transparent !important;
    }
    #demo-bar-badge a {
    display: block;
    width: 100%;
    height: 38px;
    border-radius: 0;
    bottom: auto;
    margin: 0;
    background: url(/images/examples-logo.png) no-repeat;
    background-size: 100%;
    overflow: hidden;
    text-indent: -9999px;
    }
    #demo-bar-badge:before, #demo-bar-badge:after {
    display: none !important;
    }

    form#contact fieldset {
    position: relative; width: 300px;
    margin: 50px auto;
    padding: 20px;
    background: white;
    -moz-box-shadow: 0 0 20px black;
    -webkit-box-shadow: 0 0 20px black;
    box-shadow: 0 0 20px black;
    }

    form#contact input[type=text], input[type=url],
    input[type=email], input[type=tel], textarea {
    margin: 3px 0 0 0;
    padding: 6px;
    width: 260px;
    font-family: arial, sans-serif;
    font-size: 12px;
    border: 1px solid #ccc;
    background: -webkit-gradient(linear, left top, left 15, from(#FFFFFF), color-stop(4%, #f4f4f4), to(#FFFFFF));
    background: -moz-linear-gradient(top, #FFFFFF, #f4f4f4 1px, #FFFFFF 15px);
    }

    form#contact textarea {
    width: 275px;
    height: 150px;
    }

    form#contact label {
    display: block;
    font-size: 13px;
    color: #666;
    margin-top: 10px;
    font-weight: bold;
    }

    form#contact label.error {
    width: 270px;
    margin: 3px 0 0 0;
    display: block;
    color: #cf0101;
    font-size: 11px;
    text-align: right;
    }

    form#contact .placeholder {
    color: #aaa;
    }

    form#contact .button {
    display: inline-block;
    margin: 15px 0 0 90px;
    padding: 5px 15px 5px 15px;
    background-color: #ff9e00;
    border: none;
    color: #fff;
    -moz-border-radius: 15px;
    -webkit-border-radius: 15px;
    border-radius: 15px;
    }

    form#contact .button:hover {
    background-color: #fc8500;
    cursor: pointer;
    }

    form#contact .button:active {
    margin-top: 16px;
    background-color: #f08004;
    cursor: pointer;
    }
    </style>
    </body>
    <script type="text/javascript">
    document.getElementById("submit").onclick = function () {
    location.href = "www.google.com";
    };
    </script>
    </html>

  8. So it looks like you guys made some updates since the last time a tried using this. I have a form submit button set to href="$authtarget" however it does not seem to redirect to the original website. If there a setting I am not enabling in the config file that authorizes the users? Also doesnt seem to work on iOs devices since they get the portal page once they connect.

  9. Have you verified an internet connection on the pineapple?

    What web browser are you using?

    If you have ssh access into the pineapple go ahead and ssh in and run the following commands

    opkg update
    opkg install nodogsplash kmod-sched
    

    YES! you are awesome, that did the trick. I have to say, this implementation of NDS is so much fun. I will share a template for the splash page that I had created.

  10. Hey guys,

    I have been working on a presentation over web security and awareness, and one of the things i was going to do was create a captive portal at the conference venue that people would just log into without clearing that it is safe or not. My issue is for some reason my pineapple refuses to install the dependencies from the web portal. I have tried checking for updates (im on 1.4) I have tried flashing, I have trie just about everything. Can someone possibly give me a hint as to what I could try? I'm running on windows, with winSCP and PuTTY. I would love some advice.

×
×
  • Create New...