welcome
uh we are so pleased to have you here at
this session
it's going to be very interesting uh
discussion about bluetooth
but before we get to that before we get
to our speaker i wanted to give you
some very important announcements please
do not forget to visit
the expo hall we have sponsors with
contests
and swag community organizations and you
uh things that you really want to find
out about including
red team villages with red team talks
going on
and there are raffles happening
throughout the event but the only way
you can win
a raffle is to stop by so you definitely
want to do that
also i would like to thank our fabulous
sponsors
seen here we appreciate very much our
sponsorship with our sponsors
it allows us to put on this fabulous
presentation
and allow a lot of people to attend the
event
um i will be collecting questions from
the stage
area and then um so as you
think of questions go ahead type type
type away
and then at the end of the presentation
we will go through
all of the questions or as many as we
can as many as we have time for
so please join me in welcoming ria
baldivia
who is a tinkerer at heart and enjoys
merging art with technology
she pursues her curiosity in both
domains of history
and technology and contributions to
various discourses
under these topics she will share her
love for
bluetooth low energy or ble in today's
presentation in hopes it will inspire
you to tinker so take it away rehab
thank you so much dave hi everyone um
glad to see you and i'm pretty excited
about today
first and foremost um i would like to
thank the team and volunteers and the
entire staff of the diana
initiative for hosting this and
persevering despite
2020 um i also i'm
very happy that they did that it's a
testament to the commitment
of inclusivity and just you know making
sure we move forward
and dave thank you again for working
with me throughout this entire week
uh burgundy also just helping things out
and making sure we were all on board
um so today um i'm real baldivia i'm
clues what clues can i share with you
um to help you on your journey um
playing with bluetooth low energy and
just these little devices that you
pretty much buy at the store
um and so let's go ahead and start this
fun
so i mean bluetooth is everywhere you
have your mobile device
you enable bluetooth there you have your
smart refrigerator
your smart bulbs and then you have a
network in your
own home that you're building unknown
pretty much by all these things and you
coordinate and automate
what turns on which turns off a lot
color brightness and all that wonderful
stuff
and then you have bluetooth um that's
enabled even in vehicles and
other items and pretty soon the
bluetooth special interest group is
going to have um audio low energy and
i'm pretty excited about that
because i love playing with music
programming that was my introduction to
stem with music how to program music so
um here we are today playing with blue z
and they are going and we're going to
basically talk about you know
what exactly you can do at home open
source items
hardware that you can get on the cheap
and um actually
you may not need to buy a hardware item
if you have an android
mobile so let's go ahead to our next
slide
um i'm a historian as i mentioned uh do
history and technology
and i i like merging both worlds and um
when i
talked about you know my interest in
bluetooth
with friends they were like well where
did that name come from
and i was like i don't know so let's go
ahead and look it up
and lo and behold the engineer that was
responsible for bluetooth
um is a history buff as well and he was
inspired by a book about vikings
and um the logo actually is a bind room
so it's named after this viking king
during the 10th century
um king harold blochland son
um united scandinavia jim carter came up
with a name in 1997. he was inspired by
a book who's reading about the viking
vikings um basically the symbol
represents
the king's name um also known as
bluetooth
initials and um he also was inspired the
engineer
was inspired by franz benson's longship
book it focused on danish warriors and
who had a
thing for adventure and then there was a
vikings book that exposed them to
the runic stone and what i find really
fascinating is not only
is the history buff but he
was inspired by the concept of pink
forms
um when he unified scandinavia so he saw
the product that he was building as
something that would unify
you know multiple devices and things
into like some sort of mesh network
and so that's how bluetooth came about
with um
with um with this product and i thought
that was really cool and
i wanted to make sure that you um i
shared it with you if this is the only
thing that you walk away with
after this talk that's perfectly fine
but yeah
bluetooth is named after 10th century
who is responsible for uniting
scandinavia
all right so let's start high level here
we have bluetooth
wireless technology specification is
developed
management published by the bluetooth
special
interest group um they also do that with
blue z um within bluetooth you have the
low energy on the 2.4 gigahertz
bubble and then it used to be called
blue smooth
um bluetooth smart
and in contrast to um classic bluetooth
um it's designed to provide
significantly lower power
consumption so these allows apps to
communicate with ple devices
you have peripheries that you can engage
with connect with
interact with so um that's
pretty exciting and these things are
just getting much more sophisticated and
fun and
um the more you know about them the more
fun you can have with them even at home
if you just want to research what
exactly
do you have at home all right
so after bluetooth low energy let's get
down to
the linux bluetooth protocol stack which
we call blue z
um it's an open source project under the
general public
license so it was developed in 2001
and released in 2001 and then in 2004 it
was handed over to marcel coltman
and then just like bluetooth the
bluetooth special interest group
they um gained maintenance
responsibilities maintainership um in
2005.
so the components when you play with
bluesy or bluetooth little energy such
as the
unique identifiers and all of that stuff
the attributes the characteristics
those still play um with the
specifications that were published by
the bluetooth special interest group
and here you have no tux you can't
forget him
for playing with linux gotta put a heart
there
all right some background information on
the features um blue z
provides support for the four bluetooth
layers and protocols available on
woozy.org
one of the things that i want to
highlight here is that it can support
multiple bluetooth devices let's say you
have
a raspberry pi or a single um processing
board
that has bluetooth 4.1 in it already
if you get a bluetooth usb or a two or
three
and use one of the tools such as the um
the hci
tool you can actually still stand up
all those bluetooth devices they'll have
their um
bluetooth device address as well and
then they can actually start scanning
for first so i think that's really cool
um now we're just going to play for this
presentation we're just going to play
with
one bluetooth device that's going to
serve as um
the main um broadcaster then then we'll
scan and look for properties
um uzi consists of many separate modules
um we have
things that deal with the um control
interface we have things that do a
protocol decoding and analysis tool
and the three main items that we're
actually going to play with are
introduced with but we're going to play
with two main items
are um basically
control bluetooth ctl um
hci config hdi tool and then there is
the gen generic attribute um tool
called gap tool
so platforms and distributions um bluesy
kernel modules
things that basically um you have
libraries utilities
anything that that you can get your
hands on i mean i'm using the raspberry
pi for this presentation
um distributions anything that's debian
dates i mean for linux
um one of the things that didn't show up
when i
took this from bluesy.org is that it
also is
utilized you can use it in cali linux i
had some issues
when i was playing with my espion buster
version offered um for this and i was
like well let me try
my kali linux on my pie and see if that
can work and it turned out
okay it was great because i needed to
use a wire shard anyways a packet
analyzer
and we're gonna go through that too so
here we go we have commands commands
that we're going to utilize or get
exposed to
bluetooth control command line interface
to blue
you have the hdi device configuration
utility
where you will tell the bluetooth device
that you're on to stand up or to shut
down
and then you will utilize the hdi tool
for a low energy scan
um basically once you scan up your
bluetooth device
clip hdi tools i want you to scan for
all the peripherals out there
that are utilizing low energy and then
i added gap tool here interesting about
gap tools the most
recent um up to date
version of um blue z
doesn't download or install gap tool by
default you have to do that um
individually modularly and um that's
available online as well
but not too bad either way you can still
utilize that tool
all right so with applications um before
we get
into these bluesy tools i think it's
important to understand
why these tool sets aren't what they are
um it's because of these characteristics
and the layers that are involved in low
energy so
with the generic access profile you have
the application layer and then you have
a host layer
and then within that you have the
generic profile
which dictates how devices interact with
each other i mean you have the world
you're the broadcaster you have the
observer you have the central you have
the peripheral
and then you go ahead and have a generic
action profile
which is called gap that establishes how
to exchange all profile and user data
over a low energy connection um and then
you have the
um security manager protocol and the
attribute
protocol um here the actual protocol is
very special that's where the data
gets exchanged and um the logical link
control and adaption protocol the l2 cap
layer is um the routing mechanism
for the action protocol and security
management so when you do some
analysis on packets one of the things
you need to do is make sure that you're
looking
at the packets that contain the
attribute protocol
um and then you have a host controller
interface which basically um
you know it's the interface between the
host and controller and then you have
the link layer and the physical layer
the physical layer um it contains the
analog communication
this thing is on 2.4 and then um
you have the link layer you have to
define the device sending advertising
packets
a device that initiates a connection and
manages it later
and then a periphery device and
advertiser um so basically
that's responsible they're responsible
for the rules there
um so now that we
of what understand the low energy
protocol stack is
let's go ahead and play it with the um h
the host control interface um
tool here um http so we're going to deal
with hci
and general attributes so you go ahead
and let's say you have your raspberry pi
and it has bluetooth in it the raspberry
pi regular pipe for those
those versions come with the um um
bluetooth 4.1
if you have anything under like
frederick ii you may have to get a
bluetooth
usb so let's go ahead and do studio hdi
config
number and then your command so in this
case i have sudo hdi config
hdi 0 my first device i want you to
basically stand up um run that command
go ahead and enter http again and then
your output is the device saying
yeah this is my type of um this is what
i am
this is my address um and i'm up and
running
so what do you need to do next
so in addition to the up command you can
tell um them to basically
shut down reset our stack
off encrypt we're not going to use
all of these commands here um what we're
actually going to
walk through is up and down and then
we're not going to do reset but at home
i use those three
i haven't done our stats off no off
encryption
group yet with the hdi config and hdi
tool at all
so go ahead and scan it up um
basically saying that it's down i want
to stand it up
you run that command again and you have
your hci
um zero up and it says yes i'm up and
running
fantastic now that my bluetooth device
is up and running i
want it to scan the room
for devices that um basically are low
energy
so here i'm going to use the hdi tool
pseudo hci tool and then dash eye which
basically says hey i want you to
interact with things
um i want i want the first device to go
ahead and scan the room
so when i do that a low energy scan the
alpha will showcase
devices um and i and i should be able to
see my device
there are a bunch of other devices but i
blocked them out so what i wanted to
show you is
yeah they picked up my device um
[Music]
and it provided this address it looked
like a macbook
address and i'm like all right good so
let's go ahead and see if i can interact
so it's important though to note that
hdi tool has been depleted upstream
and if you currently just use hci tool
command without sudo then you'll be
picking up bluetooth classic
so make sure to include pseudo in order
to pick up low energy packets
and make sure that it works with low
energy 4.1 controllers
all right so now that i have the device
address i can connect using
the led light on the under hd tool
that's one way to connect there's
another way to connect under blue d
which is the blue
control um a bluetooth control is the
command line interface to
z um basically do a pseudo bluetooth
control
i want you to connect to this address
and then if things are okay and you can
connect it gets connected
and it tells you connections that's
successful one thing about low energy um
is that it can't do multiple connections
at once so if i have my phone app on my
scanner on my app connected
to um to my light bulb i need to make
sure that i disconnect
before i try to get my bluetooth control
to um connect between my first device
so make sure you disconnect and it's
only one pension at a time
all right so now what about some generic
attributes we have the clients and we
have the server
so the gap client corresponds to the
eighth
it does not know anything in advance
about the service attributes so it must
first inquire
communication needs to happen and
connections happen and basically i need
you to reveal what exactly is going on
with you
so it must first inform about the
presence and nature of those attributes
by performing service discovery
so what are the primary services that i
can um play with or
if i can't play with it what can you see
what can you feel what are your
characteristics
after completing service discovery it
can then start reading and writing
if permissions are there for you to
write and read
um found in the server as well receiving
server initiated updates
and then on the server side you have the
server again corresponding with the app
server um it receives requests from a
client and sends responses back
it also sends server initiated updates
when configured to do so
so every a low energy device sold must
include at least a basic gap
server that can respond to client
requests even but only to return
an error response and i'm actually going
to show you that on a screen capture i
got for
on my app when i wanted to scan and
connect with my
um like my smartphone
okay so generic attributes um
it's established in detail how the
change of all profile and
used for data um over a ble connection
it
deals only with actual data transfer
procedures
and formats it uses attribute protocol
again whenever you do your packet
analysis
make sure you're filtered down to your
app protocol so that you can actually
see the data or actually um capture the
right request
the right commands and actually get a
glimpse and gleam of the data exchange
so here's a little um table to showcase
how these things are nested within each
other
so the gap servers they have services
within services there are
characteristics like what exactly
do this value do what color of the light
bulbs do you want this to be do you want
to see dimmer do you want to shut off do
you want to
be right or not and basically in that
what are the descriptors
scriptures and values and all those
other attributes so
you have the descriptor at the small
level the micro level and that fits into
the characteristic
um think of it as a container of user
data
and metadata and then you have that
within the service and then when the
service you have that from the gas
server
um this again is taken from o'reilly um
book
um the um intro to um
which is low energy which is a great
primer
um it's not pink and purple in the book
i just made sure everything was pink and
purple for this presentation too
but the logo plus a beautiful color
scheme
all right so now that we have a basic
understanding of what the
generic um attributes are and the
importance of
attributes when it comes to analyzing
the data that's a
um that is being shared between my app
and a smart device
let's go ahead and take a look at the
browsing tool that i
um i thought when i wrote about this
proposal and this
presentation so we have the tool so the
gadget rule is
a way to discover read and write
characteristics with
um this tool onto basically the
um the characteristics and the values of
the attributes
it defines the data structure for
organizing characteristics
and attributes and atlanta and you can
launch natural interactive mode
basically set tool dashboard and then
you basically have all these commands
once you establish the connection
with the address you can say i want you
to reveal
your primary services i want you to
reveal these characteristics
they need known characteristics that
match um specifications
to the fig to the um special interest
group
but if the manufacturer creates this new
requirement or capability
that isn't quite defined by bluetooth
sigs
then these um characteristics can
include customized um identification
they're called unique universal um
identification numbers all right so
what can you do with gachal i want to
know my primary reveal your
characteristics
i want you to read the characteristics i
want you to
i want to write to the characteristics i
want to do a right request for
characteristics i want
scriptures of the characteristics and
then listen
and then we can interact all right so
here i go ahead and go back to my
my initial setup where i have a
pseudogat tool that's an interactive
mode
i go ahead and see that it's working and
i tell
the um i tell them say hey i want you to
connect to this address
because i want to learn more about it so
i go ahead and tell it connect
to the address and if it's usable
connect and then connect
once that happens i want to say i want
to say what was the primary service
directory so all i do is
primary service and then throughout the
characteristic commands you're going to
see this
attribute um and then you're going to
see the uid
and these are supposed to basically
match up against some sort of
specification some sort of
action if it's been um approved and
normalized by the
special interest group then it's going
to have a a
standard a standard number if not and
it's unique to the manufacturer then
it's going to have a customized
um id
all right so i want to do
characteristics which is much more
robust than primary
um have handles that look like they are
standard specifications from the special
interest group
and then further down it looks like
there is an incremental trend
that doesn't look like it's specified by
the special interest group i mean it
looks like
one two three four five six seven eight
nine abcd
1911 and then the next one is 1912 from
1913 1914
and that actually tells somebody like oh
that looks like it's
customized it's been generated um
and it doesn't basically it's not
specified
um it doesn't fulfill a specification of
the special interest group
all right so i bring this up because um
you have several ways to go about this i
approach this by using
an app called the nrf connect you can
download it on your phone
and again it scans and then i found my
device
and i connected with my device and then
it shows me the client
um clients gats and the um
server gas and all these characteristics
um both the specified
um characteristics that match with the
special interest group and then it shows
me the unknown characteristics
that tells me like oh that must be
customized that must be like what the
manufacturer
created and they're not telling me what
it is they're not going to tell me what
it can do
but it has a uid and it has um
submissions defined
some of these are right some of these
are um
read some of these are notified and and
some of these are
right but no response i'm like okay that
looks interesting
so you can also do that with that tool
where you type the primary and the
characteristics like i did in my
previous
um slide on your terminal but i think
the interface is much nicer and pleasant
on my password
okay so when we talk about the universal
unique
identifier a universal unique identifier
is a
128-bit number that should be unique um
i say you need to probably
should be um and there are two formats
the 16-bit
and the 32-bit um earlier i talked about
how
you know you have the specified
um numbers and characteristics
defined by the special interest group
special interest group and then you have
you know the companies having carte
blanche um
in creating a identifier
because they're creating some sort of
like um
capability or requirement that can be
matched or doesn't exist
um within the bluetooth special interest
group so if
you are basically utilizing something
that has been specified you are allowed
to use a shorter version
the 16-bit if you are customizing some
sort of requirement or capability and
there
isn't um a uid that utilized from the
special interest group
then you would have to use a 32-bit and
that would have to be exposed
whenever somebody does a um
characteristic discovery
so here again to note if a company or
developer creates a new requirement or
capability
that does not fit with any of the
standard uid the custom you
id can be generated and that is actually
available
um on that that generator tool is
available on the sig website so all you
bluetooth developers out there
again you can customize your uid
so here standard i have my table divided
into two you have the client
and then you have the server something
that's standard and specified
you take a look at the past hits 2006
now if you have a separate device and
you are actually having these
characteristics you would use the same
uid now if i take a look at the
customize at the client side
it's basically my manufacturer creating
some new requirements and there's that
custom
uuid where it's zero zero zero one zero
two three
four et cetera 1911 and then if you
recall
screen capture it actually has three or
four um
other characteristics that went to 12 13
and 14
at the end so these things are
because one of the things you need to do
is in order to um
interact or engage with a low energy
device
that permits somebody to read and write
um onto their service you will need
their id
you will need to understand how does a
handle play into this
and then you're going to need to
understand how the value
is attached to the handle and how the
handle is
linked to the identifier
all right attributes you have type
permissions
value and handle and then you put this
on the table
um basically you have the headset 201
it's identifier on the week identifier 1
and
the commission's read only security
these will actually
show up on a packet analyzer so
just keep these in mind and um it helps
better disable the specific tissues
and um identifying identifiers
all right so the objective here let's go
do a quick walkthrough you want to start
playing with your bluetooth low energy
devices at home
who doesn't i mean you can buy stuff
everywhere and you have your mobile
device
and why not right so my environment that
i'm going to walk through is i have my
blue
to um smart light bulb i have my mobile
app i have a sniffer
i have wire shark and i'm using my
raspberry pi
i use both the valley linux and adress
and operating system
the buster version so my
light bulb is on and i have my app i
have my app and it's communicating
i want to change colors um so basically
that's what i'm doing
but i also have my nrf connect app i
find out what my address is
i go ahead and say well i want to learn
more i want to go ahead and dig deeper
beneath the hood basically what is this
uid what is
unknown characteristic so i'm going to
go ahead and get a bluetooth zipper
um you can do a lot i use the truth one
here
you have an android mobile device you
can do that as well
um just enable the um sniffer
in the developer tool option um adafruit
ellie sniffer there are two boards the
blue one and the black one the black one
is actually version one the blue one is
version two
and then you have micro bit if you want
to play with the tcle jack out in cali
it's also known as the swiss army knife
for bluetooth
leverage the micro bet um they have a
population
adapter um on it and you can utilize
that or uber truth one which is
um a bit more expensive than adafruit
but not too expensive
there are high-end ones that are in the
thousands i don't recommend that you
just get one of these available online
all right so once i snap i go ahead and
feed my packet
to the um water chart and then here i
have my um
raspberry raspberry pi reason i use that
debian face
and i need linux and it's easy to use
and accessible
i go ahead and light my light bulb feed
information and then
be on my nrs connect get the information
i want and notice that there are a bunch
of unknown characteristics
and i know the permissions most of them
i can write to it but i don't know
anything else i go and get my sniffer i
get my
truth one install it and i want to make
sure it's working because sometimes it
doesn't work and see nothing here so i
go ahead and pull up
inspection analyzer and i'm like oh my
gosh it works fantastic
you want to make sure that it's pulling
up things that are the two parts i mean
the white lines we need to find wi-fi
you want to make sure things are going
up at the 2.4
all right so let's go ahead i feed my
data
on to my um it gets snipped and then it
gets into my terminal
i really don't want to do that because
it's hard to analyze i may miss
it i encountered problems earlier and it
got really frustrating because something
was wrong with the file and
i needed to stop because i reached my
limit and there is a way to get it fed
directly into
um wireshark lesson learned here most up
to date a recent wireshark
to um the capture feature and sometimes
it doesn't work
and it's inconsistent using the tmp of
the pipe
but i found things that work with the
pipe um with
you know calling it shark fin so if you
want to learn more about naming pipes
but if i go on linux
there's the website if you want to know
iphone pipes in
wireshark that's the website well as
well but i found these commands that
help and make everything work perfectly
fine
so you go ahead um sharp
um short fin you call in wireshark you
tell the uber tooth hey i want you to
start um
sniffing ellie and i want you to i'll go
ahead and send it directly to wireshark
and voila this is what i get i get
protocols that are low energy i get
protocols
attribute here but i want to filter it
because i don't want to be inundated
with so much
things i don't need so much noise so i
go ahead and filter it down to the d2l
um um here and if you recall earlier the
presentation the reason why it's l2 cap
that's actually transport the on the
routing um
mechanism for the protocol that actually
posts
the data that data gets exchanged so now
that i've filtered it and i get the
protocol that i want
i'm like all right let's go ahead and
look like requests
i go ahead and do that and i get my
information here
i get information about the bluetooth
low energy link clearer
i get information about the bluetooth
ltcap protocol and
the one i want to deal with and expand
is a bluetooth action
protocol because that is where i am
going to get the service
we need identifier information that is
where i'm going to get the
characteristic
duid and that's also where i'm going to
get the value
that contains the action um
that i want to edit all right so now
that i have that
information what exactly do i want to do
i
am going to basically utilize the blue
z tool um such as bluetooth control you
can do that or gat tool
um for that tool so with the blue z tool
i have here
um call it up connect to my bluetooth
workflow tell it to connect it's success
fantastic
i want to go ahead and select an
attribute name attribute
and then i want you to read or write you
have to have permissions to do that
though
and then if i want to use gap tool in
order to do those edits
i call and get tool set in interactive
mode go ahead and connect to the address
and once it tells the connection is
successful i go and tell them
say hey i want to do a character request
handle basically the hex that contains
the action i want to deal with
and then the value so i want you to go
ahead and do a right request
to this handle let's say zero zero one
two and i want you to change it to the
color
you shop so if you
are excited about it as i am obviously
i'm still very very excited about it
um here are some sources for you to get
started so you've got
blues you've got gastrul hci tools
all of these are discussed um as a
primer and a foundation in
getting started with bluetooth little
energy tools techniques for full power
networking
by kevin thompson um even robert
davidson
and then you have the iit hackers
handbook a practical guide to hacking
the internet of things by teaching
and then adafruit there are a bunch of
learned tutorials there that can help
you work with
either the fruit ellie sniffer or even
with uber truth one
and then you have the blue z dot website
itself
and a bunch of other tutorials online
but i'm
really excited about sharing my love
my love for bluetooth energy with you
and i hope
this has inspired you to get involved
and just start tinkering and playing
with all the devices that you have at
home already
so dave um i'm ready to take any
questions
all right um thank you so much this has
been
really fabulous so how long um
how long have you been doing this how
long have you been
sort of in this discovery process oh my
gosh it's been about
um trial and error it's been over a year
um so i started last
year and i was like well okay what else
can i do i started buying the hardware i
started exploring it adafruit
but then i also found that the thing
that
took the most time was how to know which
version know which version to utilize
and what
has been deprecated and
if it's been deprecated can i still use
it
with the um with all the actual hex
values and all of that and with pdu
and all that um you know what exactly is
the structure
with the bits and the headers and then
the payload
but um other than that it's been a
one-year journey so far
just trying to work set up my
environment get comfortable with the
operating system
and identify which sniffer is the best
for me and also with wireshark
you know it's gone through its own
iteration so i it's taking a while
but i like i like failing forward i like
learning
and it's been fun um i appreciate that
uh
this is root this is the time for folks
in the room
to go ahead and uh submit your questions
i did post a survey link
and then we've got a great question from
kim crowley um
are there lots of iot devices with the
linux
bluetooth stack on it
so i mean the linux bluetooth
stack i mean when it comes to operating
system
i mean with raspberry pi's or raspbian
operating system
like if it's a linux operating system
already
the bluetooth bluesy should be there
already
right um so
you've been in you've been in this for
around a year
um tell me what are the what are the top
two or three tips that
uh ria of today would give
to rhea a year ago
um set up your lab at home so that
you are um your environment is
accessible
and you have no option but to interact
with it
also the ria today knowing it's 2020 and
there is covid and
this is our environment you will have to
interact with it
but also um just go straight to kali
linux
you know don't worry about setting up
your virtual box
um with ubuntu or mint like just
go for kali linux i mean it comes with
wireshark already it comes with a btle
jack already
and um yeah just go ahead and just start
early and
get your hands dirty and you know you
can't really expect
i never really expected to learn and
pick up
anything within a week or two weeks or a
month like
i learned by failing and um yeah just
do it and document so three things
just go straight to cali set up your
environment and document
so you can um not you but
a person a person can get it into this
space
we're not talking about a million
dollars here we're talking about
uh a few components
you could you could set up what would
you what do you think you could set up a
lab for less than three hundred dollars
if you wanted to
yeah like um all operating systems are
downloadable
you can get a raspberry pi like four now
with amazing
like ram capabilities for like 50 bucks
or raspberry three for 35
um the blue fruit sniffer at adafruit
like get the blueboard updated one
that's like 35
and then the ubertooth or 35 or 40
dollars and the ubertruth is like 135.
and you don't need all of them like just
choose one and
and play with it if you have an android
mobile device
there's actually a developer um setting
enable the bluetooth low energy
sniff capture and there you go like two
things in one
and you can basically do a data dump
onto your um
to your host and start analyzing that
way or convert it to a pcat file and
send it to wireshark
i only discovered that i could use micro
bit by accident i actually got a micro
bit board
two three years ago and i only found out
recently that i can use it as a sniffer
because my uber tooth
originally wasn't working and i started
panicking no
so um yeah there are things out there
that are available if you have a mobile
devices android
take a look at your developer settings
if you can um
spare like 35 40 dollars take a look at
adafruit um
bluefruit sniffer if you want to go uber
choose one
and play with you know a great spot like
those gadgets
go ahead and like save 135 but it's it's
accessible and it works like raspberry
pi's are fantastic
operating systems are free yeah
okay can you comment at all about
um online communities or forums
that folks particularly beginners
might might think about using um
or just hanging out and and lurking and
listening from
any suggestions there i would just
probably go to them
learning um modules not learning logical
learning like
sub sites on adafruit for one i
basically go
to the documentations for like raspberry
pi
or even forums that focus on wireshark
because that's really helpful
um but like interactive chat rooms i
don't have a list of that
yet it's been very much a passive um
research when it comes to looking for
um blog posts and videos and um
free classes if you can
okay well i think we just have a
new addition to the list of online
resources that are available to new
folks who are looking to get into
a bluetooth low energy uh in in the this
has just been a
really fascinating presentation i really
appreciate it
um we don't have any more questions so
we i thank you very much for your time
uh
this has been great and uh thank you to
the attendees
for joining us today uh please remember
to fill out this survey
uh it's it's in the it's in the stage
chat
and have a great conference everybody
thank you dave bye everybody have a
great conference