sgxgsx / BlueToolkit

BlueToolkit is an extensible Bluetooth Classic vulnerability testing framework that helps uncover new and old vulnerabilities in Bluetooth-enabled devices. Could be used in the vulnerability research, penetration testing and bluetooth hacking. We also collected and classified Bluetooth vulnerabilities in an "Awesome Bluetooth Security" way
MIT License
300 stars 27 forks source link

Requirement of github login #2

Closed Steso871 closed 2 months ago

Steso871 commented 2 months ago

Hello!

I tried to install on different devices (nethunter,Ubuntu vm and raspberry pi 4 with kali) but get same error message

"fatal: destination path '/usr/share/BlueToolkit/modules/tools/internalblue' already exists and is not an empty directory. cp: cannot stat '/usr/share/BlueToolkit/modules/tools/internalblue/examples/nexus5/CVE_2018_19860_Crash_on_Connect.py': No such file or directory cp: cannot stat '/usr/share/BlueToolkit/modules/tools/internalblue/examples/nexus5/CVE_2018_19860_Crash_on_Connect.py': No such file or directory cp: cannot stat '/usr/share/BlueToolkit/modules/tools/internalblue/examples/nexus5/CVE_2018_19860_Crash_on_Connect.py': No such file or directory Cloning into '/usr/share/BlueToolkit/modules/tools/blueborne/blueborne-CVE-2017-1000251'... Username for 'https://github.com':"

Thank you for sharing

sgxgsx commented 2 months ago

Hello

  1. Could you show me how are you trying to install the tool?
  2. For Ubuntu VM I recommend installing via vagrant

I see a small problem where another person took down their repository

sgxgsx commented 2 months ago

@Steso871 Could you try again and check whether you have the same error?

Steso871 commented 2 months ago

@Steso871 Could you try again and check whether you have the same error?

I type this in all my devices

sudo mkdir /usr/share/BlueToolkit sudo chown $USER:$USER /usr/share/BlueToolkit git clone https://github.com/sgxgsx/BlueToolkit /usr/share/BlueToolkit --recurse-submodules chmod +x /usr/share/BlueToolkit/install.sh /usr/share/BlueToolkit/install.sh

Steso871 commented 2 months ago

@Steso871 Could you try again and check whether you have the same error?

Yes will do it now so report as soon as possible

Steso871 commented 2 months ago

sadly i get same message Cloning into '/usr/share/BlueToolkit/modules/tools/blueexploits'... remote: Enumerating objects: 63, done. remote: Counting objects: 100% (63/63), done. remote: Compressing objects: 100% (48/48), done. remote: Total 63 (delta 13), reused 59 (delta 12), pack-reused Receiving objects: 100% (63/63), 8.71 MiB | 3.43 MiB/s, done. Resolving deltas: 100% (13/13), done. fatal: destination path '/usr/share/BlueToolkit/modules/tools/internalblue' already exists and is not an empty directory. cp: cannot stat '/usr/share/BlueToolkit/modules/tools/internalblue/examples/nexus5/CVE_2018_19860_Crash_on_Connect.py': No such file or directory cp: cannot stat '/usr/share/BlueToolkit/modules/tools/internalblue/examples/nexus5/CVE_2018_19860_Crash_on_Connect.py': No such file or directory cp: cannot stat '/usr/share/BlueToolkit/modules/tools/internalblue/examples/nexus5/CVE_2018_19860_Crash_on_Connect.py': No such file or directory Cloning into '/usr/share/BlueToolkit/modules/tools/blueborne/blueborne-CVE-2017-1000251'... Username for 'https://github.com':

Should i delete every folder and file and do a fresh install?

@sgxgsx

sgxgsx commented 2 months ago

@Steso871 Yes, please do a clean install, with fetching a new version of the repo.

You should have https://github.com/sgxgsx/blueborne-CVE-2017-1000251 in your install.sh file /usr/share/BlueToolkit/install.sh

Steso871 commented 2 months ago

@Steso871 Yes, please do a clean install, with fetching a new version of the repo.

You should have https://github.com/sgxgsx/blueborne-CVE-2017-1000251 in your install.sh file /usr/share/BlueToolkit/install.sh

Now it installed without previous error but now I got this error on my nethunter device

ERROR: Could not find a version that satisfies the requirement venv (from versions: none) ERROR: No matching distribution found for venv

Haven't installed it on rpi4 kali yet

sgxgsx commented 2 months ago

Which python3 version are you using? I guess my mistake was installing venv only for python3.11 and you might have another version


sudo apt-get install python3.11-venv

Without a clean install try the following:


sudo apt-get install python3-venv

And run the installation script again /usr/share/BlueToolkit/install.sh

Steso871 commented 2 months ago

Which python3 version are you using? I guess my mistake was installing venv only for python3.11 and you might have another version


sudo apt-get install python3.11-venv

Without a clean install try the following:


sudo apt-get install python3-venv

And run the installation script again /usr/share/BlueToolkit/install.sh

  • Do you have this problem while installing with vagrant?

"python --version Python 3.11.9"

When I type both python command it says it's already installed. I have exactly the same error on my rpi4

How do I install with vagrant?

sgxgsx commented 2 months ago

Which python3 version are you using? I guess my mistake was installing venv only for python3.11 and you might have another version


sudo apt-get install python3.11-venv

Without a clean install try the following:


sudo apt-get install python3-venv

And run the installation script again /usr/share/BlueToolkit/install.sh

  • Do you have this problem while installing with vagrant?

"python --version Python 3.11.9"

When I type both python command it says it's already installed. I have exactly the same error on my rpi4

How do I install with vagrant?

Does the following command work?


source /usr/share/BlueToolkit/.venv/bin/activate

If yes, then everything should be okay?

If no try the following command in a temporary directory


python3 -m venv .venvtodelete
python3.10 -m venv .anothervenv

If it works, then venv is available, and should work too.

In case of the vagrant, it will install the tool in an ubuntu VM in Virtualbox*. I am not sure whether it is what you want.

Steso871 commented 2 months ago

Which python3 version are you using? I guess my mistake was installing venv only for python3.11 and you might have another version


sudo apt-get install python3.11-venv

Without a clean install try the following:


sudo apt-get install python3-venv

And run the installation script again /usr/share/BlueToolkit/install.sh

  • Do you have this problem while installing with vagrant?

"python --version Python 3.11.9" When I type both python command it says it's already installed. I have exactly the same error on my rpi4 How do I install with vagrant?

Does the following command work?


source /usr/share/BlueToolkit/.venv/bin/activate

If yes, then everything should be okay?

If no try the following command in a temporary directory


python3 -m venv .venvtodelete
python3.10 -m venv .anothervenv

If it works, then venv is available, and should work too.

In case of the vagrant, it will install the tool in an ubuntu VM in Virtualbox*. I am not sure whether it is what you want.

"root@kali:/# source /usr/share/BlueToolkit/.venv/bin/activate

(.venv)root@kali:/#"

This means it works right?

sgxgsx commented 2 months ago

@Steso871 In theory yes. Double check that you have vevn for python3.10

python3.10 -m venv .anothervenv
Steso871 commented 2 months ago

@Steso871 In theory yes. Double check that you have vevn for python3.10

python3.10 -m venv .anothervenv

It's working now! Going to check examples and test it out now.

Thank you so much for your help and time :)

I ran "python3.10 -m venv .anothervenv" And got

"root@kali:/ python3.10 -m venv .anothervenv

root@kali:/# "

sgxgsx commented 2 months ago

Great! @Steso871 Now I want to ask you:

sgxgsx commented 2 months ago

Closing as resolved