<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - Relative linked text sections should automatically read on document opening" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135508#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - Relative linked text sections should automatically read on document opening" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135508">bug 135508</a> from <a class="email" href="mailto:live@hushmail.com" title="S.Zosgornik <live@hushmail.com>"> S.Zosgornik</a> <pre>(In reply to Mike Kaganski from <a href="show_bug.cgi?id=135508#c6">comment #6</a>) > You seem to not read carefully. Specifically for this case, I explained in > <a href="show_bug.cgi?id=135508#c4">comment 4</a>: > > > Absolutely. The request is out of question, because automatically reading an > > external document Again, you speak about documents with links to external SITES while I speak about locale files. LibreOffice isn't a web-browser nor an email-client. It can't open web-sites other than in plain-text and the only concern would be about external images that could track the users. So I can totally agree to a secure setting to prevent LibO to open remote files. Similar to the security setting of disable macros by default. But the dialog says: "The document contains one or more links to external data. Would you like to change the document, and update all links to get the most recent data?" And even if you chose "No" will LibO include the data of the linked document, just not updated to the current version. Sure. buffer-overrun attempts can happen, even on local files downloaded from the wrong source. But the right solution should be to ask the user to execute macro data and open remote files rather than urge him to confirm his own documents on every opening.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>