dustbyter

raz0r - thanks for the detailed information, I'll update it and post in the near future. Seb - having the bartender auto update the version would be a nice add-on to the module.

raz0r, can you provide a bit more details?

The get infusion has been updated and submitted. V1.2 is under review. The infusion was almost completely rewritten with respect as to how it stores the local database of information. Excited to solve most issues of the infusion! The Get infusion profiles the karma'ed clients through their browser's plugin. A hidden iframe is injected into the redirect.php file which provides the capability to check what the supported plugins of the browser are through client-side code. This information is then made available through the infusion large tile interface. The interface additionally allows for comments to be stored for each client by the pineapple admin.

The infusion has been updated and fixed since this issue. Additionally, there is a new update submitted v1.2.

i submitted a suggestion for this as well. To have the ability to filter out certain devices probes if you know your not interested in them. You don't want to not karma them, but instead your not interested to see their probes.

Have you checked out Box? Their whole model is around collaboration and cloud storage.

Think i found out part of the issue at least. The connected devices are getting an IP from the router that is connected to the MKV over ethernet. I would expect that the IP address is assigned through the MKV. I can always disable DHCP on the router one hop away from the MKV which is assigning addresses, but would be nice to fix this on pineapple.

Mine is the latest and greatest version. I have not yet rebooted the MKV. Does it require it? EDIT: Still the same behavior. My configuration is: Firmware: 1.3.0 Karma: 1.9 (at least, based on the handler.php file) <?php ######################### # User Variables # # Please edit these # ######################### $name = 'Karma'; #Name of tile $updatable = 'false'; #Should this tile auto-refresh $version = '1.9'; I am explicitly searching for networks that don't exist through my device to get Karma to associate with them and then checking the intelligence report and dhcp.leases. They are both empty.

Karma seems to be acting up. In the log we can see that a device sucessfully associated, but in the intelligence tab, the information such as IP address in not displayed. Karma log contents Apr 23 12:50:04 KARMA: Successful association of 78:ca:39:b1:83:5F Apr 23 12:50:04 KARMA: Checking SSID for start of association, pass through Luxor Apr 23 12:50:01 KARMA: Probe Request from 78:ca:39:b1:83:5F for SSID 'Luxor' Apr 23 12:50:01 KARMA: Checking SSID for start of association, pass through Luxor Data on intelligence tab Karma Intelligence Report HW Address IP Address hostname SSID Additionally, i checked the /tmp/dhcp.leases file and it is blank. I expected to see something there. Is anyone else having this issue?

This would be a nice addition to have to the system. Additionally, it would be nice to have the ability to post an HTTP request with the information as well, incase someone wanted to store this data remotely and perform some analytics on the data.

This is pretty neat idea. It can really be performed with any OpenWRT device that can run kismet, karma is not really required unless your looking to inspect the data. "Drones" can be set up with a cron job that posts the information logged from Kismet to some back-end server from which the analysis can be performed. Depending on what your looking to analyze, then the specific analysis can be performed.

Also check /dev/sd* to see what it has been mounted as. In some cases, my USB on MK4 was mounted as sdb or sdc and i had to adjust it in fstab.

Karma does write to a log. check the /tmp directory. There should be one log file for each interface.

Sweet! Glad to see that 1.3.0 is out so soon although for beta testing!

Well done Seb! The pineapple seems more stable then ever so far!

Sweet WM! I'll be excited to check it out! I really couldn't get the other version to do anything :)

Hi all, I have upgraded to 1.1.0 and noticed that karma is not working. Anyone else having an issue with it?

The problem is that many consumers, won't install this update. They are not aware of what firmware is. Thus they will continue to be at risk :(

Hmm, wonder if the structure of an infusion has changed with newer versions of the firmware. I'll check it out.

Hi pax0r, can you provide some more details? I have not looked at the infusion in some time. If you having issues, explain what you did and I'll look into fixing it again! sorry haven't been around as much in recent months. dustbyter

Updated infusion has been submitted. All CRLF characters have been replaced with just LF. The infusion should be available once the admins approve it. Thanks!

:( interesting... I'll work on removing those characters and reupload the infusion in the next few days. Can someone with an MKIV and MKV describe the behavior they are seeing in the infusion? I want to assess the impact of the ^M character shown in some editors.

The ^M character you are seeing is because the end line characters between windows and unix machines is different. This should not be impacting the infusion from working properly.

Hi, As I don't have a MKV i have not yet updated the infusion. I will be updating it when I get one in. Regarding the update to sdcard, you can update the references to USB accordingly. Provide a list of the files that you are refering to with the ^M Lastly, can a mod, move this over to the actual get support thread and close this thread here? Thanks!

I would imagine that the SSLStrip infusion may get some of the information you are looking for. But let me be clear that on this forum we do not condone this type of activities. If you are to do this type of assessment, ensure that you have express written consent from the network owner and that the network users are informed that their data may be sniffed.