Page MenuHomeFreeBSD

Document the need to define WITH_CASPER when using casper services
Needs ReviewPublic

Authored by asomers on Dec 19 2022, 11:31 PM.
Tags
None
Referenced Files
Unknown Object (File)
Jan 29 2024, 9:58 PM
Unknown Object (File)
Dec 31 2023, 1:37 PM
Unknown Object (File)
Dec 20 2023, 8:00 AM
Unknown Object (File)
Nov 4 2023, 4:50 PM
Unknown Object (File)
Oct 31 2023, 12:26 PM
Unknown Object (File)
Oct 23 2023, 3:35 PM
Unknown Object (File)
Oct 3 2023, 4:46 PM
Unknown Object (File)
Sep 29 2023, 4:45 PM
Subscribers

Details

Reviewers
oshogbo
Summary

[skip ci]

MFC after: 1 week
Sponsored by: Axcient

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 48765
Build 45651: arc lint + arc unit

Event Timeline

I think this requires more explanation.
Without this define the casper will work and use standard definition instead of "secure" implementation prepared for capsicum.
This allow to build a tools for FreeBSD without capsicum/casper support - for example for rescue or bootstrap.
Simply putting this define in front of includes will break this behaviour.

I see. Can you suggest better wording, or should I just abandon it and assume that users will figure it out?