[tech] Tech/Wheel Meeting 2023-01-31 18:30 - Two week reminder

[tech-reminder at ucc.asn.au]

Tech/Wheel Meeting Agenda - Tuesday 2023-01-31T18:30
====================================================
- VENUE: UCC Clubroom
  - and online at https://meetings.ucc.asn.au/b/tech

*Meeting opened HH:MM*

## Attendance
- Present
- Apologies
- Absent

## Next meeting
- Schedule next meeting
  - *day 2022-mm-ddTHH:MM
- ACTION: [???] shall be this meeting's secretary! This entails recording minutes for meeting n (beware mid-meeting glitches) and ensuring meeting n+1 reminders succeed:
  - Checklist follows:
    - Clone a new issue from [[https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/32]]
      - Preferably immediately; then reopen it and assign it to yourself
      - This issue is to keep track of any async secretarial duties detailed ahead
      - Type `/clone` into the "Write a comment" box as a "quick action"
      - Update the title to match today's date
  - [ ] ACTION: Save and commit the minutes of today's meeting, during the meeting; and at the end
  - [ ] ACTION: Set and (later) verify reminders of next meeting:
    - [ ] Promptly update `agenda.next` with the TIME/DATE/VENUE
    - [ ] Perform initial curation of `agenda.next`, and move any previous or longstanding action items out of it and into GitLab (see Action Items section below)
    - [ ] Update the crontab: `motsugo# crontab -e`
    - [ ] Check at T-7days that the notice really went out, fix for T-4days if needed
- [ ] Everyone, before next meeting: Curate `agenda.next`, and move any items you think should be tracked as GitLab issues into GitLab issues, as above

## Optional items - choose at the start of the meeting
- [ ] Ethical guidelines
- [ ] Monitoring
- [ ] Backups
- [ ] Password rotations
- [ ] New members
- [ ] Quick check of ChangeLog
- [ ] Lessons learnt

## Current Action Items
### Boilerplate
- Now maintained in GitLab at [[https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/]]
- Briefly discuss anything in here that's worth discussing, but don't spend too long rehashing unresolved issues that have already been discussed ;)
- Going forward:
  - New actions: when new ACTION items arise, put them in the minutes once, but add to GitLab
  - Ongoing actions: don't keep them in the agenda, unless they definitely need to be discussed in the next meeting
  - Completed actions: mention in the agenda that it's been completed, and and briefly discuss if need be

### Action items to discuss

## Known Broken Stuff

## Matters arising previously

## Extra items (rename/refile as appropriate)

- `monnik:/etc/sssd/sssd.conf`
  - `ad_access_filter = (|(memberOf=CN=wheel,OU=Groups,DC=ad,DC=ucc,DC=gu,DC=uwa,DC=edu,DC=au)(primaryGroupID=512))`
  - https://discord.com/channels/264401248676085760/264401248676085760/1041657156371488788
  - https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/81d92bba-d22b-4a8c-908a-554ab29148ab
    - Could have a regular check script: `memberOf: CN=wheel,OU=Groups,DC=ad,DC=ucc,DC=gu,DC=uwa,DC=edu,DC=au` should imply:
      - DOMAIN_ADMINS S-1-5-21-<domain>-512
        - count:25 `gidNumber: 512`
        - count:7 `primaryGroupID: 512`
      - otherwise, and/or as well?: DOMAIN_USERS S-1-5-21-<domain>-513
        - > A global group that includes all users in a domain. When you create a new User object in Active Directory, the user is automatically added to this group.
    - `monnik$ getent group wheel` correctly shows GID 512, from AD

*Meeting closed HH:MM*