Search This Blog

Spoofing Bluetooth Device Information

Step1: $hciconfig
Like ifconfig and iwconfig for bluetooth we have hciconfig that enumerate bluetooth interfaces in an system with a little info about that card like MAC,MTU and interface name.

hciconfig

Step2:$hciconfig -a hci0
So now we known we have a bluetooth interface card hci0.It may be anyone hci0,hci1 etc. Now as you can see below in the output that this bluetooth device is using OS name as its name own name. We will change this info so that some person might not enumerate any info about our bluetooth device. Class is a 24 bit or 6 hex number based identity for bluetooth devices. Class entity defines that bluetooth device is of which hardware class i.e 1)0x78020c is class of Phone/Smart phone,2)0x6e0100 is class of computer etc.Now will try to change this default class and name of our bluetooth device.

hciconfig -a hci0

Step3:$hciconfig -a hci0 features
This command will tell what features our card support.

hciconfig -a hci0 features

Step4: $hciconfig -a hci0 name 'aLt' class 0x78020c
Now we will change default class and name,and check the results.

Bluetooth Hacking

So now if anyone try to scan our bluetooth then he will think that its a smartphone device because as you can see in above output that our Device class is Smartphone now.

Get link

Facebook

Twitter

Pinterest

Email

Other Apps

Get link

Facebook

Twitter

Pinterest

Email

Other Apps

Comments

Post a Comment

Popular posts from this blog

Steps
1:download the page.
2:open fc4.js in your favourite editor and add following lines in it or just replace it with vode given below.
3:then open the download html file in browser and fill the form with your email and a garbage value string.
4:thats it? it will show you the real security string??
yeah but ...theirs another challenge waiting for you ... :D

I recently started working on widows 10 Apps( Apps not Applications) security. Before diving deep in hacking terms lets try to understand what's new in Windows 10 UWP( Universal Platform) as compared to old Apps. Lets begin with how apps actually work on windows 10(desktop/tablet). Now windows 10 comes with a container only for running apps inside the isolated environment. By default, /APPCONTAINER(Linker Flag) is off. This option modifies an executable to indicate whether the app must be run in the appcontainer process-isolation environment. Specify /APPCONTAINER for an app that must run in the appcontainer environment—for example, a Windows Store app. (The option is set automatically in Visual Studio when you create a Windows Store app from a template.) For a desktop app, specify /APPCONTAINER:NO or just omit the option. The /APPCONTAINER option was introduced in Windows 8.
Now there is no registry entry concept for these app in the System HIVE rather they install they own hiv…