Dr_GrEeN's Bluesnarfer & Bluebugger Guides From old fourm.

Quote:

---

Originally Posted by drgr33n

Hey guys,

Just to let you know I'm still about lurking in the background :D. Hope you guys are all well ?

---

Hello BT users,

Let me start with.. Great tut drgr33n!
And i am fresh to linux.

I have 2 problems with Bluetooth

1. bluesnarfer does not start up
I follow every command to start bluesnarfer but when i type bluesnarfer it will show me:
" bash: bluesnarfer: command not found "
I have installed it with synaptic.

Ok now 2. bluebugger is bugging me!
When i type:
" bluebugger -m f4llcon -c 3 -a FF:FF:FF:FF:FF:FF info phonebook +GMI "
i get:

bluebugger 0.1 ( MaJoMu | back to basics. )
-----------------------------------------

Target Device: 'FF:FF:FF:FF:FF:FF'
Target Name: 'K800i'

Mobile Identification
---------------------

+GMI: ''

...done

Am i blind or is it not showing up my phonebook, info and +GMI?

It may be the channel, but i tried 17, 1, 2, 3 and i stopped trying.

I googled for the bluesnarfer problem and searched the bt forums, but with no luck..

Thanks,

F4LLCON

Just wondering if anyone has figured out a way around the pairing code yet?

Will this perhaps help ? It's a python script, you can just paste it in Kate and save as bluetooth-pin-agent.py.

Code:

---

#!/usr/bin/python
# /usr/bin/bluetooth-pin-agent

import gobject

import sys
import dbus
import dbus.service
import dbus.mainloop.glib

class Rejected(dbus.DBusException):
  _dbus_error_name = "org.bluez.Error.Rejected"

class Agent(dbus.service.Object):
  exit_on_release = True

  def set_exit_on_release(self, exit_on_release):
      self.exit_on_release = exit_on_release

  @dbus.service.method("org.bluez.Agent",
              in_signature="", out_signature="")
  def Release(self):
      print "Release"
      if self.exit_on_release:
        mainloop.quit()

  @dbus.service.method("org.bluez.Agent",
              in_signature="os", out_signature="")
  def Authorize(self, device, uuid):
      print "Authorize (%s, %s)" % (device, uuid)

  @dbus.service.method("org.bluez.Agent",
              in_signature="o", out_signature="s")
  def RequestPinCode(self, device):
      print "RequestPinCode (%s)" % (device)
      return "ENTER_YOUR_FIXED_PIN_HERE"

  @dbus.service.method("org.bluez.Agent",
              in_signature="o", out_signature="u")
  def RequestPasskey(self, device):
      print "RequestPasskey (%s)" % (device)
      passkey = raw_input("Enter passkey: ")
      return dbus.UInt32(passkey)

  @dbus.service.method("org.bluez.Agent",
              in_signature="ou", out_signature="")
  def DisplayPasskey(self, device, passkey):
      print "DisplayPasskey (%s, %d)" % (device, passkey)

  @dbus.service.method("org.bluez.Agent",
              in_signature="ou", out_signature="")
  def RequestConfirmation(self, device, passkey):
      print "RequestConfirmation (%s, %d)" % (device, passkey)
      confirm = raw_input("Confirm passkey (yes/no): ")
      if (confirm == "yes"):
        return
      raise Rejected("Passkey doesn't match")

  @dbus.service.method("org.bluez.Agent",
              in_signature="s", out_signature="")
  def ConfirmModeChange(self, mode):
      print "ConfirmModeChange (%s)" % (mode)

  @dbus.service.method("org.bluez.Agent",
              in_signature="", out_signature="")
  def Cancel(self):
      print "Cancel"

def create_device_reply(device):
  print "New device (%s)" % (device)
  mainloop.quit()

def create_device_error(error):
  print "Creating device failed: %s" % (error)
  mainloop.quit()

if __name__ == '__main__':
  dbus.mainloop.glib.DBusGMainLoop(set_as_default=True)

  bus = dbus.SystemBus()
  manager = dbus.Interface(bus.get_object("org.bluez", "/"),
                    "org.bluez.Manager")

  if len(sys.argv) > 1:
      path = manager.FindAdapter(sys.argv[1])
  else:
      path = manager.DefaultAdapter()

  adapter = dbus.Interface(bus.get_object("org.bluez", path),
                    "org.bluez.Adapter")

  path = "/test/agent"
  agent = Agent(bus, path)

  mainloop = gobject.MainLoop()

  if len(sys.argv) > 2:
      if len(sys.argv) > 3:
        device = adapter.FindDevice(sys.argv[2])
        adapter.RemoveDevice(device)

      agent.set_exit_on_release(False)
      adapter.CreatePairedDevice(sys.argv[2], path, "DisplayYesNo",
              reply_handler=create_device_reply,
              error_handler=create_device_error)
  else:
      adapter.RegisterAgent(path, "DisplayYesNo")
      print "Agent registered"

  mainloop.run()

  adapter.UnregisterAgent(path)
  print "Agent unregistered"

---

And be sure to place it in /usr/bin/ and make it executable

I love it when people drag up these posts from 2008 :D I think what 2901119 means is there a better way to sniff the link keys between two devices. Back in 2008 a few of us modded a Bluetooth dongle to sniff bluetooth traffic. Unfortunately because of the channel hopping that bluetooth connections use one of the biggest challenges was to calculate the hopping sequence. Work was done but never got off the ground and peops lost interest until last year. I was thinking about resurrecting this project as what stood then pretty much is the same now. Then I was pointed in the direction of Ubertooth :d

http://ubertooth.sourceforge.net/

It's all a bit quiet on that scene atm. I think they more people to jump on board to really give that project a kick up the backside lol but I fear people are just not willing to roll there own hardware ? I for one am very interested and might be looking at ubertooth for a little summer project :D. Maybe link key cracking on GPGPU's ? I did read somewhere that link key cracking doesn't scale well on GPGPU's but I think that's a load of bull&*%^ :D I may be wrong but there's where I stand on that for now.

I think bluetooth has gone TOO many years being untouched down to people just not being interested. And thats a shame because most people have a bluetooth enabled device on them 24/7 so this could be very interesting stuff ;)

I agree, too little focus on an interesting side of information.

But I think that 2901119 was meaning is what cgelici put up; a means to enable
pairing with a bluetooth device within backtrack.
As it stands, what is available on BT4 is not best suited for that and additional
scripts are needed.

Ubertooth does look promising and looking forward to where that leads in the near future.

Lack of this script is not a Back|Track issue, it's a bluez issue, they stopped providing it. Don't ask me why... I found this script on ronnieflip's www.blindsecurity.org

Or if your using the GUI just use gnomes bluetooth app it works on kde and gnome.

Code:

---

apt-get update;apt-get install gnome-bluetooth

---

hey guys, thanks for the replies. Sorry I was so vague, but I asked it that way because it was more of a general question. I wasn't looking for one certain way around it, but more or less any way around it. All of your replies were actually helpful/relevant.

@drgr33n excellent mention of ubertooth, I've actually watched a couple of videos on it, way cool device. I'm gonna also give gnome-bluetooth a go too. Good lookin out.

@cgelici... thanks for sharing the script, I've used simple-agent before but I'm gonna give this a try and see how it differs.

As you guys have said "too little focus on an interesting side of information." Thats soo true, and partially why I drug up such an old thread. I'm glad some people are still interested though.