HelloI would like to add a protection to a spreadsheet that I have created as I intend to sell it.
Problem is that if I simply password protect it people can simply share the password, and I was wondering if there is a way to put some more robust protection.
Protecting a file is much more difficult compared to protecting a program executable file. You can set a password for a spreadsheet but if you are selling it then the purchaser will have the password and can give or sell your spreadsheet to someone else.
Excel has a feature to protect VBA code from being viewed. If the ideas you want to protect are done through VBA then the way you carry out the operations can be hidden but the spreadsheet can be used by anyone who has the file. There are third party programs that give a high level of protection to Excel spreadsheets. One, XLS Padlock, ( ) compiles the Excel spreadsheet into an executable file. This is a commercial program and has to be bought. When run it requires authorisation to run and then opens the spreadsheet in Excel, which must be installed on the computer. I am not aware of any program that can be used to secure a LO Calc file.
I want to protect my word file from copying and pasting. I tried it from restrict editing feature. But it enables only editing protection. When I copy text or images and paste into another word document, all are copied. How could I protect my document from copying and pasting? Is there any feature?
This method is a failure method ,,because any one can open protected word file by converting. Docx to zip then open the zip extension find the file name setting.xml delete it then change zip to docx then open the protected file and you can easily open and edit copy or paste the contents.
The ultimate answer is that although you can make things harder, you cannot stop copying, though. In the final analysis, though, this goes back to the aphorism that if two people know a secret, it is no longer a secret.
If you protect a document / restrict editing for "filling in forms," text cannot be selected for copying. It is not difficult to overcome this protection, nor the "No Changes" protection Filip suggested. The "filling in forms" is highly intrusive protection and you may want "No changes" instead, with the addition of a shape.
If you follow Filip's suggestion, I'm afraid text can still be selected and copied into the clipboard. However, you could, before applying the restriction, add a borderless rectangle with transparent fill in front of your text. Anyone trying to copy would select the rectangle, not the text. That has to be done for each page of the document.
This way of protecting data from editing or copy or paste is a failure method.....because it is easy to convert .docx file into zip and then delete the settings xml file.....then the file will open easily....
OK so I understand @BenLee - locking, hiding, view-only permissions - all of these still allow a user that has any access to a doc to duplicate the whole thing? Thanks for helping me it is easier for your advice than for me to try to gametheory and try out all the possible permuations.
If you do have information that you need kept confidential while displaying other information, the best option from a security standpoint is still cross-doc and only syncing over the information that is okay to be shared.
long term, we need a more secure way to present our data to our users. I see 3 possibilities, none easy, but something needs to be done at some point.
a) make all tables a view of data stored in a database and filter/allow acces based on authentication - obviously this requires a complete rewrite of coda and templating and copying are a complete different animal from what they are today. But is solves the issue we are now writing about and it solves a lot of other issues too. Working offline might be complicated or not possible anymore, I guess the user has to decide if that is OK (for me it is, we have excellent internet just about everywhere.
b) store the doc encrypted on the users computer and unencrypt only what is viewed. Not sure if this can be done though, it might open up a complete new market
c) do some processing of the docs on the backend and only send to the users what is needed to build up the screen. This would not necessarily make the doc slow if the backend and internet connection is quick enough. I think I would like this best.
PS: in published editing mode this seems to be taken care of, but the doc is (partly) open to anyone with the URL - fixing that would already be a big help Just show a (custom) login page on that URL and nothing more (of publised doc in edit mode) would make me very happy!
This is a good time to acknowledge the accomplishments that have materialized since the original start of this thread. Even though I can think of more fine grained authorization schemes, you can protect your work to a large extend at this point in time (June 2021) by combining locking pages and setting non-copy options.
Hello,
We have a few online eLearning courses that we would like to convert to a PDF. This is a popular request from our students.
One of the reasons we have not done this is that we don't want to compromise our copyright by having a competitor copy our hard work.
Is there a way to protect a PDF document from being copied? I know that if there is a will, there is a way and that we won't stop somebody who is hell bent on copying it.
We do have Adobe Acrobat Pro 9 if that helps. Any ideas on what we could do and how to best protect the document?
Thanks!
-Dave
If the document is destinated to 'generic' people (without particular IT skills), a simple Protection with the Adobe Acrobat would be a good idea. Only expert people know tools that remove this protection (and they don't work always). I suggest limiting both print abilities and copy/paste: if you limit only the copy/paste ability, someone can remove the protection by re-printing the PDF document with a PDF printer.
If your information product has sufficient value, the most secure solution is to investigate the numerous online solutions for digital security that involve the provider hosting your file and securing the site access with a password linked to that specific file. I'm on the verge of purchasing BookGuardPro, including a monthly subscription to protect my PDF files online. There are a number of similar applications. If you find something you like better let me know.
Their server assigns a password to each file which can be subsequently revoked if desired, plus there are options for allowing or denying printing and copying. This particular application includes options for Macintosh users and was more reasonably priced that some of the others I investigated.
Once your content is compromised and distributed without your consent, I see no way to recover it, hence the concern and willingness to implement addtional security precautions. Some of the companies offer government grade security at far higher cost.
1. Open the document you want converted to PDF forms as well as protect it. open the print dialog box usually by pressing CTRL + P, the printer selection select novaPDF Pro.
2. Click on the Properties button (or Preferences) to open a dialog box 'novaPDF Pro Properties'
3. following dialog box appear click 'security' tab and then you can select the type of encryption Low Level or High Level Encryption method, then you fill the password if you want or give a sign the checklist on the points modify document content.
I have created a secure and password protected PDF document but one of my friend remove the security barriers and converted my PDF to Doc using classic PDF editor. He is IT student so he mite find thesoftware that break the barriers, very few of people know these tactics.
I am using c# (VS2010 FrameWork:v4.0) and SqlServer 2012 to build an application. I searched online to find ways to prevent copying this system and I thought the only part that needs to be protected from copying is the database.
Do I need to protect also the application (executive file) from copying with the database? If yes, does this mean I have to provide the user with a new copy to install it if the user looses the application files?
One Idea I have in my mind to protect the DB is to save some passwords/keys in DB (in the form of varbinary) and when the device is logged in (runs the app) the application checks for (the MAC address) of the device if it is not saved then the app asks for a key. once the key is used, the device mac address is saved with the key. Is this a right thing to do? is there any advice about it?
I have also read about installing SQLExpress on client PC and That should protect the DB files from manipulation, so I have to provide a way to upgrade/ update DB scripts in the future rather than replacing client's DB with a new one. And I thought to provide a form in the app protected by a password, and I can write a script in a textbox in the form (__For Example: Alter Proc_ ...), and Save it. Can I do this? or would that be a stupid thing to do?
It is possible to create licensing schemes where the application runs only on the designated hardware. Your application takes the host fingerprint (eg. net MAC), uploads it to a service you host, you sign the fingerprint with a private key and provide the signature to the application, then the application validates the fingerprint signature using the embedded public key and runs the application. While this sounds doable, there is a number of ways this can and often does go wrong. Users change the fingerprint frequently (eg. hardware update). Fingerprints are difficult to enforce on virtualized environments (VMs can edit their MAC). It is very difficult to harden application code against a moderate hacker willing to attack and bypass your protection, and basically impossible to harden it against a skilled hacker.
3a8082e126