Nix 2.93.3
Lix: A modern, delicious implementation of the Nix package manager; unstable internal interfaces
Loading...
Searching...
No Matches
nix::AuthorizationSettings Struct Reference
Inheritance diagram for nix::AuthorizationSettings:
nix::Config nix::AbstractConfig

Additional Inherited Members

Public Types inherited from nix::Config
using Settings = std::map<std::string, SettingData>
Public Member Functions inherited from nix::Config
 Config (StringMap initials={})
bool set (const std::string &name, const std::string &value, const ApplyConfigOptions &options={}) override
void addSetting (AbstractSetting *setting)
void getSettings (std::map< std::string, SettingInfo > &res, bool overriddenOnly=false) override
void resetOverridden () override
JSON toJSON () override
void convertToArgs (Args &args, const std::string &category) override
Public Member Functions inherited from nix::AbstractConfig
void applyConfig (const std::string &contents, const ApplyConfigOptions &options={})
void warnUnknownSettings ()
void reapplyUnknownSettings ()
Protected Member Functions inherited from nix::AbstractConfig
 AbstractConfig (StringMap initials={})
Protected Attributes inherited from nix::AbstractConfig
StringMap unknownSettings

Detailed Description

Settings related to authenticating clients for the Nix daemon.

For pipes we have little good information about the client side, but for Unix domain sockets we do. So currently these options implemented mandatory access control based on user names and group names (looked up and translated to UID/GIDs in the CLI process that runs the code in this file).

No code outside of this file knows about these settings (this is not exposed in a header); all authentication and authorization happens in daemon.cc.


The documentation for this struct was generated from the following file: