Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[idea] allow configuration of Bluetooth device name in pm3 wrapper script #2637

Open
Laikulo opened this issue Nov 15, 2024 · 3 comments
Open
Labels
enhancement New feature or request Request

Comments

@Laikulo
Copy link

Laikulo commented Nov 15, 2024

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I'd like to be able to configure the device name that pm3 searches for, to allow for use with a device that uses a different name (set via the appropriate AT command)

Describe the solution you'd like
A clear and concise description of what you want to happen.

A command line arg to pm3 at a minimum, an envvar would also be nice. Possibly also from a per-user config.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Modifying the pm3 script in repo, and stash/stash poping around pulls.

Additional context
Add any other context or screenshots about the feature request here.

@Laikulo Laikulo added enhancement New feature or request Request labels Nov 15, 2024
@iceman1001
Copy link
Collaborator

The pm3 script tries to automatically detect the different available devices connected to the computer across different OS.
Running ./pm3 --list to see which device it finds. If your bluetooth device name for is not detected then the device most likely have a different com port enumeration.

You can try and debug it

@Laikulo
Copy link
Author

Laikulo commented Nov 15, 2024

Ah, I was meaning the values that are hard coded here:

https://github.com/RfidResearchGroup/proxmark3/blob/master/pm3#L114

I just modified them in my local copy to the name that I set, and all works as expected, it's just a bit hacky...

@iceman1001
Copy link
Collaborator

I see.
Modifying the script to handle different names, you should be able to do it. I am looking forward to see your fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Request
Projects
None yet
Development

No branches or pull requests

2 participants