E-sign a Word doc? 2

[edglock21]

Is there a native (i.e. Microsoft) way for a reader to "sign" a Word doc? We're looking for a simple way to do this without using third-party certificates, if possible.

The document is policy related and management has asked me if this is something that Word can on its own. I suggested saving email replies from each person, but was asked to find out if it can be done within the document itself.

Thanks,
Ed

 

[edglock21]

Forgot to mention the version - we're using Office 2003

 

[fumei]

Legally sign it? I don't think so, but case law is still fuzzy on this.

Are you using 2003 with Sharepoint Services?

Could you expand on the purpose? Is it an identity issue? What exactly do you mean by "sign"?

Say Person A gets the file, opens it. What does "sign" mean really? Does it mean they have read it? I hardly think so, as this is impossible to verify.

Does it mean that they type in their name and that (by agreement) means they have read it? You could pick up the current network login name and match it to what they type in the "signature", as a sort of verification.

Other than that, you need a third party certificate type verification.

Gerry

 

[eyec]

if this is for your document management policy (HIPPA, SOX, etc) you can go various routes.

the cheapest way would be to have the persons you normally want to "sign" a document scan in their signature and when you send them a document have them insert it in the document when they return it either via email or on a shared document thru the "track changes" option.

i would suggest if you go this route to consider some security measures for safeguarding the scanned signature file though.

 

[edglock21]

fumei and eyec - thanks for your replies.

fumei - We're not using Sharepoint and the boss was a little fuzzy on the purpose - my take is that the reason for the 'signature' is, as you surmised, to indicate that the person has read, understands, and agrees with the document.

eyec - I, also, made the 'scan and fax' or 'scan and email' suggestions to the boss. You're correct in your assumption that management is looking for a cheap way to reach their goal.

After some further investigation, I found that Office 2003 includes "Digital Certificate for VBA Projects" which does what they're looking for, but which is not at all secure (the user can name their certificate however they would like and it is not necessarily indicative of whether a specific person did indeed even create the certificate).

I recommended that, if they want true accountability, that we go with "real" digital certificate authority. Looks like they're going to cheap-out and do a fax solution.

Thanks again for your assistance.
Ed

 

[fumei]

Digital Certificates for VBA Projects? Uh, well true (although 2002 also has this), but I am not quite catching the relevance. This is a signing for...VBA Projects..just like the name says. It has nothing at all to do with the document contents, or really even the document at all. It is only applicable to , well, the VBA projects.

Scan a signature, type a name...who cares? IMHO a scan signature is even less "signed" than a typed name matched to the current network logon. Unless you scan it fresh (and it would take some effort to determine that this occured), then this graphic of a signature is a file.

1. the file can be copied elsewhere and modified;

2. the file could be copied elsewhere and used elsewhere;

3. the file could be deleted by accident;

4. the file could get corrupted, by accident or deliberately.

Again, it really depends on what you are trying to do, and why, and how much verification you require. You did not answer, really, what the purpose is.

Let's run another example. You have a document. You have a defined list of people who are allowed to see, or edit, or respon to this document.

The document could easily contain an array listing those people. Totally hidden from the person who opens the file, their network logon name could be compared to that list. A log file could be written as to who opened the file and when. If the person opening is on the "signing list", a message could be displayed wen they close stating "Do you agree that you have read this document, and agree" A Yes/No could set a boolean True/False document variable (also written to a log file).

Or it could state - well it could state whatever you want.

Further, the OK list could in fact automatically close the file to those NOT on the list, without them seeing the document. I must emphasize that a really good coder, if aware of the tricks behind such a document could get at it anyway. However, you can make it pretty darn difficult. This however, is getting away from the original post re: signing.

Hard to suggest anything if the purpose is unknown.

Gerry

 

[fumei]

Digital Certificates for VBA Projects? Uh, well true (although 2002 also has this), but I am not quite catching the relevance. This is a signing for...VBA Projects..just like the name says. It has nothing at all to do with the document contents, or really even the document at all. It is only applicable to , well, the VBA projects.

Scan a signature, type a name...who cares? IMHO a scan signature is even less "signed" than a typed name matched to the current network logon. Unless you scan it fresh (and it would take some effort to determine that this occured), then this graphic of a signature is a file.

1. the file can be copied elsewhere and modified;

2. the file could be copied elsewhere and used elsewhere;

3. the file could be deleted by accident;

4. the file could get corrupted, by accident or deliberately.

Again, it really depends on what you are trying to do, and why, and how much verification you require. You did not answer, really, what the purpose is.

Let's run another example. You have a document. You have a defined list of people who are allowed to see, or edit, or respon to this document.

The document could easily contain an array listing those people. Totally hidden from the person who opens the file, their network logon name could be compared to that list. A log file could be written as to who opened the file and when. If the person opening is on the "signing list", a message could be displayed wen they close stating "Do you agree that you have read this document, and agree" A Yes/No could set a boolean True/False document variable (also written to a log file).

Or it could state - well it could state whatever you want.

Further, the OK list could in fact automatically close the file to those NOT on the list, without them seeing the document. I must emphasize that a really good coder, if aware of the tricks behind such a document could get at it anyway. However, you can make it pretty darn difficult. This however, is getting away from the original post re: signing.

Hard to suggest anything if the purpose is unknown.

Gerry