Summary: | security/step-certificates | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Vincent Bentley <vince> |
Component: | Individual Port(s) | Assignee: | Vladimir Druzenko <vvd> |
Status: | In Progress --- | ||
Severity: | Affects Some People | CC: | mw, vvd |
Priority: | --- | Keywords: | easy |
Version: | Latest | Flags: | bugzilla:
maintainer-feedback?
(mw) |
Hardware: | Any | ||
OS: | Any |
Description
Vincent Bentley
2024-11-08 17:36:47 UTC
I think I can fix this without having to wait for maintainer approval. Check security/step-certificates/files/step-ca.in: name="step_ca" rcvar="step_ca_enable" Are you sure "service step_ca configure" is incorrect? IMHO, better to rename security/step-certificates/files/step-ca.in to security/step-certificates/files/step_ca.in and in Makefile "USE_RC_SUBR=step_ca". I changed my mind - waiting maintainer. Personally I don't have a preference between '-' and '_'. However, I do prefer accurate instructions. Which is why I raised this issue as a typo for the instructions and not as a bug with the service itself. I am not a FreeBSD package maintainer, so I am not familiar with FreeBSD packaging standards. Doing a search on services on the host, it already has a mix of services with hyphens and underscores. If underscores in service names are a standard to be followed by package maintainers, there will be more services to fix, ftp-proxy and os-release being two of them. # service -l | grep -e '-' -e '_' ftp-proxy growfs_fstab hostid_save ipfw_netflow ipropd_master ipropd_slave local_unbound os-release power_profile rfcomm_pppd_server static_arp static_ndp sysctl_lastload var_run wpa_supplicant step-ca If underscores replacing hyphens is a FreeBSD packaging standard, perhaps this should be added to the linting process of packages. (In reply to Vladimir Druzenko from comment #2) Hi, thanks for bringing the issue up. I agree, that there is an inconsistency. I remember that there were some issues with the - or _ when I built that. I would propose to have a look and if it can be fixed in a meaningful way. I think though, that I have to be careful with this not breaking things and especially keep it stable/reliable for people already it in order to not break their scripts/settings etc. service(8) takes the name of the rc.d script as a parameter. So if the script is named step-ca, the command should be "service step-ca *". The script can check the "step_ca_enable" variable instead of "step-ca_enable". But how should the "service step-ca enable" command work? Can you test this command. I don't have this software installed. |