metasploit-framework icon indicating copy to clipboard operation
metasploit-framework copied to clipboard

update DEPRECATION

Open sec13b opened this issue 1 year ago • 2 comments

you can permanently resolve this DEPRECATION in the DEPRECATION section of apt-key(8) for details.

google it for solution , save problem

ubuntu@sakerhet:~/jet$ sudo apt update -y Hit:1 http://downloads.metasploit.com/data/releases/metasploit-framework/apt lucid InRelease Hit:2 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. W: http://downloads.metasploit.com/data/releases/metasploit-framework/apt/dists/lucid/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. ubuntu@sakerhet:~/jet$

sec13b avatar Mar 10 '24 16:03 sec13b

──(root㉿kali)-[~] └─# ./msfinstall Adding metasploit-framework to your repository list..Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). OK Updating package cache..W: http://downloads.metasploit.com/data/releases/metasploit-framework/apt/dists/lucid/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. OK Checking for and installing update.. Reading package lists... Done

sec13b avatar Mar 11 '24 17:03 sec13b

Fix suggested here: https://github.com/rapid7/metasploit-omnibus/pull/192

nrathaus avatar Mar 27 '24 19:03 nrathaus

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

github-actions[bot] avatar Apr 29 '24 15:04 github-actions[bot]