Pwsafe linux7/24/2023 ![]() Initializing file size.ġ7:24:20.171 TRACE o.c.frontend.fuse. See the log snippet: 17:24:20.089 TRACE o.c.f. - Acquired read path lock for ''ġ7:24:20.089 TRACE o.c.f. - Acquired read path lock for ''ġ7:24:20.089 TRACE o.c.f. - Acquired read data lock for ''ġ7:24:20.089 TRACE o.c. - getattr /password.psafe3 (lastModifiedTime:, lastAccessTime: T13:12:13.599603Z, creationTime:, isRegularFile: true, isDirectory: false, isSymbolicLink: false, isOther: false, size: 73560, fileKey: (dev=10303,ino=7079318))ġ7:24:20.089 TRACE o.c.f. - Released read data lock for ''ġ7:24:20.089 TRACE o.c.f. - Released read path lock for ''ġ7:24:20.170 TRACE o.c.f. - Acquired read path lock for ''ġ7:24:20.170 TRACE o.c.f. - Acquired read data lock for ''ġ7:24:20.170 TRACE o.c. - open /password.psafe3 (0)ġ7:24:20.171 TRACE o.c.cryptofs.fh.OpenCryptoFile - First channel for this openFile. I’ve looked in the log file, but there are no errors to be seen. Specifying -do-tall or -do-wide forces the choice, and -do-auto resets the system to use its internal logic. By default, Password Safe will check the screen dimensions and choose tall or wide versions of the larger dialog screens. I’m doing this with Cryptomator in Debug mode and using the FUSE volume type. Finally, there are some special command line flags beginning with '-'. I have just tried upgrading Password Safe from 1.04 to the latest for Ubuntu which is 1.8.1, made no difference. Well I just checked - that was where I got to before from the link, and those packages no longer contain a command line client that can manage the database or look up passwords - just like in the 'cli.html' page listed above, this is a command-line tool to encrypt a file or start a humorous graphical interface, not the actual CLI tool to encrypt, decrypt, and manage without the. See the screenshot of what I see when the app attempts to open the password file in R/W mode. I haven’t had a problem with other files or apps, so possibly the problem is with Password Safe but that works fine with files which aren’t within the Vault, so I don’t think that’s it. This has been the case for several versions (I started on 1.4.2 and I am now on 1.4.10). ![]() Opening the same Vault on Windows 7 and using the same app to open the file does not have this problem, so I’m thinking the problem is specific to the Ubuntu version of Cryptomator. When I try to open it on my Ubuntu 18.04 box, it complains that the file is locked and therefore can only be opened in read only mode (See screenshot). ![]() My Cryptomator Vault contains a file which is opened Password Safe. ![]()
0 Comments
Leave a Reply. |