Un-signed button!?

HCL Domino Domino Forum
1

We are experiencing problems with mailing a button to users.

The button is LotusScript and is defined in a RTF in a profile document.

The mail is created using LotusScript and the body copied from the profile document.

The Body-rtf is Signed and the e-mail is Signed but when the recipient clicks the button he still get the message that the buttos is un-secure and signed by “-No signature-”.

If all users were on Notes 6.x we could accept they trust “No Signature” but there is a mix of everything from 4.6 and up…

Please any help is appreciated.

/Mats

2

Subject: Un-signed button!?

Thats a known problem, posted in the 4&5 forum.We have never found any way, neither with standard notes nor using api, of getting that button signed :frowning:

3

Subject: RE: Un-signed button!?

In R5 the API function NSFHotSpotSign claims to be able to sign LotusScript code, though I have not tried it.

4

Subject: *It doesn’t work very well or very consistently.

5

Subject: *For example?

6

Subject: RE: *For example?

There were some problems with the API call, so if you compile with the 6.0.0 C API or 5.0.x, the code will not work with 6.0.0. This is documented below, but there are additional problems with compiling with 5.0.9 and higher and compatibility as well, although they are not ordinal problems. If you compile and work with only 6.0.1 and above, you are probably safe, but I’m a bit skittish after getting burned a few times trying to deliver this to customers.

— extract from D6.0.1 C-API toolkit readme —

Compatibility Issues

MS Windows applications that were built with a 5.0.x release of the Lotus

C API Toolkit for Domino and Notes and call any one of the following functions:

  • SECHashPassword

  • SECVerifyPassword

  • NSFHotSpotSign

  • StoredFormAddItems

  • StoredFormRemoveItems

will not run on Notes and Domino 6 due to discrepancies with the ordinal values

defined for these functions. This problem has been fixed in Notes and Domino 6.0.1.

MS Windows applications that were built with a 5.0.x release of the Lotus C API

Toolkit for Domino and Notes and call the functions listed above will run on

Notes and Domino 6.0.1 and later releases. MS Windows applications that were built

with the Lotus C API Toolkit for Notes/Domino 6 and call one of the functions listed

above will also run on later releases of Notes and Domino.

MS Windows applications that were built with the Lotus C API Toolkit for

Notes/Domino 6 and call the function, NSFDbOpenTemplate, will not be able to run

on Notes/Domino 6.0.1 and later releases. You will need to recompile these

applications with the Lotus C API Toolkit for Notes/Domino 6.0.1.

7

Subject: RE: *For example?

From LotusScript and using the function name this does not look like it is a concern.

8

Subject: RE: Un-signed button!?

Hmm, when did that pop up? My last R5 api version is 5.0.7 and its not documented there.

9

Subject: RE: Un-signed button!?

It was not publicly documented at first. Then the initial release was documented as 5.0.8. It might exist in earlier releases too. NSFMemorySign seems to achieve the same thing. It existed in R4, but it is still not publicly documented.

10

Subject: Un-signed button!?

I tried using LotusScript code to sign a LotusScript button, and it seems to work in R4, R5 and Notes 6. If you would like to try it on your button, please e-mail me. My e-mail address is in my profile.

11

Subject: RE: Un-signed button!?

Thank you all. Sometimes a question doesn’t seem to attract any attention but this time… I’m pleased :slight_smile:

Will send you an e-mail Rod

Thanks again.