On Tue, 2009-04-07 at 23:09 +0800, Ming Fei Jia wrote: > Kohei, > > Kohei Yoshida <[email protected]> wrote on 04/07/2009 11:35:37 AM: > > > > The encryption work is already done. The CWS is blocking for the other > > feature, the sheet protection options, mostly on the ODF TC file format > > change approval. Once the file change is approved the missing piece of > > ODF load/save can be implemented quite easily for that sheet protection > > options feature. > > > > Here is the proposal: > > http://wiki.oasis-open.org/office/Spreadsheet_Table_Protection_Options > > > > (Actually any help pushing my proposal on the ODF TC would be great, > > since you guys are pretty active on the TC...) > I take a look at the proposal again. The proposal mainly includes 2 parts > of contents: (1)add table protection options;(2)add double-hash algorithm. > The proposal makes sense for me although I still need to think about the > implementation details. Of course, let us discuss the proposal on the TC > list, not appropriate here:)>
Sure. That's fine. The main sticking point was what URI to use to represent the legacy xls hashing, but let's move the discussion to the TC. > > > > > Do you > > > need our support and cooperation? -:) > > > > Thanks for your offer, but since the core encryption work is 99% > > complete I don't think I need any more help on the core part of the > > implementation. > > > > Having said that, we are still lacking some UI fine-tuning since the UI > > for security, which includes file encryption, has undergone major change > > recently in the framework project. So, some work has to be done to hook > > the xls encryption bits to that new framework, which I haven't done yet. > > So, help in that area would be great. I've been talking with Mikhail > > Voitenko and Mathias Bauer about the new security framework on the > > framework list. > I do not know the framework change at all before now. I need to first > subscribe the framework list and take a look at what happened. Moreover, > besides Excel file encryption, Symphony also implements Word file > encryption, the 2 components should have common part at the framework > layer. If Excel file encryption modified the framework layer(I think > so),the Word file encryption should reuse the same modification. So my > colleague, Steve Yin (in the cc list) and I will investigate how the > framework layer change impacts the sc/sw file encryption. Great! BTW, the new security framework would probably affect the password input UI part, but should not affect anything else IMO. In terms of common part between Word and Excel encryption, my current Excel encryption code is already partitioned to leave the common part at framework level. The cipher code is all implemented in sal, and the front-end class for that is in svx. The code in sc is very minimal in terms of performing the actual encryption since the most heavy lifting is done by that shared front-end class in svx. That front-end class in svx was already there before I began my work, for the import decryption feature. So, I think it's fair to say that the amount of extra work I did for xls export encryption is pretty small. With this in mind, I don't think any other major refactoring is needed to share common code between Word and Excel encryptions. > BTW, before we > discuss issues on framework list, a question first, the framework change > you said has already been put into latest dev repository, or still at some > CWS? so that we can easily get the change code to take a look. thanks. The new security framework I believe was first integrated in m38. So the latest milestone should have that. HTH, Kohei --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
