I have installed a Windows Program on Unix and running under Wine. The program is a DRM solution aimed at creating secure documents, at the stage of creating the document, the program fails.
The company does not support this program on Unix, can anyone who is more experienced than I am with unix offer any suggestions how this might be investigated further to find what is going wrong?
For example is there a way to find out where the prcocess is falling down.
Many thanks.
New Program on Unix
New Program on Unix
On 07/05/2011 07:05 AM, Falcon703549 wrote:
when the program fails? Is there and entry in the appdb for the program
and if so have you tried any suggestions listed there?
There are some good ideas in the forum posting guidelines for helping to
track down problems. Some of those may be a place for you to start to
gather more information about the issue so people can get a better idea
of what it might be. There is a sticky for the guidelines at the top of
the forum or the link is: http://wiki.winehq.org/ForumGuidelines
What version of the Wine are you using? Are there any error messagesI have installed a Windows Program on Unix and running under Wine. The program is a DRM solution aimed at creating secure documents, at the stage of creating the document, the program fails.
The company does not support this program on Unix, can anyone who is more experienced than I am with unix offer any suggestions how this might be investigated further to find what is going wrong?
For example is there a way to find out where the prcocess is falling down
when the program fails? Is there and entry in the appdb for the program
and if so have you tried any suggestions listed there?
There are some good ideas in the forum posting guidelines for helping to
track down problems. Some of those may be a place for you to start to
gather more information about the issue so people can get a better idea
of what it might be. There is a sticky for the guidelines at the top of
the forum or the link is: http://wiki.winehq.org/ForumGuidelines
-
SpawnHappyJake
- Level 5
- Posts: 272
- Joined: Sun Feb 06, 2011 5:57 am
A Native Solution
Let me grab my crystal ball and guess that by "DRM" you mean detecting whether the document has been altered or not, given that keeping people from copying a document is impossible.
In that case, you don't need a Windows program. LibreOffice, which does either everything MS Office can do or close to it, can sign documents for you. LibreOffice runs natively on Linux, Mac, and Windows, that is, without WINE or VirtualBox or any compatibility aids.
It uses asymmetrical encryption (that's where one key decrypts and one key encrypts) so that only you, the sole bearer of the secret private key, can create a signature for a document that when someone takes the public key, which you bundle with the document and release to a certificate authority and is mathmatically related to the private key, and uses that with a hash of the document, the signature is computed. If it matches the signature bundled with the document, then it's an original. If not, then the document has been altered.
One could verify that that really is your public key by going to the certificate authority with whom you registered that public key with your name.
I think the way it works is a hash is made of the document, then you encrypt that hash with your private key and bundle the encrypted hash with the document. You also bundle in the public key and your name. Then someone else who obtains the document can calculate the hash, decrypt the encrypted hash with the supplied public key, and see if the hashes match. If anyone alters the document, the hashes won't match. If someone replaces the encrypted hash and public key so that the hashes will match for the altered document, by going to the certificate authority one could see that that public key is not registered with who the author is supposed to be.
Cheers,
Jake
In that case, you don't need a Windows program. LibreOffice, which does either everything MS Office can do or close to it, can sign documents for you. LibreOffice runs natively on Linux, Mac, and Windows, that is, without WINE or VirtualBox or any compatibility aids.
It uses asymmetrical encryption (that's where one key decrypts and one key encrypts) so that only you, the sole bearer of the secret private key, can create a signature for a document that when someone takes the public key, which you bundle with the document and release to a certificate authority and is mathmatically related to the private key, and uses that with a hash of the document, the signature is computed. If it matches the signature bundled with the document, then it's an original. If not, then the document has been altered.
One could verify that that really is your public key by going to the certificate authority with whom you registered that public key with your name.
I think the way it works is a hash is made of the document, then you encrypt that hash with your private key and bundle the encrypted hash with the document. You also bundle in the public key and your name. Then someone else who obtains the document can calculate the hash, decrypt the encrypted hash with the supplied public key, and see if the hashes match. If anyone alters the document, the hashes won't match. If someone replaces the encrypted hash and public key so that the hashes will match for the altered document, by going to the certificate authority one could see that that public key is not registered with who the author is supposed to be.
Cheers,
Jake
