search for: subprotocols

On Mon, 6 Jan 2025, Pavol Rusnak via openssh-unix-dev wrote: > Hello list! > > Recently, there was a request to implement CTAP 2.1 resident credential > management to Trezor, a hardware wallet which already supports FIDO2 > authentication (full CTAP 2.0). > > My colleague Andrew[1] raised some points on GitHub and I'd like to check > with you what are we missing or

Hello list! Recently, there was a request to implement CTAP 2.1 resident credential management to Trezor, a hardware wallet which already supports FIDO2 authentication (full CTAP 2.0). My colleague Andrew[1] raised some points on GitHub and I'd like to check with you what are we missing or whether Andrew is right. Thank you for your help and understanding! Quoting from [1]: It really

...> someone give me a few pointers on where to start looking for a cause? Take a test system, and on an isolated network upgrade to a Samba AD DC. If you use Samba 4.2.0, this should then allow password changes. We have just completed a great deal of work on BackupKey, implementing both of the subprotocols, but while it could (I suppose, with non-trivial effort) be made to work in the Samba classic DC, with the secret keys stored in LDAP, that hasn't been done so far, and an AD upgrade will be easier and more reliable. Andrew Bartlett -- Andrew Bartlett http://samba.org/...

https://bugzilla.samba.org/show_bug.cgi?id=5301 Summary: rsync 3.0.0 copyright dates not updated to 2008 Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: michael@usg.edu

Puppet 3.3.1 // CentOS release 6.4 (Final) rpm -qa | grep puppet puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch puppetdb-1.3.0-1.el6.noarch puppet-server-3.1.1-1.el6.noarch puppetdb-terminus-1.3.0-1.el6.noarch Installed from yum packages: Running Transaction Installing : puppetdb-1.3.0-1.el6.noarch

Hi list, we have a problem with users that have personal certificates. When they change their password via the Ctrl-Alt-Del prompt, their personal certificates can no longer be used to authenticate. This happens with Windows 7 Professional joined to a Samba legacy domain. I've tested Samba 4.0.22 and 4.2.0 and they both show the same behaviour. When I leave the domain, and try it with

Hello, I have configured puppet and puppetdb (storeconfig) with postgresql and the service run and the collecting are good for example: I can make query with the next command and responds ok . [.........................] [root@master]# curl -X GET -H ''Accept: application/json'' http://127.0.0.1:8080/v2/facts --data-urlencode ''query=["=", "name",

Greetings, we are trying to setup puppetdb, nut our clients get the following error: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: Failed to submit ''replace facts'' command for lxa7t.unix.lan to PuppetDB at puppetdb:8081: Connection refused - connect(2) Info: Retrieving

I have multiple puppetdb severs pointed at the same database. Would setting gc-interval to 0 disable it on the extra puppetdb nodes? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/4DEyx0IXbLsJ. To post to this group, send email to

PuppetDB is operating fine, but I can''t figure out how to disable it from listening globally on TCP 1099 or 58722 How do I disable them from listening globally without having to resort to iptables? $ lsof -i -n -P | grep java | grep LISTEN java 30115 puppetdb 22u IPv6 119118 0t0 TCP *:1099 (LISTEN) java 30115 puppetdb 23u IPv6 117236 0t0 TCP *:58772

This is a PoC patch for NFSv4/ZFS ACLs. The objective of the patch is that rsync --acls support NFSv4/ZFS ACLs without requiring a new command line option NFSv4 ACLs can't be represented using POSIX draft ACLs, if an NFSv4 ACL is present a separate POSIX draft ACL will not be present and there are new APIs to access NFSv4 ACLs. So we need to distinguish between NFSv4 ACLs and POSIX ACLs in

Hi, first of all, sorry for taking so long. Unfortunately, some other tasks kept coming up. Anyway, attached is the version of the flags patch, that is based on the one I'm using with 2.6.9. It is against the rsync-3.0.0pre9 release. I've included the option name change from the repository, so the option is now called --fileflags. Improved from the previously distributed version is the