Skip to content

Conversation

@nbarbier-265
Copy link

The daemonize crate is unmaintained and has a security advisory (RUSTSEC-2025-0069). This switches to cf-daemonize, a Cloudflare fork with the same API.

Changes:

  • Update Cargo.toml to use cf-daemonize 0.3.0
  • Update import from daemonize to cf_daemonize
  • Remove Stdio::keep() calls (not available in cf-daemonize 0.3.0)
    Daemon preserves stdio by default when not explicitly configured

Fixes #699

Note: cf-daemonize has future incompatibility warnings. Maintainers may want to consider alternatives like daemonize-me or implementing a custom solution.

The daemonize crate is unmaintained and has a security advisory
(RUSTSEC-2025-0069). This switches to cf-daemonize, a Cloudflare fork
with the same API.

Changes:
- Update Cargo.toml to use cf-daemonize 0.3.0
- Update import from daemonize to cf_daemonize
- Remove Stdio::keep() calls (not available in cf-daemonize 0.3.0)
  Daemon preserves stdio by default when not explicitly configured

Fixes cloudflare#699
@drcaramelsyrup
Copy link
Collaborator

Note the cf_daemonize crate at this point looks like an old fork that may also be unmaintained at this point. I think I'm more concerned about switching over to that crate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RUSTSEC-2025-0069: daemonize is Unmaintained

2 participants