From: NdK <ndk...@gm...> - 2018-01-08 17:29:58
|
Il 08/01/2018 08:10, Frank Morgner ha scritto: > If OpenSC is not responsive enough, have you tried enabling file > caching? Uh? The bottleneck is the access to the token... But I didn't know file caching and I'll have to have a look. > Did you disable the card drivers that you don't need? No, I usually have to use OS supplied packages (for long term maintenance). Surely, on a test machine I can experiment with git releases, but for deployment I have to wait for the changes to arrive in the distro. > Instead of using 42 ssh sessions to the same machine, Never said these sessions are to the same machine. It would be useless. It's ~half of a 81 PCs lab. cssh is used to send the same command to all the sessions. Before using cssh, it took 3 days to deploy all the updates on all the machines. With cssh it only takes ~2h. > Complaining doesn't help much for making the situation better, Yup. I stopped complaining-without-trying-to-debug about 30 years ago :) Mine was not intended as a complaint, just as a reminder of a series of "problems" users have to face. > so here are some short hints: Tks. I'll keep 'em handy. > * Using smart cards in a managed environment work quite good (even > with PKCS#11)! Your company just needs a good IT department that > configures everything that's needed. I am one of the most experienced Linux users in our IT team (that's the main reason I can't easily deploy anything compiled from sources: other techs wouldn't be able to maintain it). BYtE, Diego |