Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

Investigate client reports of invalid salt #1418

Open
jrconlin opened this issue Jul 17, 2020 · 0 comments
Open

Investigate client reports of invalid salt #1418

jrconlin opened this issue Jul 17, 2020 · 0 comments
Labels
3 Estimate - m - This is a small change, but there's some uncertainty.
Projects
Services Engineering

Comments

@jrconlin
Copy link
Member

See mozilla/application-services#3365

I get the feeling this may be a problem with the subscriber providing zero length or empty salts. Depending on the encryption format, these can be contained in the delivered message. I'm not sure if the server should filter these invalid messages out.
@jrconlin jrconlin added the 3 Estimate - m - This is a small change, but there's some uncertainty. label Jul 17, 2020
@jrconlin jrconlin added this to Backlog: Misc in Services Engineering via automation Jul 17, 2020
@tublitzed tublitzed moved this from Backlog: Misc to Backlog: Push in Services Engineering Aug 21, 2020
@jrconlin jrconlin mentioned this issue Oct 12, 2020
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
3 Estimate - m - This is a small change, but there's some uncertainty.
Projects
Services Engineering
  
Backlog: Push
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jrconlin