dblitt

My use case would be creating one AWS SES or Sendgrid credential that is authorized to sending mail for an entire domain, and then a mail server like mox would then further authorize which users could send emails as who (and probably filter by only allowing the correct email in the From: header for example)

Those password policies only apply to their internal admin panel

> we have increased the minimum password length to 48 characters.

Isn't this complete overkill? I suppose this effectively mandates the use of a password manager, but I wonder where the 48 number came from.

I'd love the ability to send mail through a public SMTP relay, such as Amazon SES or Sendgrid, so the server could be hosted on "untrusted" IP space and send outbound mail through a trusted relay.

> Informed 'best guess' only. > Sources: https://lifearchitect.ai/papers/

Doesn't seem too convincing to me

This is where something like VFSForGit [0] helps out. Instead of cloning the entire repo, it creates a virtual file system and fetches objects on demand. MSFT uses it internally for the Windows source tree (which now exceeds 300GB).

[0]: https://github.com/microsoft/VFSForGit

You can use the PIV functionality of a yubikey to act as a smartcard, and you can log in and sudo authenticate with the yubikey and a PIN.

https://support.yubico.com/hc/en-us/articles/360016649059-Us...

I would assume he's using an intel macbook and wouldn't have the gpu acceleration (and subsequent Vision framework integration) of the m1

A similar issue happens when a laptop (with a bad battery) loses its time and can't connect to 802.1x WPA2 enterprise wifi.

At my high school, we had laptop carts that were notorious for losing their time, and nobody could log in because they were bound to AD over wifi. The system was offline because it would reject the RADIUS certificate of the wifi network due to the time being wrong. We had to manually log in as local admin to change the time or plug them all into ethernet until they could connect to NTP.