Jarl Gullberg

I've long since moved on from using Discord.NET at all, so I no longer have a dog in the race.

It's working fine on my end. Can you clarify what the issue is?

Are there any plans to revisit this? Having Kerberos support is quite important for single sign-on, especially in an LDAP/FreeIPA environment where external SSO alternatives are relatively limited.

Yeah, I just updated the mask so that the 940 card I had passed (enabling the bits that differed). I don't have any other IDPrime cards to test with, so...

I'm also encountering this bug in both 4.2.1 and 4.2.2 - not in 4.1.1, however, so it appears to be some type of regression.

I started having the same issue on my machine all of a sudden - everything worked perfectly fine beforehand, and something happened between a week ago and now that broke...

Factory reset changed nothing, unfortunately, so it's definitely controller-side. The error is exactly the same as the error I get when trying to connect to a dead IP address, too,...

This remains an isssue for me, and it seems the aos_switch collection is also experiencing the same fault: https://github.com/aruba/aos-switch-ansible-collection/issues/85

While testing again, I noticed that my smartcard reader that contains my SSH key does not light up when attempting to run the playbook, suggesting Ansible isn't trying to use...

I'm also having this problem with hippmocks 5.0 and valgrind 3.18 on Ubuntu 22.04. Same general issue, but showing up when mocking libsodium functions and running with valgrind - non-valgrind...