So what I ended up doing is thinking I would work backwards, so I did a 
grep for the most obvious password related phrase:
"Save with password" which is an option while saving.
I found a single src file that had this phrase so I thought "PERFECT!", 
the file:
fpicker/source/office/iodlg.src
I decided I needed to do a check before going any farther so what I did 
was change the text of "Save with password" to something else ("Do you 
know the muffin man!?")
I then compiles libreoffice for the first time, thinking 2 hours max, 
ended up being 10 hours (running a VM with 1 gig of RAM probably at 
fault). I opened soffice, and...damn
still reads "Save with password" when I go to save as
Not sure how this can be the case as it's the only instance of Save with 
password in all of the source files I thought it MUST be the right one.
Any ideas how this can be, I like working backwards so it'd be nice to 
see what I'm missing. Thanks for the help
On 05/28/2012 03:41 AM, Michael Meeks wrote:
Hi Joel,
On Sat, 2012-05-26 at 23:34 -0700, Joel Madero wrote:
Trying to find the location and the manner in which libreoffice
protects files. Anyone know where I can locate the appropriate source
file, what the object names are that I should look for, and if
possible direct me to the documentation. Thanks in advance
        There is no one answer here; it really depends on what file format you
are talking about :-) A good way to find those places from the bottom up
is to do:
        $ git grep rtl_cipher
        And see where it takes you; package/ is the zip file code that is used
for ODF.
        HTH :-)
                Michael.
Context
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.