+ Similar Entries
|
|
OpenNTF shows PRODUC...Blog: Erik BrooksErik Brooks Updated  Ratings
0
Comments
1
|
|
|
2009 - The Year of X...Blog: Beyond The Ye...Peter Presnell Updated Ratings
0
Comments
1
|
|
|
Are You A Legend (Ye...Blog: Beyond The Ye...Peter Presnell Updated Ratings
0
Comments
0
|
|
|
Preview: Discussion ...Blog: Beyond The Ye...Peter Presnell Updated Ratings
0
Comments
2
|
|
|
OpenNTF - free hosti...Blog: TexasSwedeKarl-Henry Martinsso... Updated Ratings
0
Comments
1
|
+ Archive
+ Blog Authors
OpenNTF Thoughts - Part 2 - Signing Applications
Since I'm a Domino Administration is only part of my job responsibilites (and Application Development is even less) and we don't have anyone to do Application Development, I've had to rely on finding code and applications wherever I could find them. The easier they are to move into production the better. One thing that would make this process easier (for me at least) is for OpenNTF to have a single signing ID that applications are signed with before being released. This would let me change my ECL's to allow these applications to just be dropped into my production environment (after testing) and work.
|
Ratings
0
|
| IBM Lotus Connections | Help | Tools | About |
|---|---|---|---|
Comments (1)
The obvious thing to do would be just to resign the template/database with the signature in your infrastructure that is allowed to run on the clients.
This would standard practice the admin can stop rogue code from
executing.
Using a central ID for openNTF is probably not a good idea. It
could open you up to a user downloading a template which you
haven't tested in your environment and they would be given full
access to run it.