Parser for btsnoop
A project that analyzes btsnoop file.
example 1:
Display btsnoop pakcet info
from btsnoop.btsnoop import *
btsnp = btsnoop('btsnoop_hci.log')
print(btsnp.parsed[0:10])
example 2:
Get remote / local device information in a list of dictionaries:
[{'peer_addr': '90:3A:E6:2A:08:15',
'name': 'MyLink Malibu',
'oui': 'PARROT SA,174 Quai de Jemmapes Paris FR 75010 ',
'lmp_manufacture': 'Texas_Instruments',
'lmp_version': 'V4_0',
'lmp_subversion': 7002,
'profiles': [(<service_class_t.AdvancedAudioDistribution: 4365>, '1.2'),
(<service_class_t.Handsfree: 4382>, '1.6'),
(<service_class_t.AV_RemoteControl: 4366>, '1.4')
]
},
]
btsnp = btsnoop('btsnoop_hci.log')
remote_info = btsnp.get_remote_info()
print(remote_info)
example 3:
Find ACL connections which are sucessful or failed due to some kind of error
btsnp = btsnoop('btsnoop_hci.log')
conns = btsnp.get_acl_connections(status=8)
print(conns)
This is the README file for the project.
The file should use UTF-8 encoding and can be written using reStructuredText or markdown with the appropriate key set. It will be used to generate the project webpage on PyPI and will be displayed as the project homepage on common code-hosting services, and should be written for that purpose.
Typical contents for this file would include an overview of the project, basic usage examples, etc. Generally, including the project changelog in here is not a good idea, although a simple “What's New” section for the most recent version may be appropriate.
Metadata
Release files for btsnoop 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| btsnoop-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for btsnoop-1.1.0-py3-none-any.whl |
Release files / btsnoop-1.1.0-py3-none-any.whl
| Download URL | btsnoop-1.1.0-py3-none-any.whl |
|---|---|
| Size | 809.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
db001d837a73d7873c7b547814b28b57be9ce803b24bf8ff312207280e7cd0dd
|
|
BLAKE2b-256 checksum How to use checksums |
0e4ddfaa80332084cf60760f8d35d7508ea4d80964cafe6b9f5661ea23531fa2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.7.0
|
Security for btsnoop 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.