Michal Vasko

> It is both updated in the sysrepo as well as the system. What exactly are you talking about, data for the module `ietf-system`? It is not enough to just...

I am confused by the wording of your question. *libnetconf2* implements just the NETCONF communication, the datastore is not included so no data. *netopeer2* in particular reads the data from...

Why do you keep asking about *libnetconf2*? No, there are no data, unless there are callbacks implementing the relevant RPCs (`get` or `get-config`), which is what *netopeer2* does.

Then you can modify the `password` authentication callback to refuse specific users. *netopeer2* uses its own callback so you can modify that, if you are using it.

Sorry, only the `publickey` callback is [being set](https://github.com/CESNET/netopeer2/blob/devel/src/main.c#L593). But you can call [nc_server_ssh_set_passwd_auth_clb()](https://netopeer.liberouter.org/doc/libnetconf2/devel/html/group__server__ssh.html#gafa6fefe02e56b3b881b75f0388fc95f9) with your own callback right after.

No, currently there is no such callback available and the only way to learn that is probably by watching the `sysrepo-monitoring` data as you have correctly found out.

Thanks but Debian scripts were not updated yet based on Fedora RPM review changes. We are hoping to finish RPMs soon and then the Debian scripts and packages will also...

I seem to remember fixing this some time ago, so it should not occur in the latest version.

You will have to find that out yourself, I really have no spare time dissecting all the commits looking for this fix. You can search older issues and you may...

*netopeer2* [ignores](https://github.com/CESNET/netopeer2/blob/devel/src/common.h#L39) NETCONF RPCs not received on a NETCONF session. Not sure if that should change, I would say it makes sense.