5/25/2023 0 Comments Pwsafe plk![]() It won't support entering the passphrase on the command-line due to security concerns: it would probably get logged in shell history, be visible in ps output and could be visible in a scrollable terminal window. Other mechanisms for safe password inputįor all operations that require a passphrase, pwsafe-cli would read it by turning terminal echo off. Everything below this line is To-Be-Implemented 3. yes suppresses the "yes, no, no-to-all, yes-to-all, quit, abort" prompt before making each change. The entries selected for merging can be restricted, but NOT the fields. Merge `pwsafe-cli mysafe.psafe3 -merge=othersafe.psafe3 ] -yes` Fields selected for sync'ing and the fields sync'ed in matching entries can be restricted just like -search. Entries in othersafe.psafe3 that don't exist in mysafe.psafe3 are ignored. Update entries of mysafe.psafe3 with matching entries from othersafe.psafe3, wherever they differ. Sync `pwsafe-cli mysafe.psafe3 -sync=othersafe.psafe3 ] ` Fields to be compared can be restricted with -fields. Entries selected for comparison can be restricted by -subset, just like -search. Show unified (default), context or side-by-side diff. Multi-safe operations Diff `pwsafe-cli mysafe.psafe3 -diff=othersafe.psafe3 ] ]` This will use the safe's and entry's password policy to generate the new password `pwsafe-cli mysafe.psafe3 -search=Hotmail -fields=Title -new-password`ģ. Pwsafe-cli -search=gmail -clear=field1,field2. Pwsafe-cli -search=gmail -update=Field1=Value1,Field2=Value2. Pwsafe-cli ~/Sample123.psafe3 -search=gmail -delete Update Pwsafe-cli -search=gmail -print=e-mail,URL Delete However, other fields can be printed by explicitly specifying the search action to be -print with the desired fields: Printing just prints the Group, Title & User of matching entries on stdout, but Title is the only field that's guaranteed to be present for an entry. Results are printed on stdout one entry per line in the following format: The known valid field types areĪCTION represents the action to be performed on the search results. By default, all fields would be searched. The fields argument is a comma-separated list of fields in which search-text would be searched for. Other supported operators (mimicking the GUI) areĪ trailing /i makes the string operation case-insensitive, while /I makes it case sensitive. ![]() `pwsafe-cli mysafe.psafe3 -search=search-text ] ACTION` yes suppresses the confirmation, and just goes ahead with the changes. For search actions that modify the safe, pwsafe-cli would confirm before performing the action, once for each entry irrespective of the number of changes to that entry. This is perhaps the most important command, because it lets you zero in on an entry and perform some operation on it. Add a new entry to a safe `pwsafe-cli newsafe-psafe3 is auto-generated if unspecified. New Actions Create a new safe pwsafe-cli newsafe.psafe3 -new Pwsafe-cli mysafe.psafe3 -imp|-exp -text|-xml 2. Pwsafe-cli already implements import from & export to text & xml formats: diff=some/other/safe.psafe3).Īny operation that can modify the safe takes a -dry-run argument which just skips the part that saves the safe file after making modifications. This is the "current" safe: any operation that requires another safe provides the path to that safe as the value to the operation (e.g. It will probably not achieve feature parity with the GUI version, but will make pwsafe a lot more useful at the command-line.Īll commands require the safe to be operated on as the very first argument to pwsafe-cli. This document proposes some new features to be added to command-line version of pwsafe (called pwsafe-cli, in src/ui/cli). Add more functionality to PasswordSafe CLI
0 Comments
Leave a Reply. |