You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there is an error (e.g. UID has no email address or the mail server fails to deliver), pius still stores the signed key attachment in --out-dir along with successfully sent signatures. So after many keys are signed there's no separation distinguishing deliveries and non-deliveries. Motivated diligent users need to know which signatures to send by some other means (alternate recipient address, alternate sending server, or push to key server).
There is no logging option to help with this. I suppose one could run script -c 'pius -A --out-dir=$out_dir' pius.log, and then examine that for errors when the session is over. But users have to think of that in advance - and even if they do, it's still a burden to search for the failures and find the corresponding signature file.
The text was updated successfully, but these errors were encountered:
It looks like my script hack fails. When I run this way:
script -c "pius -A --out-dir=$out_dir" >(dos2unix >> pius.log)
it should append the whole session output to pius.log, but it only writes the output of the first key signed. That may be a bug in script but it effectively increases the need for pius to do some logging.
When there is an error (e.g. UID has no email address or the mail server fails to deliver), pius still stores the signed key attachment in
--out-dir
along with successfully sent signatures. So after many keys are signed there's no separation distinguishing deliveries and non-deliveries. Motivated diligent users need to know which signatures to send by some other means (alternate recipient address, alternate sending server, or push to key server).There is no logging option to help with this. I suppose one could run
script -c 'pius -A --out-dir=$out_dir' pius.log
, and then examine that for errors when the session is over. But users have to think of that in advance - and even if they do, it's still a burden to search for the failures and find the corresponding signature file.The text was updated successfully, but these errors were encountered: