[FIX] l10n_es_bank_statement: Sustituir utilizacion de eval por safe_eval #190
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Gracias por el cambio. Efectivamente, así es más seguro. 👍 |
pedrobaeza
added a commit
that referenced
this pull request
Jun 25, 2015
[FIX] l10n_es_bank_statement: Sustituir utilizacion de eval por safe_eval
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Con este commit se pretende sustituir el uso de la función eval, que es insegura por defecto, por la función safe_eval proporcionada por OpenERP.
Así se evitaría que cualquier usuario pueda ejecutar código modificando el campo OBI de las líneas de extractos bancarios.