I often have the situation where I use rushlink without the requirement of having a short URL. Moreover, in some of these cases, I would rather have a URL that is resistant to enumeration attacks.
I propose that we allow a flag "entropy", with a number as argument, or a boolean "high-entropy" value, that will instruct the server to generate a key with a minimum amount of entropy. I would propose a very conservative 96 bits, which is equivalent to keys of 16 characters.
I often have the situation where I use rushlink without the requirement of having a short URL. Moreover, in some of these cases, I would rather have a URL that is resistant to enumeration attacks.
I propose that we allow a flag "entropy", with a number as argument, or a boolean "high-entropy" value, that will instruct the server to generate a key with a minimum amount of entropy. I would propose a very conservative 96 bits, which is equivalent to keys of 16 characters.
Update: because of the way keys are encoded, every character adds 5 bits of entropy. If we take a key of 16 characters, we still have 80 bits of entropy, which should be fine.
Update: because of the way keys are encoded, every character adds 5 bits of entropy. If we take a key of 16 characters, we still have 80 bits of entropy, which should be fine.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I often have the situation where I use rushlink without the requirement of having a short URL. Moreover, in some of these cases, I would rather have a URL that is resistant to enumeration attacks.
I propose that we allow a flag "entropy", with a number as argument, or a boolean "high-entropy" value, that will instruct the server to generate a key with a minimum amount of entropy. I would propose a very conservative 96 bits, which is equivalent to keys of 16 characters.
Allow requesting of high-entropy URL keysto Allow uploading with high-entropy URL keysUpdate: because of the way keys are encoded, every character adds 5 bits of entropy. If we take a key of 16 characters, we still have 80 bits of entropy, which should be fine.
Fixed by
6d3e8028cb.