Issue 124533 - Option "Always create a backup copy" should be activated by default
Summary: Option "Always create a backup copy" should be activated by default
Status: CLOSED DUPLICATE of issue 104879
Alias: None
Product: General
Classification: Code
Component: security (show other issues)
Version: 4.0.1
Hardware: All All
: P3 Normal with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-27 08:53 UTC by richard_g
Modified: 2017-05-20 10:01 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description richard_g 2014-03-27 08:53:16 UTC 
Too many documents are lost because users do not make several backup copies of their work and because they do not know that there is an option allowing to always create a backup copy. Look at the forum in the subject "Document recovery", and you will see the disaster!

As a security enhancement, I suggest that the option "Always create a backup copy" should be activated by default, and I will not a accept a response such as "Backup copies will take too much disk space" when disks capacity is several hundreds Gbytes! If you want to have the best office software, you have to enhance the documents security first !

Richard.
Comment 1 Edwin Sharp 2014-03-27 12:32:24 UTC 
Agreed - but duplicate bug

*** This issue has been marked as a duplicate of issue 104879 ***
Comment 2 Andre 2014-03-27 12:53:32 UTC 
This is a problem regarding the safety of documents (handling the accidental modification or deletion), not about security (malicious exploit of crashes or other bugs).
Comment 3 richard_g 2014-03-27 13:45:25 UTC 
OK, this is a problem regarding safety of documents, not security. Sorry for my poor english.

I add votes to issue 104879.
Comment 4 Andre 2014-03-27 14:54:55 UTC 
@richard_g: Absolutely no problem.  I just mentioned that, because security bugs require a stricter handling and are usually not visible to the public.  This is to prevent the publication of exploitable bugs before there is a "cure".

I changed the assignee to the regular (non-security) default.