https://bugs.documentfoundation.org/show_bug.cgi?id=157943

            Bug ID: 157943
           Summary: LibreOffice 7.6.2.1 - opened files can be modified by
                    someone else without first person's knowledge, even
                    when .lock file exists
           Product: LibreOffice
           Version: 7.6.2.1 release
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: LibreOffice
          Assignee: [email protected]
          Reporter: [email protected]

Description:
After updating LibreOffice to version 7.6.2.1 on our employees’ PCs our users
realized they can modify files located in shared folders (Active Directory
shares mapped to disks) which are currently opened by someone, modify it and
save changes without original editor’s knowledge. When user tries to open
„locked” file he gets an error saying the file is locked by someone, has
options „Open R/O”, „Open Copy” and „Open” at the bottom of window. When he
chooses the last option he can modify file and nothing stops him from
overwriting this file in it’s original location. IMHO this should not happen
and it’s dangerous becasuse e.g. user may perform calculations in spreadsheet
file basing on outdated data just because he simply doesn’t know that file has
been modified.
This problem happened in LibreOffice Writer and Calc, I guess the same will
affect rest of Libreoffice programs.

Steps to Reproduce:
1.Alice opens file in shared location and she’s working on it, making some
changes, saves file with e.g. CTRL+S shortcut, keeps file open, .lock file is
created in filesystem,
2.Bob tries to open file, which is currently opened by Alice, error is shown
saying file is locked by someone and user has to choose what to do,
3.Bob has options „Open R/O”, ”Open Copy”, ”Open”, chooses „Open” at the bottom
of a error window, file opens,
4.Bob modifies file like nothing ever happened, saves it, sees no more
warnings,
5.When Alice tries to save her work (nothing is shown earlier!), she gets an
error saying the file has been modified by someone.


Actual Results:
Bob is able to open and modify a file on which Alice is currently working. She
doesn’t know the file has been opened for editing and modified by someone else
until she tries to save her version of file with e.g. CTRL+S shortcut. She gets
an error. When she re-opens that file she can see what has been modified. She
can save her version of file by choosing "Save anyway", but she will never know
WHAT has been modified and WHO did it.

Expected Results:
Bob should be allowed only to open file on which Alice is currently working in
R/O mode or to create a local copy on his PC. MOdifying a original file in it’s
original location should be impossible until .lock file is removed
(automatically or manually in File Explorer if something went south)



Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: pl-PL (pl_PL); UI: pl-PL
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to