Possibility of having a Disable File Ownership flag

I haven't found any better place to post this so I'm going to open this issue to at least get some clarity.

I have been fighting against my operating system to let me change the permissions of the config file but it seems that it's impossible (at least trying to do what I am). My issue/question however is why there isn't a --disable-security-checks flag to skip the checking of the key/config permissions. Since it's such an old project I'm sure that I'm not the first that has wondered this but I can't find anywhere that says why it's not going to be added.

The flag could trigger a !! WARNING !! that gets printed every time it gets used to warn the user. But outright disabling the option to even use ssh if the files aren't secured properly makes it impossible for anyone that doesn't have the ability to change the file permissions.

I'm more wondering what the design ethos is and why this hasn't been added or at least discussed? (I have found a few posts talking about it but so far its has been just saying "No you can't")

If this is not the place to ask this question it would be nice to know where design discussions for this project take place.

Cheers

No file or test is named. Start by locating the existing key and config permission checks and the command-line option handling, then review the project's security rationale and prior discussion. Done means reaching a documented decision about whether an override flag belongs in the project and what warning behavior it requires.