Release Meeting Minutes/2010-05-04
Zhanna Tsitkova, Greg Hudson, Tom Yu, Will Fiveash, Sam Hartman, Robert Relyea
alternative implementations of single functionality vs implementations of multiple functionalities?
- static plugin needs a config file?
- Good to have more [pluggable] infrastructures. Want uniform way of specifying configuration (for plugins)... want some explanation of "factory". Why is it called "factory"? Why do you want groupings? Want better separation of configuration vs headers. OK to use krb5 config stuff for GSS mechglue. Approach as described by Zhanna is problematic for Debian... can't package using a single config file. Undesirable to require configuration for static plugins [built-in modules]. Service vs listener distinction seems intrinsic to code [interface?], and shouldn't be in the config. Are multiple plugin managers really needed?
- ...embedded situation: might want to interoperate, allow applications to control how plugins are loaded.
- Talk to TeamF1 or Mark Eichin. RFID [...] do their own build of some Linuxes, lightly customized.
- ...programatically alter configs. Shawn Emery is more directly involved with the people requesting pluggable config. [Zhanna?] Didn't explicitly state MT-safety... a general concern about plugins. Take care of shape plugin interfaces take so to make it easier to be MT-safe.
- Concerns about hash validation concept: why not make it the problem of the OS?
- (void*)? type safety. [use pointers to incomplete structs instead]. Problems with scanning a directory for modules. OpenSSL being loaded by a Kerberos app loading pkinit, but application independently uses OpenSSL... crash.
- That is partly due to global state in OpenSSL [RTLD_GROUP, etc. don't save you because that is a name resolution thing, not total runtime isolation]
[Is automatic enable the right default?]
- Carefully consider how it interacts with init_secure.