30
edits
(Improved Security - install confirmation mechanism) |
m (Improved Security - install confirmation mechanism) |
||
Line 32: | Line 32: | ||
*How about using a 'password', gathered and stored similar to other passwords? It's left as an exercise for the reader to determine if autofill would be tolerable (someone will build an extension to do it, surely). | *How about using a 'password', gathered and stored similar to other passwords? It's left as an exercise for the reader to determine if autofill would be tolerable (someone will build an extension to do it, surely). | ||
*Here's my pitch: | *Here's my pitch: | ||
**The crowbar becomes the primary | **The crowbar becomes the primary UI for remote installs. | ||
**The crowbar integrates the password mechanism. | **The crowbar integrates the password mechanism. On first use or if the password is not configured, change the title of the password box to "Set Password" or some such. | ||
**For users who can change the whitelist, controls appear to allow doing so (directly) and also to allow one-time bypassing. (Can an admin pre-populate the whitelist and/or make it read-only?) | **For users who can change the whitelist, controls appear to allow doing so (directly) and also to allow one-time bypassing. (Can an admin pre-populate the whitelist and/or make it read-only?) | ||
**The former install dialog becomes both on-demand and purely informational (warning, domain name, software name, etc.). | **The former install dialog becomes both on-demand and purely informational (warning, domain name, software name, etc.). The dialog is accessed through a "Details" button. The on-button timer goes away. | ||
*If this is all whack, just delete it. It won't hurt my feelings. ;-) | *If this is all whack, just delete it. It won't hurt my feelings. ;-) | ||
edits