View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008587 | Kali Linux | Kali Package Improvement | public | 2024-01-10 23:18 | 2024-01-18 08:19 |
Reporter | ggbce | Assigned To | arnaudr | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | assigned | Resolution | open | ||
Summary | 0008587: 50unattended-upgrades file is not set with working default values for Kali | ||||
Description | If we install APT package "unatteded-upgrades" or try to configure it with default values with dkpg-reconfigure "unattended-upgrades", the generated file in /etc/apt/apt.conf.d/50unattended-upgraded is not valid to work with kali-rolling. He's set with Debian default information for an original Debian distribution. The origin pattern for uncommented lines is (all lines are wrong also...): Unattended-Upgrade::Origins-Pattern { If I refer to "apt-cache policy" for a working (valid) values in origin pattern on kali-rolling machine, it should be: "origin=Kali,codename=${distro_codename}"; | ||||
Correct me if I'm wrong, but Kali is a rolling distro, there's not security repo, there's only the kali-rolling suite. So unattended-upgrades is not for Kali. What did you want to achieve with unattended-upgrades? |
|
No. Unattented-upgrades are to keep updated all packages via APT, even for security reason or for improve reasons. It make automatically same thing than using manually apt-get upgrade or apt-get full-upgrade. It's not because Kali is a "Security distro" that you don't need to keep it up to date ;) And always take a look manually for updates is not very useful in many situations. Anyway, I just inform the precompiled package with 50unattented-upgrades file doesn't fit what expected to work as-is for Kali on Kali, it seem to be ported from Debian directly without adjusting parameters. |
|
It's not about keeping the system up-to-date yes/no, it's about doing so unattended. The primary use-case for unattended-upgrades is a stable distribution, most likely running on a server. This is because a stable release only receives targeted updates, either security fixes, or bug fixes for bugs that were considered important enough to be fixed. In this context, it's safe enough to upgrade the system automatically, without human validation: it's unlikely to break things, and in any case, the upside of applying security fixes asap outweighs the risk of breaking something. Now, a rolling distro? For a rolling distro I strongly advise NOT to update it with unattended upgrades, sooner or later it might break your system. For a rolling distro, I'd recommend attending uprades: user decide to upgrade, check the output of apt, and hit Enters only if everything looks good. Now, of course you do what you want with your system, and if unattended-upgrades works great for you and your Kali install, all the best.
Yep indeed, the package comes from Debian unmodified. If you get it to work for Kali, please share your config here, and I'll include it in Kali so that other users can benefit. |
|
Like I already wrote: Basically the default current configuration in 50unattended-upgrades file under Origin-Pattern should be something like that: Unattended-Upgrade::Origins-Pattern { The manual solution I found for the moment is to edit the file to put in comment or remove all lines containing "origin=Debian,... or o=Debian,...", then and add this: Unattended-Upgrade::Origins-Pattern { To keep updated all packages provided from Kali repositories. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2024-01-10 23:18 | ggbce | New Issue | |
2024-01-11 08:54 | arnaudr | Note Added: 0018780 | |
2024-01-11 08:54 | arnaudr | Note Edited: 0018780 | |
2024-01-11 12:50 | ggbce | Note Added: 0018781 | |
2024-01-12 02:12 | arnaudr | Note Added: 0018783 | |
2024-01-17 18:35 | ggbce | Note Added: 0018801 | |
2024-01-18 08:19 | daniruiz | Assigned To | => arnaudr |
2024-01-18 08:19 | daniruiz | Status | new => assigned |