Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

question: Validation of list in ID command #400

Open
duesee opened this issue Dec 7, 2023 · 0 comments
Open

question: Validation of list in ID command #400

duesee opened this issue Dec 7, 2023 · 0 comments
Labels
misuse Violation of misuse-resistance question Further information is requested

Comments

@duesee
Copy link
Owner

duesee commented Dec 7, 2023

RFC 2971 tells us that ...

  • "Strings are not case-sensitive."
  • "Implementations MUST NOT send the same field name more than once."

... and that ...

  • "Field strings MUST NOT be longer than 30 octets."
  • "Value strings MUST NOT be longer than 1024 octets."
  • "Implementations MUST NOT send more than 30 field-value pairs."

I'm not sure what to do with this information, really. Sure, we could enforce all of this. But... does that mean we reject longer, dulicate, or too much fields?

I'm leaning towards not doing anything of this until there is a good reason. Resource exhaustion probably needs to be handled more generically, anyway?

If we want to do this, we probably should use a wrapper struct that holds a hash-map.

Dovecot (out of curiosity)

A ID ("012345678901234567890123456789" "")
* ID ("name" "Dovecot")
A OK ID completed.
A ID ("012345678901234567890123456789X" "")
A BAD Invalid ID parameters

A ID ("name" "A" "name2" "B")
* ID ("name" "Dovecot")
A OK ID completed.
A ID ("name" "A" "name" "B")
* ID ("name" "Dovecot")
A OK ID completed.
@duesee duesee changed the title question: ID validation question: Validation of list in ID command Dec 7, 2023
@duesee duesee added question Further information is requested misuse Violation of misuse-resistance labels Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
misuse Violation of misuse-resistance question Further information is requested
Projects
Status: No status
Development

No branches or pull requests

1 participant