A while back I was developing a workflow scheduler. However the run duration kept coming back negative. The runs kept finishing like 15 seconds before they started. Eventually I figured out why; the company had configured a policy to use their custom NTP server, but it was 16.7 seconds off. So my Windows laptop’s time was in the future, but the WSL VM (which ran the program) used another NTP server and was correct. In the end I just added a bodge that made the program request the time from an external server on startup to calculate an offset.

  • carrylex@lemmy.world
    link
    fedilink
    arrow-up
    15
    ·
    1 day ago

    IT department really wanted to use their snake oil antivirus enterprise super secure hackproof™ software everywhere.

    So it was installed on the CI servers.

    Fastforward a few months and we were wondering why one build agent was no longer picking up jobs.

    After a day of debugging we found out that a certain snake oil sofware tampered with a single machine internal TCP conncetion and somehow fucked it up in a way that all packets in one direction just vanished.

    Disabling the snake oil software magically fixed the problem.

    • HamsterRage@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      23 hours ago

      Should a CI server even have access to the Internet and need antivirus software? Maven access I guess.

      • bss03@infosec.pub
        link
        fedilink
        English
        arrow-up
        3
        ·
        20 hours ago

        It is good to have a build method that doesn’t require network access; at one time that used to be required for Debian builds. However, for a variety of reasons, most CI servers do have access to the network, even if there’s a firewall (or NAT) between them and the Internet.