Marcin Kozlowski

You have \x00 somewhere in your payload. Payload would stop on first occurence, that's why it is checked by this assertion. Try to eliminate \x00 in your payload.

Check if you control R4 via REMOTE_NAME in btu_hci_msg_ready. I think you are close, but your payload might need adjustment, given that your mobile is vulnerable.

Stack isn't leaked via SDP. That's why assertion fails. Could be that your device is not vulnerable. Try to run leak.py to check it.

Yes, it is complete, it is mostly Armis code. My work was to find the right offsets for my mobile (Samsung S3 Neo on LinageOS 14.1). You need to adjust...

Hi @MarkLee131 These are currently all the rules in place (1,700+) They cover Code and Infrastructure (IaC) ``` Loading plugin: git Loading plugin: email Loading plugin: git Loading plugin: trufflehog3...

Hi @noraj Thanks for you message and sorry for a delayed reply. Previously, only collaborators could edit it (submitting PR or added by me). I opened the wiki for public...

@noraj Great. Yes, you are more than welcome.

Hi @ok-karthik Thanks for your issue. I think you are missing the `CODE_DIR` env setup step and cd'ing into it. If you exec into Container, pass the env var (`-e`)...

@ok-karthik I will add a check to make sure code is a git repo clone and CODE_DIR env var is set, so it can warn about it. Thanks for your...

Thank you for your feedback and ideas. I don't have MacOS device. However, based on your feedback I made some changes Ideally SMC should be run on Linux (Cloud Kubernetes,...