gburjan

eyaml edit should create tempfiles with more restrictive permissions (for example 0600) instead of using current umask

4

Seems like eyaml backend's write_tempfile function uses ruby Tempfile without specifying appropriate permissions, so decrypted temporary files which contain decrypted passwords are saved as world readable on a usual Linux...