dark_pyrro

Be more specific and detailed Select one (1) module and describe the steps you do and where/when the error occurs. If it happens "almost all of the time on every module", then I would probably look somewhere else other than the modules themselves. But... more info needed to be able to try to assist. Never had such issues, at least not for all modules and not all of the time.

You won't see any 5 GHz devices when using the Mark IV. Haven't seen any info over the years about anyone getting 5 GHz working on that device. What adapter are you using? How can you tell from a video that all of the clients are found when there's no way to verify from watching a video how many clients that actually is around the Nano at the point when the video was recorded?

Not sure how you plan to intercept keystrokes using a hardware device if it's not in line with any keyboard.

To get the key there without void any warranty might be tricky (as said). It's for sure easier if able to access the Crab using hardware serial or adding ssh support, but those are tweaks that will void warranty. The only alternative that I can think of would be to create an autoexec.txt file on th eMicro SD card that is scripted to transfer any key file to the correct location of the Crab.

Did you manage to get the public key to the Crab in the correct location? That could be tricky when it comes to the Crab since it's rather "closed" out of the box.

That makes things "a bit" easier for sure if trying to use a hardware keylogger. It's how the Key Croc is designed to work. There are generally no guarantees that problems will always be avoided. Things can always happen depending on the circumstances.

I'm confused. Lots of hacking experience, but don't know where to start when it comes to cybersecurity and pentesting. This needs some further clarification. What exactly do you need to know?

I guess you have to ask official support about that. The FCC test report says AC 100-240V at least and I don't think those reports "cuts corners" when it comes to specs. But, getting an official answer is probably the safest way.

Could be, or not. Difficult to say. The MK7AC ones are designed for 5 GHz for sure, but there's no guarantee the 2.4 GHz ones are even if it would be possible. I don't have the MK7AC myself, I use another 5 GHz adapter with the Mark VII, so I don't know in which way the antennas might differ physically. If there aren't any distinct ways to tell which one is for the Mark VII or the MK7AC, then perhaps discretely "tag" some of them, or put some colored tape (or such) on them. The antennas on the 5 GHz adapter I use are very easy to identify because of shape/design.

You could try to get in contact with official support and see if it's possible to get the missing antenna. There are no guarantees, but you could always ask them.

The original ones should be 5 dBi omni directional 50 Ohm RP-SMA and designed for 2.4 GHz

What happens if you try to wget the file when connected to the Pineapple using ssh?

Try asking on Discord. There's probably an increased chance that someone might be able to reply to that on there.

Can't make any sense when reading this. So, the factory reset/recovery worked after all? What CLI? The recovery page is web based. What do you do when trying to enter "reset mode" (which I assume is the recovery page after booting with the button pressed and getting a red solid LED)

Perhaps try asking on the GSG Discord instead

Can you connect to it from a computer using the USB-C port of the Pineapple?

I would probably submit a support ticket

Why create a new thread when it relates to the issue discussed...?

Is the setup just looping (i.e. if you try it once again)? Did you try to factory reset the Pineapple and start over?

From where are you trying to clone the repo? From the Bunny? If this is from the Bunny (I assume it is judging from the errors posted this far), is your Bunny connected to the internet? In what way?

I guess you have to investigate what capabilities your phone has. Obviously the Bunny is capable of doing this (since my tests are successful), and if it's not working, it's logic to assume that any limitations are on the "phone side". I've successfully recreated this on 3 different Android devices now.

I can't recreate that scenario. If adding adb shell dumpsys -l to the payload (and write the output to a file on the Bunny), it works.

let it sleep for a while after the adb connect, you need to let it have enough time to connect before running any adb commands