lxc-pve_7.0.0-1_amd64.deb compromised?

I expect that you to trust virustotal (since you use it) more than the random strangers from the internet on this forum. If Proxmox did this on purpore then you should not trust their answer either. Do you see anything suspect in those shell code snippets on the virustotal website?

EDIT: Regarding dh_installsystemd: https://man7.org/linux/man-pages/man1/dh_installsystemd.1.html
 
Last edited:
  • Like
Reactions: Johannes S
i dont believe the devs make it on her own :). but only the devs can look into the code if this are right or compromised.
 
It does look like a false-positive to me.

The file that gets flagged is the statically linked init executable of LXC (/usr/bin/init.lxc.static), which can probably trip up some scanners. Unfortunately, there are no details other than "something detected" to know what causes the detection.

If I rebuild the package using today's build env (with Trixie 13.5 as baseline) and on a different machine then the one in the repository was built on, that binary does no longer trip the scanner, despite being the exact same size with just build-id and structure of the binary (offsets/..) changed.
 
  • Like
Reactions: Johannes S, daanw, Carlos Gomes and 1 other person
You must log in or register to reply here.
Top Bottom
Back