[TYPO3-project-4-3] Making RSA Auth default login method?

[Dmitry Dulepov]

Hi!

Michael Stucki wrote:
> Settings in $TYPO3_CONF_VARS can easily be changed globally, but any EM
> configuration or action requires the same steps for every installation.

That's correct but I will feel more secure if my keys do not go to the same directory as somebody else keys :) On my servers I even set up different PHP session directories for different vhosts.

> For example, in the "rsaauth" extension, the path for the temporary keys
> would make full sense if it becomes a TYPO3_CONF_VARS setting. I think
> it could be used by many other features too.

Yes, I thought about it. I decided on the extension configuration instead. Using TYPO3_CONF_VARS may lower the security a little because adding another member of TYPO3_CONF_VARS requires a simple editing of localconf.php. Altering extension data in localconf.php is harder because it is a serialized array.

> Thinking about this, I start dreaming of a commandline-interface for the
> extension manager... :-)

I always dream about t3shell :D Just imagine:

================
typo3> installext -?
Syntax: installext [-autodb] [-autoupdate] -[[no]clearcache] extkey
Success.

typo3> installext -autodb rsa
Extension "rsa" is not found.
Error.

typo3> installext -autodb rsaauth
Extension "rsaauth" is installed.
Database is updated.
Success.

typo3> set -ext rsa -opt temporaryPath -value "/whatever"
Success.

typo3> get -conf -opt BE:loginSecurityLevel
superchallenged
Success.

typo3> set -conf -opt BE:loginSecurityLevel -value rsa
Success.

================

-- 
Dmitry Dulepov
In TYPO3 blog: http://dmitry-dulepov.com/reviews/magento-beginners-guide-by-william-rice.html
LinkedIn: http://www.linkedin.com/in/dmitrydulepov
Twitter: http://twitter.com/dmitryd
Skype: liels_bugs