> In gitlabs case this is much less relevant (...)
Why, though? GitLab is often self hosted, so being able to iterate through objects, like users, can be useful for an attacker.
Why, though? GitLab is often self hosted, so being able to iterate through objects, like users, can be useful for an attacker.
As for an attacker being able to iterate through users, if that information is supposed to be private, and yet an attacker is getting anything other than a 404, then that's a problem in and of itself and my energy would be better spent fixing that.
Like I said elsewhere: it's like calling ROT13 "defense in depth".