pro_grammer@programming.dev to Linux@lemmy.ml · 6 months agoNeofetch development discontinued, repository archivedgithub.comexternal-linkmessage-square71fedilinkarrow-up1394arrow-down12file-textcross-posted to: libre@hexbear.nettechnology@hexbear.netopensource@lemmy.ml
arrow-up1392arrow-down1external-linkNeofetch development discontinued, repository archivedgithub.compro_grammer@programming.dev to Linux@lemmy.ml · 6 months agomessage-square71fedilinkfile-textcross-posted to: libre@hexbear.nettechnology@hexbear.netopensource@lemmy.ml
cross-posted from: https://programming.dev/post/13437386 The author’s profile says this: “Have taken up farming.”
minus-squareOtter@lemmy.calinkfedilinkEnglisharrow-up38arrow-down1·edit-26 months agoIt would need to keep up with future changes and any security updates
minus-squaremoreeni@lemm.eelinkfedilinkarrow-up30arrow-down2·6 months agoWell, it does its job for now. As for the security updates… Isn’t neofetch just a little fancy tool to display data from your system that is already exposed to any process on your distribution? What attack surface does it introduce?
minus-squareOtter@lemmy.calinkfedilinkEnglisharrow-up26·6 months agoGoing by the releases, it didn’t need updates that often, but it still needed updates to fix and ensure compatibility as things changed Security wise, I think you’re right
It would need to keep up with future changes and any security updates
Well, it does its job for now. As for the security updates… Isn’t neofetch just a little fancy tool to display data from your system that is already exposed to any process on your distribution? What attack surface does it introduce?
Going by the releases, it didn’t need updates that often, but it still needed updates to fix and ensure compatibility as things changed
Security wise, I think you’re right