On Mon, 2018-10-29 at 18:30 -0700, Yoshimasa Niwa wrote: > > I was thinking of.jist looking it up in a list (of --formentry > > args that were provided on the command line) in the same place your code > > does the keychain lookup. > > I see, like `--formentry password=keychain` to ask Keychain, > `--formentry password=stdin` to select from where it reads each value? No, the --formentry options would contain the field name and the actual answer. For example --formentry main:user=dwmw2 --formentry main:group=foo Using keychain would be a separate option. > > Why the sorting to put user first, btw? Is that mandatory? > > Sort of, because to lookup password in Keychain (or any similar > vaults,) the entries are usually paired with the user name, > (and a few other keys like URL,) it needs to know `user` first. Hm, take a look at the way NetworkManager-openconnect constructs the 'key' for looking up this data. That just uses $FORMNAME:$FIELDNAME in the style I've been using in my examples above.... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20181030/118d9c02/attachment.bin>
