Jump to content

Shark Jack Cable LED bug


ChristophR
 Share

Go to solution Solved by dark_pyrro,

Recommended Posts

The RGB LED of my new Shark Jack Cable is not working as expected.
1. In Arming Mode it is blinking yellow instead of blue, does that indicate anything?
2. By entering LED commands, they are adding up, which means after entering `LED B FAST` it is blinking blue and yellow, and after entering `LED R FAST` it is blinking blue, red and yellow alternating. `LED G SOLID` makes the LED green until the next blinking color is coming again.
In payloads it is the same effect, also for the default payload.

I already tried to fix it by re-flashing the firmware, but the problem remains.

Any idea how to solve this issue or did I just miss a feature?

Link to comment
Share on other sites

1.
Yellow indicates arming mode
https://docs.hak5.org/shark-jack/getting-started/default-settings#led-status-indications

2.
They do add on top of each other. Use LED OFF before issuing any new LED activity. If creating a payload with multiple LED commands, they can be observed if running ps when connected to the Shark using serial or ssh in attack mode/using a payload. However, for some reason it seems to be something strange with the LED OFF command for the Shark Jack Cable in attack mode. Not sure if it's a valid accusation, but it works on the battery based Shark. It doesn't even seem to be needed to issue LED OFF when switching LED modes on the battery based Shark. Haven't had time now to dig deeper into it though, but the LED command files aren't the same on the battery Shark and the cable Shark.

Link to comment
Share on other sites

Thanks for the quick feedback!

1.
on the instruction note from the package it says blinking blue is Arming Mode, maybe your link refers just to the Shark Jack without cable?

2.
unfortunately LED OFF is not doing anything on my Shark Jack Cable. The LED keeps blinking yellow, or whatever I stack on it.

Looking forward to your idea

Link to comment
Share on other sites

1.
The blinking blue is a "heritage" from the battery based Shark since most of the OS/system of the both devices are the same. The blinking blue doesn't really indicate arming mode, but charging. Since the cable variant doesn't have a battery, that LED indicator isn't valid. Perhaps a "typo" when the instruction card was printed, or the fact that there was a bit too much "copy/paste" from the battery based information card when the cable based Shark was released to market. I have both cards, I can compare them but I have to do some storage room digging to accomplish that.

2.
It's something related to the part of the LED command that looks for already spawned LED related processes but it fails to kill them (whereas the battery based Shark succeeds, they have a somewhat different approach in doing that; ps vs. pgrep).

Link to comment
Share on other sites

  • Solution

Simply replace the pgrep routine of the SJC in the end of the /usr/bin/LED file with the one from the battery Shark, it should do the job. It's the easiest/fastest workaround.
 

ps | grep LED | grep -v grep | awk '{print $1}' | grep -v $$ | xargs kill -9 &> /dev/null

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...