• 0 Posts
  • 855 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle




  • I’m also old and use iptables at server level as well.

    But network perimeter here is the server perimeter, not the network (e.g. router).

    Most ppl in my profession would not assume a host’s net controls as “network perimeter”, so I’m not sure what your context is there.

    Just because you know how things work, doesnt mean everyone does.

    Yeah, fair. But by the same token, we still have to chime in when these terms are thrown around and offered to newer homelabbers. And there is a lot of free security “advice” in these sub’s from folks who have a weak understanding of any of it.


  • Those are considered firmware, yes. And these can vary in their installation as being updated via the firmware interface itself or some other update mechanism.

    Some firmwares like on certain IBM thinkpads, my surface pro 6 and others can be updated directly via a Linux command called fwupd, but the firmwares must live in specifics public repositories.

    This news means we’ll all have a much better time using fwupd to update these on dell and lenovo machines, but the firmwares themselves will remain proprietary blobs.

    Coreboot replaces the bios/firmware altogether, and it’s not an easy task to get new ones, unfortunately.










  • non_burglar@lemmy.worldtoSelfhosted@lemmy.worldRemote Code Execution in Forgejo?
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    3
    ·
    edit-2
    13 days ago

    I understand what you’re saying, but Forgejo has an outdated and made-up-from-thin-air policy. From their security.md:

    • You MUST disclose vulns to the author (why are we dictating instead of inviting participation)
    • emails about vulns MUST be encrypted (I don’t even understand this one, this gives really strong “we don’t know how email works” vibes)

    And it just goes on, like someone from 2003 wrote that policy.

    Now, I’m going to agree with you that it’s a bit of a dick move to do the carrot dangle thing, but some vendors/devs just don’t respond without the pressure. And forgejo has been forced by github supporters to implement a security policy after trying to ignore it.

    It seems that the author has some ongoing interactions with forgejo, and it would be great if these were disclosed in the article, but forgejo seems to need a kick in the pants, especially over an RCE, the forbidden sev 10 of vulns.