I would like to propose a suggestion. I have a site where another designer will be working on the site. He is a Joomla nerd as well and because I do not share my keys with anyone I removed the update keys to Akeeba Backup and Admin Tools.
I see that JCE sets the key as a password field so that it cannot be copied and I think that is a really good idea. You might want to consider doing this for your extensions to help us that love Akeeba and want to do our part to help you flourish.
We often have others login to our sites to help sort a problem or some other need. All they need to do is go into the component and they can have access to our keys. Yes we could setup ACL to prevent access but we don’t always remember to do that...;)
So just passing along my thoughts to help Akeeba and to ensure that those that want to use it pay for that privilege...
I see that JCE sets the key as a password field so that it cannot be copied and I think that is a really good idea. You might want to consider doing this for your extensions to help us that love Akeeba and want to do our part to help you flourish.
We often have others login to our sites to help sort a problem or some other need. All they need to do is go into the component and they can have access to our keys. Yes we could setup ACL to prevent access but we don’t always remember to do that...;)
So just passing along my thoughts to help Akeeba and to ensure that those that want to use it pay for that privilege...
