fix: various fixes for log information, cryptomodule, deprecation warnings#503
Conversation
…any potential path traversal attack. added tests for the same wherever the user can provide file id/name inputs
…tions from being logged, added deprection warning on LegacyCryptoModule to aware user of potential risk, additional recommanation for using aesCbcCryptor for cryptography.
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (36)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
parfeon
left a comment
There was a problem hiding this comment.
In general I have doubts that there were any "critical security risks" which has been addressed with fixes.
| /** | ||
| * Construct crypto module with legacy cryptor for encryption and both legacy and AES-CBC | ||
| * cryptors for decryption. | ||
| * | ||
| * @deprecated Use {@link aesCbcCryptoModule} for new applications. | ||
| */ |
There was a problem hiding this comment.
Is there a need in this if it already properly deprecated in AbstractCryptoModule?
There was a problem hiding this comment.
Same as above when used in TS
| /** | ||
| * Construct crypto module with legacy cryptor for encryption and both legacy and AES-CBC | ||
| * cryptors for decryption. | ||
| * | ||
| * @deprecated Use {@link aesCbcCryptoModule} for new applications. | ||
| */ |
There was a problem hiding this comment.
Is there a need in this if it already properly deprecated in AbstractCryptoModule?
There was a problem hiding this comment.
| message: { token }, | ||
| details: 'Revoke token permissions with parameters:', | ||
| })); | ||
| this.logger.debug('PubNub', 'Revoke token permissions.'); |
There was a problem hiding this comment.
There were reasons why we printed this all out for the engineer: so later they will share logs with us and we will see whether proper value has been passed for this or another API or not.
This change will make it harder debug issues related to the PAM.
|
@pubnub-release-bot release |
|
🚀 Release successfully completed 🚀 |


refactor: omit potential use sensitive information from logs.
Logger omits potential use sensitive information to be logged.
refactor: added deprecation warning for legacy crypro module.
User will get warning while trying to configure legacy crypto module.
fix: encoding on user provided file api inputs to avoid potential path traversal attack.
encoding on user provided file api inputs to avoid potential path traversal attack.