Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- W: http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu/dists/noble/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. W: https://ppa.launchpadcontent.net/openshot.developers/ppa/ubuntu/dists/jammy/InRelease: Signature by key FBA0C227099A5360635E3D9152165BD6B9BA26FA uses weak algorithm (rsa1024) W: https://ppa.launchpadcontent.net/ubuntu-toolchain-r/test/ubuntu/dists/jammy/InRelease: Signature by key 60C317803A41BA51845E371A1E9377A2BA9EF27F uses weak algorithm (rsa1024)
- ###### ChatGPT said:
- ChatGPT
- These warnings from `apt` indicate issues with the repository keys used for verification:
- 1. **Legacy Keyring (`trusted.gpg`)**
- - The key for `kelebek333/kablosuz` is stored in the deprecated `/etc/apt/trusted.gpg` keyring.
- - Solution: Move the key to `/etc/apt/trusted.gpg.d/` or use `gpg` with `signed-by` in the `.list` file.
- 2. **Weak Signature Algorithm (RSA 1024-bit)**
- - The keys for `openshot.developers` and `ubuntu-toolchain-r/test` use RSA 1024-bit, which is considered weak.
- - Solution: Contact the PPA maintainers to update their key to at least RSA 2048-bit.
- - Workaround: You can still use these PPAs, but it's recommended to avoid weakly signed repositories.
- To fix the legacy keyring warning for `kelebek333/kablosuz`:
- bash
- CopyEdit
- `sudo mkdir -p /etc/apt/keyrings sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/kelebek333.gpg --recv-keys <KEY_ID> echo "deb [signed-by=/etc/apt/keyrings/kelebek333.gpg] http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu noble main" | sudo tee /etc/apt/sources.list.d/kelebek333.list sudo apt update`
- Replace `<KEY_ID>` with the actual key ID.
- For the weak RSA keys, you can report the issue to the PPA maintainers or consider alternative sources.
- 4o
- ##### You said:
- sudo apt-key list Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). /etc/apt/trusted.gpg -------------------- pub rsa4096 2019-10-14 \[SC\] F30D 3DBF B753 4F67 0B44 C719 23E5 0C67 0722 A6D9 uid \[ unknown\] Launchpad PPA for Butterfly
- ###### ChatGPT said:
- ChatGPT
- The warning indicates that `apt-key` is deprecated and advises managing repository keys in `/etc/apt/trusted.gpg.d/`. The key you listed (`F30D 3DBF B753 4F67 0B44 C719 23E5 0C67 0722 A6D9`) is stored in the legacy `/etc/apt/trusted.gpg`, which is discouraged.
- ### **Fixing the Issue**
- To move this key to the new keyring format:
- 1. **Export the Key to a File**
- bash
- CopyEdit
- `sudo apt-key export 0722A6D9 | sudo tee /etc/apt/trusted.gpg.d/butterfly.gpg > /dev/null`
- _(Replace `0722A6D9` with the last 8 digits of the key if needed.)_
- 2. **Verify the New Location**
- bash
- CopyEdit
- `ls -l /etc/apt/trusted.gpg.d/`
- 3. **Remove the Old Key from `trusted.gpg`**
- bash
- CopyEdit
- `sudo apt-key del 0722A6D9`
- 4. **Update APT**
- bash
- CopyEdit
- `sudo apt update`
- This ensures that the key is stored correctly without relying on the deprecated `trusted.gpg`. Let me know if you need further assistance!
- 4o
- ##### You said:
- W: The key(s) in the keyring /etc/apt/trusted.gpg.d/butterfly.gpg are ignored as the file has an unsupported filetype.
- ###### ChatGPT said:
- ChatGPT
- The error occurs because `apt` expects keys in `/etc/apt/trusted.gpg.d/` to be in binary (GPG) format, but `apt-key export` generates an ASCII-armored key, which is not supported.
- ### **Fixing the Issue**
- Instead of using `apt-key`, use `gpg` directly:
- 1. **Create the Keyring Directory (if it doesn't exist)**
- bash
- CopyEdit
- `sudo mkdir -p /etc/apt/keyrings`
- 2. **Export and Convert the Key Properly**
- bash
- CopyEdit
- `sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/butterfly.gpg --recv-keys 0722A6D9 sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/butterfly.gpg --export > /etc/apt/keyrings/butterfly.gpg`
- 3. **Update the Repository List** Modify the `.list` file referencing this key (e.g., `/etc/apt/sources.list.d/butterfly.list`) to include:
- bash
- CopyEdit
- `deb [signed-by=/etc/apt/keyrings/butterfly.gpg] http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu noble main`
- 4. **Update APT**
- bash
- CopyEdit
- `sudo apt update`
- ### **Explanation**
- - `apt` expects keys in `/etc/apt/keyrings/` in binary format.
- - The `signed-by=` directive ensures that only this key is used for verifying the repo.
- Let me know if you run into any issues!
- 4o
- ##### You said:
- Err:8 http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu noble InRelease The following signatures couldn't be verified because the public key is not available: NO\_PUBKEY 23E50C670722A6D9 Reading package lists... Done Building dependency tree... Done Reading state information... Done 401 packages can be upgraded. Run 'apt list --upgradable' to see them. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu noble InRelease: The following signatures couldn't be verified because the public key is not available: NO\_PUBKEY 23E50C670722A6D9
- ###### ChatGPT said:
- ChatGPT
- The error occurs because APT cannot find the public key (`23E50C670722A6D9`) for the `kelebek333/kablosuz` PPA. You need to manually add the key and update your sources.
- ### **Fixing the Issue**
- #### **1\. Remove Old Key (if present)**
- bash
- CopyEdit
- `sudo rm -f /etc/apt/trusted.gpg.d/butterfly.gpg sudo rm -f /etc/apt/keyrings/kelebek333.gpg`
- #### **2\. Import the Correct Key**
- Use `gpg` to fetch and store the key in the correct format:
- bash
- CopyEdit
- `sudo mkdir -p /etc/apt/keyrings sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/kelebek333.gpg --recv-keys 23E50C670722A6D9 sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/kelebek333.gpg --export > /etc/apt/keyrings/kelebek333.gpg`
- #### **3\. Update the Repository Source**
- Ensure the PPA entry in `/etc/apt/sources.list.d/kelebek333.list` (or equivalent) is formatted correctly:
- bash
- CopyEdit
- `deb [signed-by=/etc/apt/keyrings/kelebek333.gpg] http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu noble main`
- #### **4\. Update APT**
- bash
- CopyEdit
- `sudo apt update`
- ### **Alternative Method (Using `wget`)**
- If the above fails, try fetching the key manually:
- bash
- CopyEdit
- `sudo mkdir -p /etc/apt/keyrings wget -qO - "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x23E50C670722A6D9" | sudo tee /etc/apt/keyrings/kelebek333.gpg > /dev/null`
- Then, verify the repository again:
- bash
- CopyEdit
- `sudo apt update`
- Let me know if you encounter further issues! 🚀
- 4o
- ##### You said:
- sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/kelebek333.gpg --recv-keys 23E50C670722A6D9 gpg: keybox '/etc/apt/keyrings/kelebek333.gpg' created gpg: keyserver receive failed: No data owner@roamtop:~$ sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/kelebek333.gpg --export > /etc/apt/keyrings/kelebek333.gpg bash: /etc/apt/keyrings/kelebek333.gpg: Permission denied owner@roamtop:~$ sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/kelebek333.gpg --export | sudo tee /etc/apt/keyrings/kelebek333.gpg gpg: WARNING: nothing exported
- ###### ChatGPT said:
- ChatGPT
- The issue arises because the keyserver query is returning no data. This can happen for several reasons, including an outdated key, a deprecated keyserver, or a missing key.
- ### **Solution: Manually Download and Add the Key**
- Since the automatic method isn't working, let's try manually downloading and adding the key.
- #### **1\. Check if the Key Exists on Ubuntu Keyserver**
- Run:
- bash
- CopyEdit
- `wget -qO - "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x23E50C670722A6D9"`
- If this returns an error or no key data, the key may no longer be available.
- #### **2\. Try Manually Adding the Key**
- If the above command works, then add the key using:
- bash
- CopyEdit
- `wget -qO - "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x23E50C670722A6D9" | sudo tee /etc/apt/keyrings/kelebek333.gpg > /dev/null`
- #### **3\. Update APT Sources**
- Ensure the PPA is configured correctly in `/etc/apt/sources.list.d/kelebek333.list`:
- bash
- CopyEdit
- `deb [signed-by=/etc/apt/keyrings/kelebek333.gpg] http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu noble main`
- #### **4\. Update APT**
- bash
- CopyEdit
- `sudo apt update`
- ---
- ### **If the Key is No Longer Available**
- If `wget` also fails to retrieve the key, then:
- 1. **The key might be removed or the PPA is no longer maintained.**
- 2. **Check the PPA's official page:**
- - Visit: https://launchpad.net/~kelebek333/+archive/ubuntu/kablosuz
- - Look for any updates or alternative key instructions.
- Would you like me to check the PPA status for you? 🚀
- 4o
- ##### You said:
- It downloaded and the plaintext keyfile is at /etc/apt/keyrings/kelebek333.gpg but apt update says: 401 packages can be upgraded. Run 'apt list --upgradable' to see them. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu noble InRelease: The following signatures couldn't be verified because the public key is not available: NO\_PUBKEY 23E50C670722A6D9
- ###### ChatGPT said:
- ChatGPT
- The issue is likely that `apt` requires the key to be in **binary GPG format**, but it seems to be in **ASCII-armored format** (plaintext). Let's fix this by converting the key properly.
- ---
- ### **Fix: Convert the Key to Binary Format**
- Run the following commands:
- 1. **Remove the existing key (since it's ASCII-armored)**
- bash
- CopyEdit
- `sudo rm -f /etc/apt/keyrings/kelebek333.gpg`
- 2. **Re-download and properly import the key as a binary file**
- bash
- CopyEdit
- `wget -qO - "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x23E50C670722A6D9" | gpg --dearmor | sudo tee /etc/apt/keyrings/kelebek333.gpg > /dev/null`
- 3. **Ensure correct permissions**
- bash
- CopyEdit
- `sudo chmod 644 /etc/apt/keyrings/kelebek333.gpg`
- 4. **Verify that the key is now in binary format**
- bash
- CopyEdit
- `file /etc/apt/keyrings/kelebek333.gpg`
- It should return something like:
- vbnet
- CopyEdit
- `/etc/apt/keyrings/kelebek333.gpg: GPG key public ring, created <date>`
- 5. **Modify the APT source list (if needed)** Ensure the file `/etc/apt/sources.list.d/kelebek333.list` contains:
- bash
- CopyEdit
- `deb [signed-by=/etc/apt/keyrings/kelebek333.gpg] http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu noble main`
- 6. **Update APT**
- bash
- CopyEdit
- `sudo apt update`
- ---
- ### **Why This Works**
- - `apt` does **not** support plaintext GPG keys.
- - `gpg --dearmor` converts the key into a **binary format** (`.gpg`), which `apt` recognizes.
- - The `signed-by=` option ensures only the specific key is used for this repository.
- After running these steps, `sudo apt update` should work without errors. Let me know if you need further assistance! 🚀
Advertisement
Add Comment
Please, Sign In to add comment