I would like to hear some input from the Dev team.
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Księgowość
- Zapasy
- PoS
- Project
- MRP
To pytanie dostało ostrzeżenie
4
Odpowiedzi
8879
Widoki
I would like to hear some input from the Dev team.
The real reason is historical. We never thought "ok, it's a good idea to not encrypt password by default".
We implemented the plain password XML-RPC auth as it was the fastest implementation back in 2005, when our priority was to deliver our direct implementation customers asap. (and we didn't had extra budget at that time to implement several auth methods).
Since then, we have added encryption as a module "auth_crypt" as well as other authentification mechanisms; ldap, openid, oauth, etc. Every authentification mechanism is implemented by a specific module. We supplied them as optionnal modules so that everyone can choose the one he needs. We did not installed base_crypt by default as it's implementation was not compatible with ldap. (I do not know if it's still the case)
I guess we did not changed the default mode because: 1/ there is always something more important to do (the todo was trapped in the daily flow of things to do), 2/ it would have broken compatibilities for existing customers. 3/ base_crypt was not compatible with auth_ldap (but I think this should be fixed now)
Since the point 2 is not a problem anymore as we have a good migration service now, we should change the default the encrypted password in the next version.
Can anyone propose a merge proposal on the trunk branch to change the default?
Thank you for the thorough explanation.
The OpenERP developers have justified the use of plain-text passwords as a password-recovery measure:
"As for the reason for cleartext passwords: once you switch to encrypted passwords you can't recover user passwords anymore. So enabling it is a choice, because there's no going back. We don't currently plan to make passwords encrypted by default."
(from OpenERP bug #738721)
I see the point in the question, IMHO as long as you protect the PostgreSQL database and root users, you are going to be fine from a security standpoint. It's not perfect, but I would enforce security at the server level instead of the appĺication level
If you want you can install module auth_crypt (standard OpenERP module) to crypt your passwords but, after this, you can't recovery them. You can choose!
Podoba Ci się ta dyskusja? Dołącz do niej!
Stwórz konto dzisiaj, aby cieszyć się ekskluzywnymi funkcjami i wchodzić w interakcje z naszą wspaniałą społecznością!
Zarejestruj się| Powiązane posty | Odpowiedzi | Widoki | Czynność | |
|---|---|---|---|---|
|
1
lut 25
|
7402 | ||
|
1
mar 15
|
5109 | ||
|
Settings to session timeout?
Rozwiązane
|
|
17
kwi 24
|
57820 | |
|
10
gru 23
|
36323 | ||
|
2
cze 20
|
24394 |
Check this: http://help.openerp.com/question/6545/does-openerp-store-passwords-in-clear-text/
Yes I saw, my question is slightly different than that one :)
Yes it is, i am waiting for explanation too. :)
For me more crucially, why is communication using xmlrpc and not xmlrpcs by default? The nature of openerp is that it houses businesses core data, it should by nature think of security first. Users passwords are also not checked for complexity, users can happily use passwords123 in openerp, for business use, that's bad.