Add Dropbox Access Token rule

[gemesa]

No description provided.

[bradlarsen]

This looks really good. A couple things:

• In this new rule, there is a funny interaction between the payload character class and the word boundary anchor at the end.
• I did some investigation, and I believe the payload length can actually be more flexible than always 140 characters, and occurrences in the wild seem to range from 130 (maybe 135, actually) to 151 characters.

Thank you again @gemesa!

[gemesa]

This looks really good. A couple things:

* In this new rule, there is a funny interaction between the payload character class and the word boundary anchor at the end.

* I did some investigation, and I believe the payload length can actually be more flexible than always 140 characters, and occurrences in the wild seem to range from 130 (maybe 135, actually) to 151 characters.

Thank you again @gemesa!

Good findings, I have applied your suggestions. What I usually do is generate a few API tokens myself and observe the patterns. For me they have always been 140 characters long and I did not do any further investigation. I will also keep in mind the edge case where the tokens end with -.

[bradlarsen]

What I usually do is generate a few API tokens myself and observe the patterns. For me they have always been 140 characters long and I did not do any further investigation.

Yes, that's a very reasonable approach! Doing so should lead to high-precision rules.