Guide Comprehensive Guide to Safely Extracting L3 Keys: From Setup to Key Management

[tectpro]

I'm writing this guide as many of you have expressed a keen interest in learning more about it.
This guide is intended for educational purposes only, and its goal is to empower you with the information and skills you need.

Please Read Before Continuing:

Before we dive into the details of this guide, I urge you to take a moment to read the following important warning.
It contains crucial information that safeguards your interests and ensures a better understanding and application of the guide's content.

Important Warning:

Under no circumstances should you purchase L3 or L1 from any sources (such as Telegram or Discord). These transactions not only typically require cryptocurrency but also pose significant risks:

1. Risk of Fraud: A high likelihood of being scammed right at purchase. This often involves making a payment in cryptocurrency and then not receiving the promised goods.
   
   
2. Risk of Compromised Keys: Even if you do receive something, there's a good chance you'll end up with "shared" keys. Hundreds of others simultaneously use these keys, which will likely be revoked within a few days, rendering them useless.

For these reasons, extracting these items yourself is strongly advised, ensuring a safer and more reliable process.

With this understanding, let's proceed with the guide.

Getting Started: Essential Setup and Downloads​

Before we dive into the main content of this guide, it's crucial to ensure you have all the necessary tools and software ready. This section outlines everything you need to download and set up beforehand. Follow these steps carefully to prepare your environment, making the rest of the guide easier.

1. Python Installation​

Python is a fundamental tool for our work. If it's not already installed on your system, here's how to do it:

• Visit the Python official website at https://www.python.org/downloads/ and download the latest version.
• Run the installer and follow the on-screen instructions. Tick the boxes that say "Use admin privileges when installing py.exe" and "Add python.exe to PATH" during installation.
  

2. Android Emulator Hypervisor Driver​

For efficient emulation, the Android Emulator Hypervisor Driver is required:

• Go to https://github.com/google/android-emulator-hypervisor-driver/releases and download the latest release.
• Extract the zip file, right-click on silent_install.bat and choose Run as administrator, this will take a moment.

3. Android Studio Setup​

Android Studio is the IDE for Android development, which we'll use for specific tasks:

• Download Android Studio from https://developer.android.com/studio. Kindly note that this is roughly 1GB in file size.
• Install Android Studio, but do not select an Android Virtual Device during installation.
  

• Add the end leave Start Android Studio selected.
• Click Next until you reach the license Agreement, where you must Accept all of them before clicking on Finish.
  

• This will now take a while to download and install additional components. Please be patient. During this process, you might be asked to Accept or Continue.
• Once the installation is completed, you will see a screen similar to the one on the screenshot below.
  
• Close this screen for the moment as we come back to it at a later point.

4. Dumper Tool​

The Dumper tool is crucial for some of the processes we'll be undertaking:

• Navigate to the Dumper's GitHub page at https://github.com/wvdumper/dumper.
• Click on the 'Code' button and then 'Download ZIP'. Save the ZIP file to your computer.
  
• Extract the ZIP file into a dedicated folder where you'll be working with the Dumper tool.
• Open an elevated command prompt (Admin) in the folder where you extracted dumper-main
• Run the command pip3 install -r requirements.txt which is an essential step as it automatically installs all the Python package dependencies listed in the requirements.txt file, ensuring your project environment is correctly set up with the necessary libraries.

5. Installing Frida Tools​

While Frida itself will be installed as part of the Dumper tool's requirements, frida-tools is a separate set of utilities that enhances Frida's capabilities:

• Ensure you have Python and Frida installed as per the previous steps.
• Open your command line interface (CLI) and execute the following command to install frida-tools:
  pip install frida-tools
• The installation will be completed shortly, and frida-tools will be added to your toolkit.

6. Setting Up Frida Server for Android Emulator​

The Frida Server enables Frida to interact with your Android emulator. Here's how to set it up:

Download Frida Server:​

1. Visit the Frida releases page on GitHub at https://github.com/frida/frida/releases.
2. As we're using an Android Studio emulator for Android Pie, which typically uses x86 architecture for improved performance, look for the Frida Server binary compatible with x86. Specifically, download frida-server-16.2.1-android-x86.xz.

Place the Frida Server in the Correct Directory:​

1. Extract the downloaded .xz file using WinRAR or another software that supports .xz archives, such as 7-Zip.
2. Move the extracted frida-server file to your Android SDK platform-tools directory, typically located at C:\Users\yourname\AppData\Local\Android\Sdk\platform-tools. Make sure to replace yourname with your actual Windows username.
   

Version Verification:​

1. To ensure compatibility, verify that the Frida Server version matches the Frida version installed. Open a command line prompt and run frida --version in your command line interface to check the installed Frida version.
2. Compare this version number with the version of the Frida Server you've downloaded (16.2.1 in this case) to confirm they align.

Important Note: Ensuring that the Frida Server and the installed Frida version on your system are compatible is essential for a smooth and error-free operation. Version mismatches may lead to unexpected issues during runtime, so confirming this compatibility is critical.


Please ensure that all these tools are installed and set up correctly before proceeding to the next steps of the guide.
This preparation is vital for executing the tasks ahead smoothly and successfully.


Now that all the necessary tools and software are set up, you are fully prepared for this exciting journey.
The groundwork we have laid together is crucial for the smooth execution of upcoming steps, ensuring you have a solid foundation on which to build.

Starting Android Studio and Creating a Virtual Device​

Now that our environment is ready, the next step is to start Android Studio and set up a new virtual device that will be used for our tasks. Follow these steps to create your virtual device:

1. Launch Android Studio:
   • Open Android Studio on your computer. If this is your first time running it, the setup wizard may guide you through some initial configurations.
2. Access the Virtual Device Manager:
   • Once Android Studio is open, find the Virtual Device Manager. Click on "More Actions" and click on "Virtual Device Manager".
     
3. Create a New Virtual Device:
   • In the Device Manager window, click the "+" button to create a new virtual device.
     
     
     
   • Select "Pixel 6" from the list of devices. Then click "Next".
     
4. Select the System Image:
   • Now, you need to choose the operating system for your virtual device. Look for the "Pie" system image corresponding to Android 9. It's crucial to select Pie, as our guide is specifically tailored for this version of Android.
   • If you haven't downloaded the Pie system image, click the "Download" arrow next to it. Depending on your internet connection, this process may take some time.
     
5. Verify and Finish:
   • After downloading the system image, ensure that "Pie" is selected and then click "Next".
     
     
     
   • Review the configuration to verify that it shows "Pixel 6" and "Android Pie". Then, click on "Finish". The setup will take a moment to complete, depending on your system's capabilities.
     

Once the virtual device is created, it will appear in your Device Manager.
You can then start the virtual device by clicking on the "play" button next to it. Depending on your system, this might take some time.


Note: The screenshots in Android Studio might show different devices or Android versions, but follow these instructions to select "Pixel 6" and "Android Pie".

Interacting with the Virtual Device using ADB​

With your Android virtual device up and running, the next step is to use ADB to install and start the Frida Server. This process requires you to be in the ADB directory C:\Users\yourname\AppData\Local\Android\Sdk\platform-tools. Remember to replace yourname with your actual Windows username.

Note: In the following commands, please ensure to replace frida-server-16.2.1-android-x86 with the actual version of the Frida Server you downloaded and installed. This adjustment ensures compatibility and smooth operation.

1. Open an Elevated Command Line:
   • Navigate to the ADB directory: C:\Users\yourname\AppData\Local\Android\Sdk\platform-tools.
   • Open a command prompt window as an administrator in this directory.
2. List Connected Devices:
   • In the command prompt, type the following and press Enter:
     adb.exe devices
     
     
   • This command lists all connected Android devices. The device listed as "device" is the one you're working with. If there's only one listed, that makes things simpler.
     
3. Push Frida Server to the Virtual Device:
   • To upload the Frida Server to your Android device, use the following command:
     adb.exe push frida-server-16.2.1-android-x86 /sdcard
     
     
     
   • If you have more than one device connected, you'll need to specify which one by using the -s option, followed by the device identifier (e.g., emulator-5554):
     adb.exe -s emulator-5554 push frida-server-16.0.2-android-x86 /sdcard
4. Gain Administrative Rights and Execute Frida Server:
   • Now, you must move Frida Server to a suitable directory, change its permissions, and execute it. Start by opening a shell on the device:
     adb.exe shell
     
     
     
   • If you have multiple devices, specify which one as before:
     adb -s emulator-5554 shell
     
     
   • Gain superuser access by typing su and pressing Enter.
     
     Then, execute the following commands one by one:
     

     mv /sdcard/frida-server-16.2.1-android-x86 /data/local/tmp
     chmod +x /data/local/tmp/frida-server-16.2.1-android-x86
     /data/local/tmp/frida-server-16.2.1-android-x86

     
     
   • Important: Keep the command prompt open after starting the Frida Server. Closing it will stop the Frida Server process.

Extracting Keys with the Dumper​

With Frida Server running on your virtual Android device, you can now use the dumper to extract keys.
This process involves executing a script from the dumper's directory and interacting with a specific web page on your virtual device.

Navigate to the Dumper's Folder:​

• Open File Explorer and go to the folder where you extracted the dumper tool earlier.

Run the Dumper Script:​

• Open a command prompt window in this directory.
• In the command prompt, type the following command and press Enter:
  python dump_keys.py
  
  
• Keep this command prompt open. It's crucial for the dumping process.

At this point, you should open two command prompt windows: One command prompt running the Frida Server and one executing the dumper script.

Note: If you encounter an error message similar to "If this call came from a _pb2.py file, your generated code is out of date," it indicates a version compatibility issue with the protobuf package. To resolve this, you may need to downgrade your protobuf package to version 3.20.0. Within the open command prompt, using the command pip install protobuf==3.20.0. This adjustment ensures compatibility and smooth operation of the dumper script. Repeat the step above with python dump_keys.py.
If you no longer encounter any errors, you are ready to proceed.

Interact with the Web Page:​

• On your virtual Android device, open the Chrome browser. Do not sign in!
• Navigate to the DRM demo page by entering the following URL: https://bitmovin.com/demos/drm
  When asked if you want to play protected video, click Accept/Yes.
• The dumper automatically extracts keys when the page loads, and DRM content processing begins.

Managing the Extracted Keys
After the dumper completes its work, you'll find the extracted keys in a specific directory structure within the dumper's folder:

Locate the Keys:​

• Navigate to the key_dumps folder inside the dumper's directory. The path will look similar to X:\dumper\key_dumps\Android Emulator xxxxx\private_keys\xxxx\xxxxxxxxxx. The exact path may vary depending on your device and the processed content.

Rename the Key Files:​

• In the final directory, you'll find files named client_id.bin and private_key.pem.
  You need to rename these files for further use:
  • Rename client_id.bin to device_client_id_blob.
  • Rename private_key.pem to device_private_key.

This renaming step is essential for the following stages of your work. It ensures the files are correctly identified and utilized by any subsequent processes or tools you will use.


In closing, remember that the extracted L3 keys are sensitive and should not be shared with anyone.
Should you require new keys in the future, simply revisit the section 'Starting Android Studio and Creating a Virtual Device,' provided all the necessary tools remain installed on your system.

This guide was created with special approval, emphasizing its unique contribution to educational purposes.
As such, please understand that this topic will be closed for comments to maintain clarity and focus.

Thank you for your understanding.

 

[tectpro]

FAQ:
Question: Can you create an L3 key for me?

Response: As emphasized in the guide, I cannot generate or share L3 keys with anyone. The guide provides detailed, step-by-step instructions designed to empower you to perform the task independently and straightforwardly.


Question: You mention L3 and L1, but there's no L1 in the tutorial.

Response: You're correct. The tutorial focuses explicitly on L3 keys due to their accessibility for educational purposes. L1 keys involve complexities that require a physical device, and for security and ethical reasons, a tutorial on L1 keys will not be provided. The warning section mentions L1 and advises against purchasing such keys from unverified sources.


Question: I have problems following the guide!

Response: If you encounter any difficulties, please send me a private message with the title of this tutorial, a detailed description of the problem you're facing, and a screenshot, if possible. I'll do my best to assist you. Remember that my response might not be immediate, and my assistance will be limited to setting up the necessary tools and ensuring they're operational. I won't be able to create keys for you.


Question: Why do I have to create a virtual device? Can't I use my phone?

Response: Utilizing a virtual device is recommended due to its ease of use and increased security. Using an actual device would require enabling certain features that might compromise your phone or tablet's apps and overall security. Therefore, a virtual device is the preferred choice for this tutorial and to maintain a safe learning environment.


Question: This tutorial is so long, can't you shorten it?

Response: The length and detail of the tutorial are intentional to ensure that individuals of varying technical backgrounds can follow along successfully. Each step has been carefully explained to avoid confusion, providing a comprehensive understanding of the process. As such, no plans exist to create a condensed version of this tutorial.

 

[tectpro]

I made this guide for anyone who loves Tux with Ubuntu Linux users in mind.
Remember, it might not be the same if you're using a different Linux version.

Who is Tux? Tux is the official mascot of the Linux operating system. It's a cute, chubby penguin that represents Linux in various logos.

Getting Started: Essential Setup and Downloads​

This guide is intended for educational purposes only, and its goal is to empower you with the information and skills you need.

1. Python Installation​

Python is indispensable for this task. Here's how to set it up on Ubuntu:

• Open a terminal with Ctrl + Alt + T.
• Check if Python is installed by entering python3 --version. Ubuntu usually comes with Python pre-installed.
• If you need to install or update Python, use:
  sudo apt update && sudo apt install python3
  
  
  
  
• Install pip, the Python package manager, to manage your Python libraries:
  Enter into the terminal sudo apt install python3-pip and confirm with Y when asked.
  
  

2. Android Studio Setup​

Android Studio includes everything you need for Android development, including the Android Emulator.

• Download Android Studio from the official site https://developer.android.com/studio
• To extract the .tar.gz file, we use the graphical user interface (GUI).
• Extract the downloaded file by right-clicking and selecting 'Extract Here'. Wait for the extraction to complete.
  
  
  
• You should now see a folder containing the extracted and downloaded files.
  
• Copy the extracted folder to a location of your choice. Please remember the location!
  
  
• After you copied the folder to the new location, follow these steps:
  • 1. Open the extracted folder.
    
    
  • 2. You'll find the 'android-studio' folder inside the extracted folder. Open it.
    
    
  • 3. Once you're in the 'android-studio' folder, open the 'bin' folder.
    
    You should now be in the following directory: /home/ubuntu/androidxxx/android-studio/bin
    It may look different on your machine.
• Start Android Studio by running studio.sh in the bin directory of the extracted folder.
  Right-click on the file studio.sh and click "Run as a Program".
  
  
  
  
• Follow the installation wizard, which will guide you through the setup process.
• You must accept all Licenses in the License Agreement before you can proceed.
  
  
  
  
• Wait for the process to complete. This might take a while.
• Once you see the window in the screenshot below, close it now, as we will return to it later.
  
  

3. Dumper Tool​

The Dumper tool is a helpful tool necessary for this task:

• Download the Dumper tool from its GitHub repository: https://github.com/wvdumper/dumper, and choose the 'Download ZIP' option.
  
  
  
• Extract the ZIP by right-clicking on the ZIP file, clicking "Extract here," and moving the folder to a location of your choice.
  
  
• Navigate to the Dumper tool directory, right-click a space, and click "Open in Terminal".
• Install required Python dependencies by entering the following into the terminal
  pip3 install -r requirements.txt

4. Installing Frida Tools
Frida is a dynamic toolkit for developers:

• Install Frida tools using the terminal that's already open from the previous step by entering the following command:
  pip3 install frida-tools
  
  
• You will see a warning similar to the one in the screenshot below
  
  
  
• To resolve this, you should add /home/ubuntu/.local/binto your PATH. Here's how to do it:
  1. Open a new terminal.
     
     
  2. You need to edit your .bashrc or .profile file (the file to edit can depend on your shell and system configuration but .bashrc is a common choice for Bash shell users). You can use a text editor like nano for this purpose:
     Type the below command into your terminal and hit Enter.
     nano ~/.bashrc
     
     
  3. Scroll to the end of the file and add the following line:
     export PATH="$PATH:/home/ubuntu/.local/bin"
     
     This command appends /home/ubuntu/.local/bin to the existing PATH.
     
     
     
  4. Save and close the file.
     If you use nano, you can do this by pressing Ctrl + X, then Y to confirm the changes and Enter to close.
     
     
  5. For the changes to take effect, you need to reload your .bashrc. You can do this by typing the following command in the terminal:
     source ~/.bashrc
     
     The directory containing the Frida scripts has been added to your PATH, and you should be able to run the Frida tools from any directory in your terminal. You can verify that the directory was successfully added to the PATH by echoing the PATH variable:
     echo $PATH
     You should see /home/ubuntu/.local/bin listed in the output. Now, Frida tools should work without any issues related to the PATH.
     
     
     With Frida tools installed, the next step is to download the Frida Server.

5. Setting Up Frida Server for Android Emulator
The Frida Server facilitates the interaction between Frida and your Android emulator. Here's how you can set it up:

• Download the Frida Server:
  • Open a terminal and type frida --version to verify the version of frida that has been installed.
    
  • Next, open a browser and navigate to the Frida releases page on GitHub at https://github.com/frida/frida/releases.
    
    
  • Since we're using an Android Studio emulator for Android Pie, which typically employs x86 architecture for enhanced performance, identify the Frida Server binary compatible with x86. Specifically, download frida-server-16.2.1-android-x86.xz.
• Place the Frida Server in the Appropriate Directory:
  • Extract the downloaded .xz file by right-clicking on it and clicking on "Extract Here"
• Verify the Version:
  • Ensuring that the Frida Server version aligns with the installed Frida version is crucial to guarantee compatibility. Open a command line and execute frida —-version to check the installed Frida version.
    
    
  • Cross-reference this version number with the Frida Server version you downloaded (16.2.1) to verify they match.
    
    
  • To avoid unexpected runtime issues, it is vital to ensure compatibility between the Frida Server and the installed Frida version.

6. Installing ADB (Android Debug Bridge)
ADB is an essential tool for Android development, allowing you to send a wide array of device commands through your computer. Here's how to install it on Ubuntu:

• Open a terminal window with CTRL+ALT+T
• Install ADB by running the following command:
  sudo apt install adb confirm with Y when asked.

Please ensure all these tools are correctly installed and configured before proceeding with the guide.
This preparatory step guarantees subsequent tasks' smooth progression and success.

With all the necessary tools and software now set up, you're well-prepared to embark on this exciting journey.
Our foundational work is key to the smooth execution of the following steps and provides a sturdy base for future endeavours.

Starting Android Studio and Creating a Virtual Device​

Now that our environment is ready, the next step is to start Android Studio and set up a new virtual device that will be used for our tasks. Follow these steps to create your virtual device:

1. Launch Android Studio:
   • Go to the folder that you extracted and moved in point 2, for example /home/ubuntu/androidxxx/android-studio/bin
     
     
   • Open Android Studio by right-clicking on studio.sh and clicking on "Run as a Program". If this is your first time running it, the setup wizard may guide you through some initial configurations.
2. Access the Virtual Device Manager:
   • Once Android Studio is open, find the Virtual Device Manager. Click on "More Actions" and click on "Virtual Device Manager".
     
     
3. Create a New Virtual Device:
   • In the Device Manager window, click the "+" button to create a new virtual device.
     
     
     
     
     
   • Select "Pixel 6" from the list of devices. Then click "Next".
     
     
4. Select the System Image:
   • Now, you need to choose the operating system for your virtual device. Look for the "Pie" system image corresponding to Android 9. It's crucial to select Pie, as our guide is specifically tailored for this version of Android.
   • If you haven't downloaded the Pie system image, click the "Download" arrow next to it. Depending on your internet connection, this process may take some time.
     
     
5. Verify and Finish:
   • After downloading the system image, ensure that "Pie" is selected and then click "Next".
     
     
     
     
     
   • Review the configuration to verify that it shows "Pixel 6" and "Android Pie". Then, click on "Finish". The setup will take a moment to complete, depending on your system's capabilities.
     
     

Once the virtual device is created, it will appear in your Device Manager.
You can then start the virtual device by clicking on the "play" button next to it. Depending on your system, this might take some time.

Note: The screenshots in Android Studio might show different devices or Android versions, but follow these instructions to select "Pixel 6" and "Android Pie".

Interacting with the Virtual Device using ADB​

With your Android virtual device up and running, the next step is to use ADB to install and start the Frida Server. This process requires you to be in the directory where you extracted the frida-server-16.2.1-android-x86.

Note: In the following commands, please replace frida-server-16.2.1-android-x86 with the version of the Frida Server you downloaded and installed. This adjustment ensures compatibility and smooth operation.

1. Open a new terminal:
   • Navigate to the directory where you extracted the frida-server-16.2.1-android-x86
   • Open a new terminal by right licking into a space and click on "Open in Terminal"
2. List Connected Devices:
   • In the terminal, type the following and press Enter:
     adb devices
     
     
   • This command lists all connected Android devices. The device listed as "device" is the one you're working with. If there's only one listed, that makes things simpler.
     
3. Push Frida Server to the Virtual Device:
   • To upload the Frida Server to your Android device, use the following command:
     sudo adb push frida-server-16.2.1-android-x86 /sdcard
     
     
     
   • If you have more than one device connected, you'll need to specify which one by using the -s option, followed by the device identifier (e.g., emulator-5554):
     sudo adb -s emulator-5554 push frida-server-16.0.2-android-x86 /sdcard
4. Gain Administrative Rights and Execute Frida Server:
   • Now, you must move Frida Server to a suitable directory, change its permissions, and execute it. Start by opening a shell on the device:
     adb shell
     
     
     
   • If you have multiple devices, specify which one as before:
     adb -s emulator-5554 shell
     
     
   • Gain superuser access by typing su and pressing Enter.
     
     Then, execute the following commands one by one:
     
     mv /sdcard/frida-server-16.2.1-android-x86 /data/local/tmp
chmod +x /data/local/tmp/frida-server-16.2.1-android-x86
/data/local/tmp/frida-server-16.2.1-android-x86
     
     
     
     
   • Important: Keep the terminal open after starting the Frida Server. Closing it will stop the Frida Server process.

Extracting Keys with the Dumper​

With Frida Server running on your virtual Android device, you can now use the dumper to extract keys.
This process involves executing a script from the dumper's directory and interacting with a specific web page on your virtual device.

Navigate to the Dumper's Folder:​

• Open Files and go to the folder where you extracted the dumper tool earlier.

Run the Dumper Script:​

• Open a terminal in this directory. Right click into a space and click on "Open in Terminal"
  
• In the terminal, type the following command and press Enter:
  python3 dump_keys.py
  
  
• Keep this terminal open. It's crucial for the dumping process.

At this point, you should have opened two terminals: one running the Frida Server and one executing the dumper script.

Note: If you encounter an error message, "If this call came from a _pb2.py file, your generated code is out of date," it indicates a version compatibility issue with the protobuf package. To resolve this, you may need to downgrade your protobuf package to version 3.20.0. Within the open terminal, using the command pip3 install protobuf==3.20.0. This adjustment ensures compatibility and smooth operation of the dumper script. Repeat the step above with python dump_keys.py.
If you no longer encounter any errors, you are ready to proceed.

Interact with the Web Page:​

• On your virtual Android device, open the Chrome browser. Do not sign in!
• Navigate to the DRM demo page by entering the following URL: https://bitmovin.com/demos/drm
  When asked if you want to play protected video, click Allow/Accept.
• The dumper automatically extracts keys when the page loads, and DRM content processing begins.

Managing the Extracted Keys
After the dumper completes its work, you'll find the extracted keys in a specific directory structure within the dumper's folder:

Locate the Keys:​

• Navigate to the key_dumps folder inside the dumper's directory. The path will look similar to /home/ubuntu/dumper/key_dumps/Androidxxx/xxxx/xxxxxx. The exact path may vary depending on your device and the processed content.

Rename the Key Files:​

• In the final directory, you'll find files named client_id.bin and private_key.pem.
  
  You need to rename these files for further use:
  • Rename client_id.bin to device_client_id_blob.
  • Rename private_key.pem to device_private_key.

This renaming step is essential for the following stages of your work. It ensures the files are correctly identified and utilized by any subsequent processes or tools you will use.


Remember that the extracted L3 keys are sensitive and should not be shared with anyone.
Should you require new keys in the future, simply revisit the section 'Starting Android Studio and Creating a Virtual Device,' provided all the necessary tools remain installed on your system.

This guide was created with special approval, emphasizing its unique contribution to educational purposes.
As such, please understand that this topic will be closed for comments to maintain clarity and focus.

I appreciate your understanding.