welcome: please sign in

The following 978 words could not be found in the dictionary of 7 words (including 7 LocalSpellingWords) and are highlighted below:
302ing   ability   able   about   Abstraction   accepts   access   accessible   accident   account   achieve   achieved   acl   acls   acquire   action   actions   actual   actually   ad   Adam   Add   add   adding   additional   address   addresses   adequate   Admin   admin   administering   admins   afs   after   again   agent   aimed   Alias   all   allow   already   Also   also   alternative   although   always   am   Ambitious   ambitious   an   And   and   announcing   another   any   anyway   apache   Apache   apache2   app   App   appear   application   applies   approve   approximately   apps   archive   archived   archives   are   arrange   array   as   aspect   associated   assuming   at   At   attribute   auth   available   avoid   away   awkward   back   backlog   backups   Barely   base   based   be   because   become   been   before   begin   behalf   behavior   being   belonged   better   Better   between   bit   blog   blunt   Board   book   books   both   Box   brief   bugzilla   built   Buster   but   But   by   ca   cache   call   can   Can   candidate   cannot   case   Case   Category   center   century   cert   certbot   Certificate   certificate   Certificates   certificates   Certs   certs   cgid   chain   change   changed   changes   check   child   Child   Chlipala   claims   clauses   clear   clearer   client   Clinton   clinton   clunky   cockpit   code   commands   common   comply   config   configuring   consider   construct   constructed   constructs   consuming   Contact   containers   Content   control   convenient   Convert   coop   Coop   copies   corporation   correct   could   course   create   credentials   cron   current   Currently   currently   daemon   data   Data   database   Databases   databases   date   dates   davlockdb   day   days   db   deal   default   Default   Deficiences   defining   definitely   delete   deleted   deletes   deletion   demoncat   depart   destroy   destroying   did   difference   dir   directive   directly   Directory   directory   dirs   display   Do   do   docker   docs   does   Dom   domain   domains   Domtool   domtool   don   done   Done   dot   drop   dues   dump   dumps   dusty   each   Easier   easier   Easiest   easy   Ebadi   ejabberd   eliminate   email   Email   emailing   emails   en   enabled   end   ends   enough   entire   entries   Env   environment   error   especially   etc   even   Even   everyone   everything   example   Example   except   exceptions   exhaustive   exist   existing   expected   Experience   expiration   expire   Expired   explicit   exponentially   export   exported   exposed   expressive   Extend   extending   extension   extern   external   facebook   failing   Fastcgi   fastcgi   fcgi   Fcgid   fcgid   Feature   few   fi   figure   file   files   filesystem   filing   final   Finalize   find   fine   firewall   Firewall   firewalls   first   fix   fixing   fixperms   fleshed   folks   foo   for   forever   forked   formally   formed   freenode   freezing   from   full   function   fwtool   gain   general   General   generalized   generally   generate   generated   get   Get   Give   go   Goals   going   good   google   grab   great   gui   Handler   has   hash   have   haven   having   hcoop   head   hierarchical   hierarchies   hierarchy   High   hoc   hold   Homepage   hook   hooks   hopper   host   hosting   hosts   housekeeping   how   html   http   https   idea   Idea   identical   identified   If   if   ignore   Immediate   immediately   implement   implementation   implemented   implementing   implicit   important   Improve   improved   in   Incidental   include   Including   Index   index   information   initial   inject   insert   Inspecting   Inspiration   Inspire   install   Install   installed   installer   instead   instrument   int   integrates   integration   interchange   interface   intermediate   interpreter   into   io   ip   Ip   ipv4   ipv6   is   it   It   its   join   Journal   journal   just   keep   keeps   kerb   kerberos   keys   Keys   kind   know   lack   lamer   Language   later   latest   launched   launches   launching   laws   lazybastard   lead   least   leaving   Leaving   legally   less   letencrypt   lets   letsencrypt   Letsencrypt   lib   library   like   likely   limitation   limiting   links   list   listing   lists   living   lo   loaded   location   locations   longer   Look   looks   loop   looping   low   Macro   macro   magic   mail   Mail   mailing   Mailman   main   mainly   maintainer   Make   make   makes   making   mam   manage   managed   management   managers   Managing   managing   manual   manually   map   Market   match   matches   Matching   matching   may   maybe   Maybe   me   mediocre   Member   member   members   might   minimal   mix   mod   module   Modules   modules   moinmo   moments   month   months   more   most   Most   mostly   move   Move   multi   multiple   musing   must   My   my   mydomain   mysql   name   named   near   need   Need   needed   Needs   needs   net   Networked   never   new   New   Nextcloud   nice   No   no   node   nodes   non   none   Not   not   notice   now   nowadays   nuke   number   of   off   oh   Old   On   on   once   One   one   only   open   openafs   Openstreetmap   operates   operator   optimization   or   org   other   ought   Our   our   out   outside   overhaul   overkill   overloaded   own   owned   owner   owns   page   pages   Pages   pain   particular   pass   passed   password   passwords   path   pathname   paths   pattern   Pattern   pay   Payment   pem   per   perform   performed   performing   perhaps   Perhaps   period   perm   permission   permissions   Permissions   permitted   perms   personal   Personal   Phone   Place   places   planet   plans   platform   plus   podman   Podman   policy   polluted   polluting   polymorphic   Ponies   pool   popular   Portal   portal   ports   possible   Possible   post   postgresql   pre   preferences   preffered   prefs   primitive   primordial   Priority   priv   privacy   private   privs   pro   probably   Problems   problems   process   processes   product   program   programs   project   prone   prove   provided   provider   providing   Ps   public   punish   purge   purged   purity   purpose   queries   queryable   querying   quite   quotacheck   rate   raw   re   read   really   Record   record   records   recurred   redirect   Reference   refining   register   registered   registry   regular   remember   removal   remove   removing   Replace   replacement   reply   request   requesting   require   required   requires   requiring   restoration   restrict   restricted   retaining   retention   return   rewrites   rid   right   Robin   root   Root   roster   rosters   roundcube   rss   rule   rules   run   running   runs   runtime   safe   same   sandstorm   Sandstorm   script   secretly   section   securely   security   See   seemed   seems   self   sense   sensitive   sentences   separate   serialize   server   servers   services   Set   set   sets   setting   Shiny   shoehorned   short   should   shown   shtml   sidebar   simple   since   Since   single   site   situation   skill   Skip   slightly   sml   so   solution   Solution   some   someone   something   somewhere   soon   sort   source   sources   space   spamassassin   spawned   spawner   special   split   spots   Spring   srv   ssl   standard   started   stash   Statements   stopping   store   stored   storing   string   stringent   Stuff   submission   subtype   suexec   Summer   superusers   support   Supporting   sure   surprising   symlinks   Syntax   syntax   sysadmin   system   tail   takes   target   Tasks   Templeton   term   test   text   than   that   The   the   their   them   themselves   then   theory   There   there   therefore   these   they   things   Things   think   thinking   this   This   those   though   through   Thus   tickets   time   to   To   token   tokens   too   tool   Tool   top   topic   track   tracked   treasurer   Treasurer   triples   trivial   try   Trying   tt   tuples   turned   tweak   type   types   Types   under   understand   unfair   unknown   unknownlamer   unpleasant   unprivileged   unserialize   Unstructured   until   unworkable   up   Updating   upload   us   usable   use   used   Useful   useful   user   userdir   userdirs   username   users   using   vague   val   validity   various   ve   very   vhost   via   vmail   voicemail   volume   volumes   waiting   waklog   want   warn   was   way   We   we   Web   web   webmail   Website   Websites   welcome   well   were   what   What   when   where   which   Which   who   Wiki   wiki   will   willpower   window   Winter   with   without   won   work   working   works   would   wrapped   wrapper   Wrapper   wrapping   wrinkle   write   wsgid   www   you   your   zero  

Clear message


I am Clinton Ebadi. I am the Treasurer of the coop (someone has to do it), and the current lead sysadmin / DomTool maintainer / lo-fi AdamChlipala replacement.

1. Board Statements

See /BoardStatements

2. General Coop Goals

Unstructured musing on when/what I think the coop ought to be.

3. Contact

4. Websites

5. Immediate Tasks

5.1. High Priority Tasks

6. Admin Stuff

6.1. Improve SSL Experience

6.1.1. Domtool

Replace use_cert cert function that just takes the final name instead of the full pathname, providing the full pathname is kind of clunky.

extern type your_cert;
extern val cert : your_cert -> ssl
(* SSL = cert "mydomain.pem"; *)

We also need to support letencrypt, perhaps like so:

extern type your_letsencrypt_cert;
extern val letsencrypt : your_letsencrypt_cert -> ssl
(* SSL = letsencrypt "my.domain"; *)

Which would find the certs in the standard location used by certbot... or we could use symlinks there from our location.

6.1.2. Portal

We should allow submission of certs / keys through the web interface. Can use an insert-only afs dir to securely allow hcoop.daemon to write certs without being able to access them, which would then be installed manually by an admin using ca-install.

The portal request page should display all certs a user is permitted to use already, their common name, and their expiration date.

6.1.3. Managing Certificates

Needs Updating Not very fleshed out, also does not consider how we're going to manage letsencrypt certs

Since we no longer need to support explicit intermediate certs (everything nowadays accepts the chain in the main certificate file), we can just use domtool's cert permission to track things.

A cron should check for things like:

Certificate CN and validity dates should be shown on the portal ssl page; ssl check cron should cache this somewhere the portal can read it.

destroy-user needs to nuke certs for leaving members ... we need to overhaul this generally and stash all member data in one location when destroying for later removal / restoration (if they return in the 30 day deletion window).

6.1.4. Managing Member Data Better

Trying to hash out how we can better manage user data when they depart; right now we reply on someone (me...) to go in 30 days after removing a member to remove all of their non-afs data manually, which is prone to error and needs to be managed better if we want to comply with things like GDPR (although I don't think it applies to us directly as a US corporation, it would be nice to do so since we really don't want to be retaining data longer than needed anyway, and the US will likely have stringent privacy laws aimed at facebook/google that will punish all the same for failing to remove data immediately too...).

Not personal data, but things we should clear for housekeeping in general:

We already manage mail and $HOME data fine, both are easy to clear (delete the volumes, done).

One aspect of the solution I've been thinking about that would also make it easier for members to export their data in general: we could set up a backups.$user volume, and store dumps of data we hold on behalf of the data there: database backups, mailing list archives, an exported dump of their ejabberd roster, maybe even copies of their ssl certs.

We also need a registry of data we keep on behalf of members that can't immediately be identified based on their username: at least ssl certs and mailing lists (those might be it though... and certs are already tracked with domtool perms so maybe just adding a "list" perm would be adequate, which could then be used to maybe allow members to perform some list management through a domtool program). And we need to store things like domtool permissions when destroying (might be able to achieve some of this by first freezing members before removing them), so that we can use them later when performing the final purge of data after the retention period ends (important to keep a brief retention period for those "oh right, I have to actually pay dues" moments...).

6.2. etc.

6.3. Website

(create Website bugzilla product and move these there)

6.3.1. Wiki

6.4. domtool plans

6.4.1. restricted modules for apache

Inspiration: hcoop.net's vhost is non generated by domtool, and only because it enabled mod_userdir

Idea: have a set of restricted modules that can only be used by superusers. Easiest to just have another ad-hoc list setting in config for domtool. ACL example: hcoop priv www, www priv overloaded to also allow use of restricted module.

Problems: no way currently to restrict access to actions or lib files.

Deficiences: priv www is a blunt instrument. priv system in general is mediocre. It might be nice to be able to do something like hcoop priv www apache-module/userdir mail/hopper.hcoop.net (i.e. access to all www nodes, access to the userdir module only, access to hopper). Keys gain some hierarchy polluting the purity of the triples db, but it is already a bit polluted... is there any difference between adding hierarchy to priv keys and the existing implicit hierarchies in domains and paths?

Solution: might be overkill just for mod_userdir, if it looks like minimal additional code is required perhaps implement hierarchical privs (extending www and mail privs to support limiting to particular admin hosts) and restricted apache modules.

6.4.2. Pattern Matching and New Types

A vague idea that may prove to be unworkable. I think at least implementing list matching in domtool would be quite useful. Abstraction syntax would be need to be improved to support multiple clauses. case would also be needed to make it useful. Syntax would be easy enough to add except for having to deal with runtime non-exhaustive match exceptions (perhaps requiring exhaustive matches and living with the limitation). Ambitious, probably time consuming, might require adding tail call optimization to the interpreter. Example:

(* A map operator *)
val map = \action -> \list -> 
  case list of head::tail =>
      action head;
      map action tail;
     | [] => Skip;
(* Alias a list of email addresses to *)
val multiAlias = \sources -> \target -> map (\source -> emailAlias source target) sources;

I probably lack the skill/willpower in the short term... alternative idea, just implement a loop primitive in SML and magic the types away by making it a primitive construct (defining its type on DomTool/LanguageReference). Maybe implement polymorphic actions if adding then is secretly easy:

extern val map : (('a -> 'b) -> ['a]) -> [^Root];

(* Alias a list of email addresses to *)
val multiAlias = \sources -> \target -> map (\source -> emailAlias source target) sources;

Most of the gain, none of the pain.

New types: even more ambitious. Supporting at least tuples or named records, and perhaps a construct for querying the domtool acl database. Idea would be to use it for something like the firewall, where only primitive "generate one firewall rule" constructs would be needed, and then user firewalls could be constructed by querying the ports available to each user and matching/looping.

One pattern that has recurred in domtool is that of a special purpose client + server commands that operates on a simple database. E.g. spamassassin prefs, vmail users, firewall rules, and the domtool acl database. It would be useful to have a generalized serialize/unserialize sets of sml records library, perhaps with a generalized/queryable tuples database built on top of the primitive raw-records database. Even better would be to allow databases to be exposed to domtool, and simple queries performed on them. Maybe.

val writeRecord' : [('record -> 

6.4.3. ip / ipv4 / ipv6

There are a few places (mostly apache) where it would be great to be able to interchange ip and ipv6 addresses. But there's no way to subtype in domtool (except for refining base int and string).

It's been shoehorned in for now (always requiring a node to have an ipv6 address), but this can be a bit awkward (e.g. webAtIp requires that an ipv4 and ipv6 address be provided).

Also might make sense to be able to pass an array of IPs in a few spots instead of just fixing it at one ipv4 and one ipv6 address per WebPlace. you can just pass more than one WebPlace already.

7. Things to Look At

7.1. Easier App Install

We should probably figure out how we can support docker containers because they are popular and there is no stopping them (plus maybe they are a bit convenient). Podman in theory works on Debian Buster and might even run in afs (I did one test and it seemed to)... but mainly it lets users run containers as themselves without need a daemon running as root and zero security.

8. Board Stuff

9. etc

Barely formed sentences.

9.1. tt-rss at hcoop

Our postgresql does not use passwords. The installer needs a single tweak to remove the required attribute of the database password to install.

9.2. Fastcgi Problems with openafs

Old Content: This section is from before fastcgi was implemented. Leaving so I might remember one day to try the idea of adding an suexec hook to apache.

The mod_fcgid spawner runs in its own process pool and therefore without tokens or the ability to acquire tokens for processes it launches. Thus, all fcgi processes must be wrapped to avoid surprising behavior. The FcgidWrapper directive is not very expressive: the "wrapper" is the fastcgi application that is launched and then passed any files matching the extension using SCRIPT_NAME. A wrapper wrapping script is needed to grab tokens before launching the actual wrapper, and just using {Add,Set}Handler fcgid-script won't work as expected (users could of course arrange for programs run that way to grab tokens manually).

mod_wsgid and mod_cgid have identical problems. Inspecting the apache source code makes it appear that it would be possible to fix the situation generally by adding a pre/post suexec hook. The process managers for mod_cgid/mod_fcgid/mod_wsgid are forked from the primordial apache process which I understand has all modules loaded. Modules like mod_auth_kerb and mod_waklog could then inject tickets/tokens/etc. into the environment from which external processes were spawned using the suexec hooks.


ClintonEbadi (last edited 2020-07-23 05:11:47 by ClintonEbadi)