Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on PDF attached files and temporary files #5950

Closed
OlivierDoucet opened this issue Jan 17, 2021 · 2 comments · Fixed by #6606
Closed

Error on PDF attached files and temporary files #5950

OlivierDoucet opened this issue Jan 17, 2021 · 2 comments · Fixed by #6606

Comments

@OlivierDoucet
Copy link

Overview

When I open a pdf file attached on an entries, Acrobat make error that the file is already open by an other user.
When I looking for temporaty file on my profil AppData\Lacal\temp, I see different files with the same name but some new carraters behin. That is to say, with this error, temp file are not cleaned at the end of open process.
If I open an other type file (.csv for exemple) it is on redead only mode. I can't modified then.
I am on window10 And keppassxc.exe is allowed to acces to all files.
If I open with Keepass2 that is OK

Best regards

Expected Behavior

File must be open en clean at the end in Appdat/Local\Temp

Screen shot

image
image
image

VERSION

KeePassXC - Version 2.6.2
Révision : e9b9582

Qt 5.15.1
Le mode débogage est désactivé.

Système d’exploitation : Windows 10 Version 2009
Architecture de l’unité centrale : x86_64
Noyau : winnt 10.0.19042

Extensions activées :

  • Saisie automatique
  • Intégration aux navigateurs
  • Agent SSH
  • KeeShare (partage signé et non signé)
  • YubiKey

Bibliothèques cryptographiques :
libgcrypt 1.8.6

@phoerious
Copy link
Member

Tracked by #2400.

@OlivierDoucet
Copy link
Author

Thank you phoerious for your comment, but I don't find meaning to change temp directory on keepassxc settings.
post #2400 explain "Just setting the mode to 0600 is not very ..." but what is 0600 mode ?

phoerious added a commit that referenced this issue Jun 10, 2021
Externally opened attachments are now lifecycle-managed properly.

The temporary files are created with stricter permissions and entirely
random names (except for the file extension) to prevent meta data leakage.

When the database is closed, the files are overwritten with random
data and are also more reliably deleted than before.

Changes to the temporary files are monitored and the user is asked
if they want to save the changes back to the database (fixes #3130).

KeePassXC does not keep a lock on any of the temporary files, resolving
long-standing issues with applications such as Adobe Acrobat on Windows
(fixes #5950, fixes #5839).

Internally, attachments are copied less. The EntryAttachmentsWidget
now only references EntryAttachments instead of owning a separate copy
(which used to not be cleared properly under certain circumstances).
phoerious added a commit that referenced this issue Jun 12, 2021
Externally opened attachments are now lifecycle-managed properly.

The temporary files are created with stricter permissions and entirely
random names (except for the file extension) to prevent meta data leakage.

When the database is closed, the files are overwritten with random
data and are also more reliably deleted than before.

Changes to the temporary files are monitored and the user is asked
if they want to save the changes back to the database (fixes #3130).

KeePassXC does not keep a lock on any of the temporary files, resolving
long-standing issues with applications such as Adobe Acrobat on Windows
(fixes #5950, fixes #5839).

Internally, attachments are copied less. The EntryAttachmentsWidget
now only references EntryAttachments instead of owning a separate copy
(which used to not be cleared properly under certain circumstances).
droidmonkey pushed a commit that referenced this issue Jul 14, 2021
Externally opened attachments are now lifecycle-managed properly.

The temporary files are created with stricter permissions and entirely
random names (except for the file extension) to prevent meta data leakage.

When the database is closed, the files are overwritten with random
data and are also more reliably deleted than before.

Changes to the temporary files are monitored and the user is asked
if they want to save the changes back to the database (fixes #3130).

KeePassXC does not keep a lock on any of the temporary files, resolving
long-standing issues with applications such as Adobe Acrobat on Windows
(fixes #5950, fixes #5839).

Internally, attachments are copied less. The EntryAttachmentsWidget
now only references EntryAttachments instead of owning a separate copy
(which used to not be cleared properly under certain circumstances).
droidmonkey pushed a commit that referenced this issue Aug 22, 2021
Externally opened attachments are now lifecycle-managed properly.

The temporary files are created with stricter permissions and entirely
random names (except for the file extension) to prevent meta data leakage.

When the database is closed, the files are overwritten with random
data and are also more reliably deleted than before.

Changes to the temporary files are monitored and the user is asked
if they want to save the changes back to the database (fixes #3130).

KeePassXC does not keep a lock on any of the temporary files, resolving
long-standing issues with applications such as Adobe Acrobat on Windows
(fixes #5950, fixes #5839).

Internally, attachments are copied less. The EntryAttachmentsWidget
now only references EntryAttachments instead of owning a separate copy
(which used to not be cleared properly under certain circumstances).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants