bastian/debyl-site
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

noticket - markdownlint fixes

Browse Source
This commit is contained in:
Bastian de Byl
2023-10-14 16:45:34 -04:00
parent 5f4c121113
commit 51d9ba3390
5 changed files with 13 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
content/post/bt_win_linux.md
View File

@@ -14,11 +14,12 @@ This is a guide written on how to share the same Bluetooth device(s) across Wind
1. Pair your Bluetooth device(s) with Linux **first** 1. Pair your Bluetooth device(s) with Linux **first**
2. Reboot into Windows, then re-pair the devices with Windows 2. Reboot into Windows, then re-pair the devices with Windows
3. Run `regedit` **as Administrator** 3. Run `regedit` **as Administrator**
4. Navigate to: 4. Navigate to:
```
```text
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys
``` ```
If you **do not see any Keys under the tree** then you need to open `regedit` as a system-account user. One way to do this is using the PsExec by [downloading it from Microsoft Sysinternals](https://learn.microsoft.com/en-us/sysinternals/downloads/psexec). Once it is downloaded, you will need to run a command-prompt **as Administrator** and navigate to the location `PsExec` is unzipped and run `PsExec.exe -s -i regedit`. The Bluetooth keys should now be visible. If you **do not see any Keys under the tree** then you need to open `regedit` as a system-account user. One way to do this is using the PsExec by [downloading it from Microsoft Sysinternals](https://learn.microsoft.com/en-us/sysinternals/downloads/psexec). Once it is downloaded, you will need to run a command-prompt **as Administrator** and navigate to the location `PsExec` is unzipped and run `PsExec.exe -s -i regedit`. The Bluetooth keys should now be visible.
5. Right-click on `Keys` in the left-hand pane and select `Export`. During the dialog change `Save as type` to `Text files` and that the `Export range` is set to `Selected branch`. Store this somewhere **accessible by both Windows and Linux** -- if a shared drive is unavailable, use a USB drive or cloud-storage. 5. Right-click on `Keys` in the left-hand pane and select `Export`. During the dialog change `Save as type` to `Text files` and that the `Export range` is set to `Selected branch`. Store this somewhere **accessible by both Windows and Linux** -- if a shared drive is unavailable, use a USB drive or cloud-storage.
@@ -28,10 +29,12 @@ This is a guide written on how to share the same Bluetooth device(s) across Wind
9. Open the `info` file, with root privileges, in the text editor of your choice. 9. Open the `info` file, with root privileges, in the text editor of your choice.
10. In another tab/window, using either a text viewer or editor, open the **previously exported Windows registry text file for the device** 10. In another tab/window, using either a text viewer or editor, open the **previously exported Windows registry text file for the device**
11. From the **Windows** file, copy the Bluetooth Key. Example: 11. From the **Windows** file, copy the Bluetooth Key. Example:
```
```text
00000000 31 c0 08 fa 4f 7b d2 4c - 6f e1 7d ba 32 29 a9 a7 1À.ïO{ÒLoá}ºQ)©§ 00000000 31 c0 08 fa 4f 7b d2 4c - 6f e1 7d ba 32 29 a9 a7 1À.ïO{ÒLoá}ºQ)©§
``` ```
_From the above copy `31 c0 .... a9 a7`_ _From the above copy `31 c0 .... a9 a7`_
12. Paste the key from the previous step into the `Key=` portion of the **Linux** Bluetooth `info` file. Make sure to **remove all spaces, hyphens, and change all characters to upper-case (all-caps)**. 12. Paste the key from the previous step into the `Key=` portion of the **Linux** Bluetooth `info` file. Make sure to **remove all spaces, hyphens, and change all characters to upper-case (all-caps)**.
13. Save the `info` file with the changes to complete device sharing. Repeat for any other Bluetooth devices to share. 13. Save the `info` file with the changes to complete device sharing. Repeat for any other Bluetooth devices to share.

2
content/post/headphone-fix.md
View File

@@ -19,7 +19,7 @@ with the catch being: _I had to fix them_
Past mistakes have taught me to be gentle and patient when it comes to taking Past mistakes have taught me to be gentle and patient when it comes to taking
things apart. This was no exception either. After looking over the unit on each things apart. This was no exception either. After looking over the unit on each
side, I figured the only way *in* was lifting the mesh cover off. So I went at side, I figured the only way _in_ was lifting the mesh cover off. So I went at
it, carefully, with a pair of tweezers. I worked my way around the edge and it, carefully, with a pair of tweezers. I worked my way around the edge and
wedged the mesh upwards. wedged the mesh upwards.

2
content/post/password_checker.md
View File

@@ -106,7 +106,7 @@ getpws()
} }
``` ```
This accomplishes our *first goal* of checking duplicate passwords -- This accomplishes our _first goal_ of checking duplicate passwords --
**hooray!** **hooray!**
# Passwortstärke # Passwortstärke

2
content/post/stm32-part1.md
View File

@@ -109,7 +109,7 @@ For accomplishing this, a few things need to happen:
{{< admonition warning "Note for Different STM32Fx Microcontrollers" >}} {{< admonition warning "Note for Different STM32Fx Microcontrollers" >}}
Review the datasheet for the specific **STM32Fx** microcontroller being Review the datasheet for the specific **STM32Fx** microcontroller being
programmed, as the Alternate Function mappings may be *significantly* different! programmed, as the Alternate Function mappings may be _significantly_ different!
{{< /admonition >}} {{< /admonition >}}
## GPIO Alternate Function Setup ## GPIO Alternate Function Setup

2
content/post/updating_gpg_key.md
View File

@@ -229,4 +229,4 @@ gpg --armor --export-secret-keys YOUREMAILADDRESS | gpg --armor --symmetric --ou
Import it in OpenKeychain (_may require deletion in OpenKeychain first -- make Import it in OpenKeychain (_may require deletion in OpenKeychain first -- make
sure **not to revoke and delete!**_) and we're done! sure **not to revoke and delete!**_) and we're done!
[^1]: https://guardianproject.info/archive/luks/ [^1]: [guardianproject.info/archive/luks/](https://guardianproject.info/archive/luks/)