Mailing-List: contact ooo-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-issues@incubator.apache.org
From: bugzilla@apache.org
To: ooo-issues@incubator.apache.org
Subject: DO NOT REPLY [Bug 119090] Default Encryption Fails for Down-Level
 Implementations
Date: Mon, 19 Mar 2012 18:52:24 +0000
Message-ID: <bug-119090-248469-WrQZl0x0jB@https.issues.apache.org/ooo/>
In-Reply-To: <bug-119090-248469@https.issues.apache.org/ooo/>
References: <bug-119090-248469@https.issues.apache.org/ooo/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

https://issues.apache.org/ooo/show_bug.cgi?id=119090

--- Comment #10 from Rob Weir <robweir@apache.org> 2012-03-19 18:52:24 UTC ---
Thinking on this a little more.

At some point we need to change to AES and at that point we will break compat
with earlier editors.  We cannot avoid that.  We can only delay that.

But delay does have some value.  We can seed the install base with the ability
to read AES files,and do that for a release or two before we enable AES as the
default for writing.  So then in the future, when we make AES the default for
writing, the older versions (at least 3.4+) have the ability to read them as
well.

I have no idea whether changing the default is easy or hard, or whether any one
volunteers to do this.  But it is one possible approach.

The user could then change the default via the configuration option.

-- 
Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.