https://bugs.kde.org/show_bug.cgi?id=438671
--- Comment #3 from David Hurka <david.hu...@mailbox.org> --- Thanks! I understand that your browser offered to open this remote document with Okular, or with the browser’s embedded PDF viewer. When Okular opens the file, it realizes that it is password protected, and wants to look for a password in kdewallet, or get it from you. kdewallet is password protected, that is why you get two password dialogs. > 1) In the provided data environment (browser-based), you double-click > a selected file to open. A message windows opens: > > Conversion in progress... > > changes to > > Document will be prepared for annotations.... > Name_of_document.pdf > > Then an additional browser window pops up with the options > to select how to open the file. > Selection options are: > browser > okular (standard) This procedure lets me think that the cloud service wants you to use a certain browser plugin (maybe the embedded PDF reader). And then they will tell the password only to this browser plugin. There is no way to tell such a password to Okular, or at least Brainloop does not use such a way. The reason for protecting the document with an unknown password is that you are not supposed to create copies of the document. If you save the document to disk, you will not receive the password, because you don’t use that plugin. > Opening of *.pdf files only works with Adobe Reader, because the > Adobe rights management is activated in the Secure Data Space and > a user can therefore the user will always see a Brainmark file as > a PDF file. > A Brainmark file is the copy of the original file as an image > or PDF, which is watermarked. Okay, you mention that it works with Adobe Reader. Then Adobe Reader probably has some interface for receiving a password from a browser, and then it doesn’t allow to save on disk anymore. I don’t think Okular can’t provide such an interface, because it is not proprietary. If it had such an interface, you could simply change the source code so that Okular allows saving to disk. Brainloop wouldn’t want to use it. But Adobe Reader may seem proprietary enough that Brainloop thinks using it is secure. (I really doubt that it is secure - what prevents you from making screenshots?) > [Contents of https://www.brainloop.com/en-gb/solutions/brainloop-boardroom/] Sometimes companies only want to look secure. Maybe we can provide this interface, and make Brainloop think the user will not uncheck the “Obey DRM limitations” checkbox, so they can use this interface while still looking secure? -- You are receiving this mail because: You are watching all bug changes.
