-
Notifications
You must be signed in to change notification settings - Fork 48
Open
Open
Copy link
Labels
S-needs-triageRequires initial triage or categorizationRequires initial triage or categorizationT-featureSuggests a new feature or enhancementSuggests a new feature or enhancementT-securitySecurity vulnerabilities or related fixesSecurity vulnerabilities or related fixes
Description
Describe the feature
Issue
- Currently relayer connections only supports
redis://protocol communication with redis (unsecured connections). Data is transmitted without encryption, making it suitable for local development or trusted networks but vulnerable to interception in untrusted environments.
Feature
- Support Redis encryption and connection to relayer service via TLS.
- Create example that uses Redis encrypted connection in examples dir.
- Create Security Recommendations docs page. Mention that using encrypted Redis is recomended for production systems.
- Add note to all existing examples to point to Security Recommendations docs page.
- Make sure your test runs with both self hosted of redis server (running locally, aws ecs etc ) and using managed service of redis ( eg. aws elasticache )
Metadata
Metadata
Assignees
Labels
S-needs-triageRequires initial triage or categorizationRequires initial triage or categorizationT-featureSuggests a new feature or enhancementSuggests a new feature or enhancementT-securitySecurity vulnerabilities or related fixesSecurity vulnerabilities or related fixes