TBK

paxctl has been re-added (https://github.com/alpinelinux/aports/commit/1d3717bebc12493bb9b896db37db728c9d7a661e) on edge, which means it will be available with v3.13. v3.13_rc2 was tagged yesterday (commit https://github.com/alpinelinux/aports/commit/8ed9169257163ccf3f7a927e0ce8e833579f2a76) so it should be released soon™. If for some...

> It would be good if you provide stack traces of all threads. I am uncertain if it is sufficient but I ran `strace ./test_malloc` - https://gitlab.alpinelinux.org/TBK/aports/-/jobs/79038/raw

What kind of SSO do you need? More specifically protocol and provider. Passport would properly be the best option since it has support for 300+ authenticators - http://passportjs.org/docs

Throw LDAP into the mix and you also got local/corp deployments covered.

So to satisfy everybody's needs as well as #72, following packages should suffice? ``` "passport": "^0.3.2", "passport-oauth": "^1.0.0", "passport-ldapauth": "^1.0.0", "passport-facebook": "^2.1.1", "passport-twitter": "^1.0.4", "passport-google-oauth": "^1.0.0" ```

I have made a design concept for the user login:  I got the Facebook and Twitter login buttons from https://dribbble.com/shots/1358062-Social-Login-Buttons, the Google and GitHub I made...

I am not sure how the Settings design should look and the same goes for what happens after the user clicks the "Login with ....." button. Could be: - New...

passport-kerberos I have not had the time to adding passport support as of yet, might be able to do it next week.

nix support should be "relatively easy" with .NET Core 3.0 - https://github.com/dotnet/wpf#status

@pcwizzy37 completely removes vlan with this commit https://github.com/pcwizzy37/aqemu/commit/37d5447126343cc7a70b95c6e73d670be444a05d