Merge pull request #1 from rtx4d/master

Update old image links

_posts/2018-09-17-Qualcomm-Firmware.md

@@ -5,7 +5,7 @@ title: Qualcomm's Chain of Trust
 
 ## Covering Qualcomm's chain-of-trust up to the point of Android being loaded
 
-![hero](https://lineageos.org/images/engineering/hero_qualcomm_firmware.jpg)
+![hero](https://lineageos.org/images/engineering/hero_qualcomm_firmware.webp)
 
 The Qualcomm chain-of-trust is a complex, yet straightforward to understand set of processes. Many of you have likely heard the term “bootloader” but have no clue what it actually is, or does.
 
@@ -60,15 +60,15 @@ Diagrams to describe the maturity process of the chain of trust follow:
 
 ### Pre-2013 Era
 
-![2013-2014 Era diagram](https://lineageos.org/images/engineering/content_qualcomm_firmware_0.png){: .blog_post_image_content }
+![2013-2014 Era diagram](https://lineageos.org/images/engineering/content_qualcomm_firmware_0.webp){: .blog_post_image_content }
 
 ### 2013-2016 Era
 
-![2015-2017 Era diagram](https://lineageos.org/images/engineering/content_qualcomm_firmware_1.png){: .blog_post_image_content }
+![2015-2017 Era diagram](https://lineageos.org/images/engineering/content_qualcomm_firmware_1.webp){: .blog_post_image_content }
 
 ### Modern (2016-2018) Era
 
-![2018 Era diagram](https://lineageos.org/images/engineering/content_qualcomm_firmware_2.png){: .blog_post_image_content }
+![2018 Era diagram](https://lineageos.org/images/engineering/content_qualcomm_firmware_2.webp){: .blog_post_image_content }
 
 As you can see, the boot chain has evolved significantly. In 2015, the possible attack area was condensed, and the Secondary Bootloader (SBL) chain was merged into one unified SBL.
 As we move further down the line we see SBL entirely replaced with Qualcomm’s new proprietary solution, the eXtensible Bootloader (XBL), which mitigated many of the security

_posts/2021-02-25-Working-with-SELinux-on-Android.md

@@ -6,7 +6,7 @@ author: Aayush Gupta (theimpulson) & Nolen Johnson (npjohnson)
 
 ## Understanding the basics of SELinux
 
-![hero](https://lineageos.org/images/engineering/hero_selinux.jpg)
+![hero](https://lineageos.org/images/engineering/hero_selinux.webp)
 
 ## Glossary
 

_posts/2023-10-10-Android-Debugging-Crash-Course.md

@@ -6,7 +6,7 @@ author: Nicholas Lim (niclimcy) & Nolen Johnson (npjohnson)
 
 ## Understanding the different tools used during debugging
 
-![hero](https://lineageos.org/images/engineering/hero_debugging.jpg)
+![hero](https://lineageos.org/images/engineering/hero_debugging.webp)
 
 ## Glossary
 * ADB: Android Debug Bridge.
@@ -34,7 +34,7 @@ author: Nicholas Lim (niclimcy) & Nolen Johnson (npjohnson)
 ## What is Debugging?
 To understand Android debugging, it is important to understand the different parts of the Android system. At a high level, the Android system is made up of three main components: apps, the platform, and the kernel.
 
-![Android Stack](https://lineageos.org/images/engineering/content_android_stack.png){: .blog_post_image_content }
+![Android Stack](https://lineageos.org/images/engineering/content_android_stack.webp){: .blog_post_image_content }
 
 ## User Space Debugging
 User space debugging allows us to find and fix app and platform issues. This process can be fairly straightforward on Android if we use the right tools.
@@ -273,7 +273,7 @@ If all else fails, you can use `panic()` in portions of the kernel you wish to d
 Here are some custom debugging tools developed by OEMs we found over the years that have proved helpful.
 
 ### EDL memorydump (qcom)
-![Qualcomm CrashDump](https://lineageos.org/images/engineering/content_qualcomm_crashdump.png){: .blog_post_image_content }
+![Qualcomm CrashDump](https://lineageos.org/images/engineering/content_qualcomm_crashdump.webp){: .blog_post_image_content }
 
 Some Qualcomm devices have CrashDump enabled, which allows you to use Qualcomm's firehose tool to get a memorydump. As the firehose tool is closed source, we recommend using a rewritten open source version of the tool by Bjoern Kerler, which can be found here at [bkerler/edl](https://github.com/bkerler/edl). You can retrieve a memory dump using `edl memorydump`.
 
@@ -344,4 +344,4 @@ dlopen(libloc_socket.so) -> 0x2229c8abec54dac9, errno: (null)
 ```
 
 ## Bonus
-While working on non private system apps like Aperture, you could use [Android Studio](https://developer.android.com/studio) for easier testing and debugging!
+While working on non private system apps like Aperture, you could use [Android Studio](https://developer.android.com/studio) for easier testing and debugging!