News for hackers. Stuff that matters.
Re:Most “mandatory requirements” in corporations are imaginary by sfifs on Wednesday August 19, 2020 @05:48AM (#24208727)
In BigCorps, if there's a stupid requirement, there's usually a reason for the stupid requirement to be there in the first place but getting to the reason might require un-peeling a few org layers to since the people enforcing the policy will not be the people who wrote the policy. A more productive use of time would be to understand the reason for the policy, document out why it doesn't apply to your case and then attempt to get approval.

For instance, there's a restriction at my workplace (not a software company, a regular old industry fortune 500) which prevents git installs from pushing to any non corporate GitHub repo from our work machines.

The obvious reason it exists is to prevent people (a lot of who are analysts or data scientists - not professional programmers) from shooting themselves in the foot by pushing code to their personal repos in error.

It's annoying to work around if you need to say push a contribution to an open source project and you could rage at the infosec for enforcing it - but it obviously exists because stupid errors would have happened.

This principle is also called Chesterton's fence

https://en.m.wikipedia.org/wiki/Wikipedia:Chesterton%27s_fen...

Re:Most “mandatory requirements” in corporations are imaginary by rvense on Wednesday August 19, 2020 @10:34AM (#24210774)
About five years ago, a place I was working at was selecting a new laptop for all employees. Mine was up for replacement, so I was interested in what they were picking. They'd arrived at some god-awful Lenovo gamer model. It fit the performance and price point they'd decided they needed.

I said I'd prefer to have something smaller with less Christmas lights.

"Policy is everyone has to have the same laptop, and some people need more graphics power than the one you're asking for."

Turns out there'd been some big thing back and forth already about size and performance and this was the compromise that nobody liked.

"But why does everyone have to have the same laptop?" I asked.

"Well, it's just policy. Every desk has a docking station, and we don't want to have to buy different ones."

So I flipped the selected monstrosity over to reveal the extremely lacking docking connector at the bottom. There were some awkward laughs and I got my Thinkpad.

Re:Most “mandatory requirements” in corporations are imaginary by grogenaut on Wednesday August 19, 2020 @12:44PM (#24212486)
This is literally my job. Amazon calls it Dive Deep/Earn Trust. I get called in constantly to "Remove Blockers". Part of it is just understanding why the policy exists and then getting a policy modification. While it's definitely an art, it's not as hard as a lot of people think, but you can't be afraid to escalate.
Re:Most “mandatory requirements” in corporations are imaginary by pyrale on Wednesday August 19, 2020 @05:42PM (#24216986)
It is also _much_ easier when you're called in for that purpose. Someone who didn't get that mandate on hire will be considered troublesome and overstepping, while someone roped in for that reason will be innovative and an enabler.
Re:Most “mandatory requirements” in corporations are imaginary by grogenaut on Wednesday August 19, 2020 @08:55PM (#24218729)
I actually grew into this position. And like 60% of the time people don't ask me to show up, I just do. Or someone points me at an issue.
Re:Most “mandatory requirements” in corporations are imaginary by pyrale on Thursday August 20, 2020 @03:59AM (#24220944)
Sounds like some companies got it right, then. I wwould advise figuring out which company one is in before agitating for policy change though.
Re:Most “mandatory requirements” in corporations are imaginary by Anthony-G on Thursday August 20, 2020 @06:43AM (#24221872)
You sound like a cross between the The Littlest Hobo and The A-Team. :)

https://en.wikipedia.org/wiki/The_Littlest_Hobo

https://en.wikipedia.org/wiki/The_A-Team

Re:Most “mandatory requirements” in corporations are imaginary by Kinrany on Wednesday August 19, 2020 @01:12PM (#24212886)
This sounds like an awesome job. Literally paid to fix frustrating bureacratic processes.

Like a professional user advocate paid to convince developers that the users do have a point and the request is not impossible.

Re:Most “mandatory requirements” in corporations are imaginary by grogenaut on Wednesday August 19, 2020 @08:57PM (#24218742)
Do you like firefighting and having uncomfortable conversations with people all the time.
Re:Most “mandatory requirements” in corporations are imaginary by wayanon on Thursday August 20, 2020 @04:08AM (#24221019)
Is this basically a Business Analyst?
Re:Most “mandatory requirements” in corporations are imaginary by grogenaut on Thursday August 20, 2020 @08:44PM (#24230705)
Principal Engineer
Re:Most “mandatory requirements” in corporations are imaginary by Terretta on Wednesday August 19, 2020 @10:55PM (#24219397)
Welp, I need more of yous than two pizzas would feed.
Re:Most “mandatory requirements” in corporations are imaginary by kill_nate_kill on Wednesday August 19, 2020 @11:30PM (#24219589)
Shit, that's like .8 of me.
Re:Most “mandatory requirements” in corporations are imaginary by brokenmachine on Thursday August 20, 2020 @01:53AM (#24220316)
I'd rather poke both my eyes out than do that awesome job.
Re:Most “mandatory requirements” in corporations are imaginary by m463 on Thursday August 20, 2020 @12:53AM (#24220017)
> it's not as hard as a lot of people think

It never is after you've done it once.

It's hard for people to scope an unknown task - especially dealing with bureaucracy. Is it going to be easy peasy, or will the rabbit hole just keep getting deeper.

Additionally, the ROI for an employee to investigate things like this is not very high, or could be negative. Imagine a poor H1B person - whose life and future depends on a company - trying to chase little things like this down. ("it's ok, I don't need " an ssd; an ergonomic chair; a 17" monitor is fine; etc...)

you're doing good work.

Re:Most “mandatory requirements” in corporations are imaginary by beastcoast on Wednesday August 19, 2020 @04:26PM (#24215913)
It also helps that Amazon isn’t afraid to entertain ideas from lower in the ranks. You just need a strong idea and be willing to write a memo that explains it, then work your way up the chain until you get to a decision maker.
Re:Most “mandatory requirements” in corporations are imaginary by grogenaut on Wednesday August 19, 2020 @08:56PM (#24218733)
I've seen new hire SDE1's call out jassy in an aws allhands. And jassy seriously answers those questions. Very impressive.
Re:Most “mandatory requirements” in corporations are imaginary by waheoo on Wednesday August 19, 2020 @01:14PM (#24212908)
More people need to read "the goal."
Re:Most “mandatory requirements” in corporations are imaginary by vpilcx on Wednesday August 19, 2020 @03:07PM (#24214751)
Who's the author? There's three different books with that title on Amazon.
Re:Most “mandatory requirements” in corporations are imaginary by mikaraento on Wednesday August 19, 2020 @03:16PM (#24214888)
Eliyahu M. Goldratt

And yes, everybody should read it.

Re:Most “mandatory requirements” in corporations are imaginary by kozak on Wednesday August 19, 2020 @03:15PM (#24214866)
Eliyahu M. Goldratt
Re:Most “mandatory requirements” in corporations are imaginary by Bootwizard on Wednesday August 19, 2020 @11:24AM (#24211314)
I did almost exactly the same thing at my last job. I'm a game dev and they provided us all with woefully underpowered MacBooks that didn't even have a dedicated GPU. The game engine was constantly crashing while working and making it very difficult to get anything done. I recorded the amount of time wasted on these crashes over the course of a week.

I then proved to management that there was about 5 hours a week being completely wasted for me waiting for my machine to open applications after they crash. So after that we all got new MacBooks that were properly spec'd out for game development. I got to pick the specs :)

Re:Most “mandatory requirements” in corporations are imaginary by VHRanger on Wednesday August 19, 2020 @11:43AM (#24211603)
Why would anyone ever do game development on Apple hardware?

You're making iOS games?

Re:Most “mandatory requirements” in corporations are imaginary by mcraiha on Wednesday August 19, 2020 @12:10PM (#24212006)
Yes, iOS cross compile is a pain. And Unity is a bit more stable in Macs (YMMV).
Re:Most “mandatory requirements” in corporations are imaginary by VHRanger on Wednesday August 19, 2020 @12:33PM (#24212331)
Yeah this part is something that annoys me but lots of the Unity team is working on macbooks, even though it's only a relevant platform for iOS as far as the end user is concerned.
Re:Most “mandatory requirements” in corporations are imaginary by JJMcJ on Wednesday August 19, 2020 @02:23PM (#24214026)
> So after that we all got

laughed at and told to stay later and work weekends.

At far too many companies.

Re:Most “mandatory requirements” in corporations are imaginary by Doxin on Thursday August 20, 2020 @05:13AM (#24221388)
At which point you go "Fuck you pay me" presumably? Or am I alone in pushing back at underpaid overtime?
Re:Most “mandatory requirements” in corporations are imaginary by JJMcJ on Thursday August 20, 2020 @02:45PM (#24226967)
> am I alone

There isn't enough pushback, unfortunately.

Re:Most “mandatory requirements” in corporations are imaginary by robbyking on Wednesday August 19, 2020 @11:55AM (#24211779)
I had the opposite experience once: at my previous company we were all issued mid-tier ThinkPads. Completely out of the blue we all received an email saying we'd be given a set budget and would be able to choose any machine we wanted. We went from 100% Windows to about 80% OS X within a week. They ended up giving the old ThinkPads away. (I put Ubuntu on one and gave it to my mom.)

This was in 2012 or so, and because of that I was able to learn Objective-C and go on to work on the first version of our native app. It made me a stronger engineer, and allowed the company to have developers who were already familiar with the product and backend services work on native. It was win-win.

Re:Most “mandatory requirements” in corporations are imaginary by jimmaswell on Wednesday August 19, 2020 @01:32PM (#24213230)
That many people willingly moved to OSX? Why? Was it a graphics company?
Re:Most “mandatory requirements” in corporations are imaginary by pak9rabid on Wednesday August 19, 2020 @02:06PM (#24213748)
OSX is great at getting the fuck out of the way and letting you get more work done in my experience (development work).
Re:Most “mandatory requirements” in corporations are imaginary by Shared404 on Wednesday August 19, 2020 @03:41PM (#24215255)
I think it's just what you're used to.

Put me in front of a Linux desktop, and I can just start working.

Put me in front of a Windows desktop, give me 30 minutes to set up what I need, and I can start working.

Put me in front of a Mac, and come back to me still yelling at it five hours later.

I'm sure I could learn if it was worth the time to me, but I definitely wouldn't argue that it's superior (for me personally at least).

Re:Most “mandatory requirements” in corporations are imaginary by eitland on Wednesday August 19, 2020 @04:02PM (#24215548)
Yes it is really individual: I have an ex-colleague who was a linux super-user and awesome sysadmin but moved to Mac for his development laptop. He loved Mac, and couldn't stand the hassle of Linux anymore as far as I understood him.

This confused me a lot as even though I wasn't even close to his level at that time I had no problems living with my Linux machines while my Mac laptop used to drive me crazy every day with some nonsense.

Turns out it is extremely individual. Maybe it is because I'm a keyboard person. When I work efficiently I feel I rarely touch the touchpad. I use fullscreen a lot, I sometimes use virtual desktops a lot etc.

Re:Most “mandatory requirements” in corporations are imaginary by robbyking on Wednesday August 19, 2020 @04:13PM (#24215687)
Enabling "Use keyboard navigation to move focus between controls" makes keyboard navigation much, much easier on macOS.
Re:Most “mandatory requirements” in corporations are imaginary by Shared404 on Wednesday August 19, 2020 @09:53PM (#24219072)
You may be on to something with the keyboard idea.

I've always used i3/Sway/Pop!_Shell, or just dealt with windows subpar tiling. I'm picky about terminals as well, so that may have something to do with it. Although Mac's shell is nicer than windows (obviously), I can't stand the built in terminal app.

Re:Most “mandatory requirements” in corporations are imaginary by m463 on Wednesday August 19, 2020 @09:54PM (#24219083)
I think my productivity graphs would look like:

  |          22  <- linux
  |        22
  |  1111121111  <- macos
  | 1   22
  |1  22
  |122
  |000000000000  <- windows
  -------------
Re:Most “mandatory requirements” in corporations are imaginary by m463 on Wednesday August 19, 2020 @09:51PM (#24219057)
It has been getting in the way more and more.

The only good news would be... if apple decides to "reverse course" questing for non-discerning-consumers, all the "crazy ones" will breathe a sigh of relief and buy a pile of new hardware.

I remember when apple gave up on its "apple-inward-looking" powerpc hardware and shipped intel machines. All of a sudden apple machines could run windows too, people could see more possibilities buying apple and the market for apple hardware became much larger very quickly.

Re:Most “mandatory requirements” in corporations are imaginary by kergonath on Wednesday August 19, 2020 @03:44PM (#24215299)
OS X is a great platform, less frustrating to use than Windows, with lots of well-designed GUI apps, a true MS Office, and a whole UNIX under the hood.
Re:Most “mandatory requirements” in corporations are imaginary by rubatuga on Wednesday August 19, 2020 @02:07PM (#24213770)
It was before WSL
Re:Most “mandatory requirements” in corporations are imaginary by EVdotIO on Wednesday August 19, 2020 @02:57PM (#24214605)
Yes, while WSL2 has some filesystem quirks, it works pretty darn well for what I do (ruby development). I picked up a 5 Y/O 2 CPU E5 v4 Xeon workstation for 300 bucks. I've sunk in an additional 400 for an SSD, RAM and GPU, and when paired with Microsoft Remote Desktop, I've got a solid setup that allows the best of all worlds.
Re:Most “mandatory requirements” in corporations are imaginary by TimTheTinker on Wednesday August 19, 2020 @03:13PM (#24214848)
If ruby development is your gig, and especially if Linux is your target runtime environment, I don't understand why you'd choose anything other than Linux, unless the choice was made for you.

Speaking as a web dev on a company-issued Mac, running my local dev environment inside a Parallels Linux VM. I asked to switch to Linux but was turned down.

(Now if Microsoft released LSW, i.e. an Ubuntu-based distro with Windows syscall support via a KVM-hosted NT kernel, I very well might opt for that instead.)

Re:Most “mandatory requirements” in corporations are imaginary by EVdotIO on Wednesday August 19, 2020 @05:38PM (#24216938)
Obviously back in the day windows was an absolute dog for any dev work outside of windows, and a complete no go. I've only started using it for development a few months now, but so far haven't encountered any major issues. Maybe I'll run into some interoperability problems with specific syscalls at the compatibility layer, but so far it largely just works for my needs (VS Code with intellisense and debugging, docker, K8S, Zsh and few other tools). If my tests pass locally, I can safely assume they pass on the CI server, and haven't been proven wrong so far. If I ever need a linux box, there's an old laptop that's just for that. At this point it's turtles all the way down, what's the harm adding another turtle on top.

It's not all roses, there is a noticeable performance hit with the filesystem in both WSL and the windows layer. I wouldn't use it for production, and why would you, but for development, it's fine and largely not a problem. If you had to regularly deal with a large numbers of files, say log parsing or compiling, it's probably not going to work.

Besides recent OS X SSL library issues, I've haven't ever run in problems developing on a Mac and have used one for the better part of 10 years now. Can't say the same with developing on Linux (almost exclusively on the graphics side of things, but that's a problem when it's your primary machine).

Re:Most “mandatory requirements” in corporations are imaginary by jimmaswell on Wednesday August 19, 2020 @04:31PM (#24215985)
msys2 et al always did fine for me
Re:Most “mandatory requirements” in corporations are imaginary by db48x on Wednesday August 19, 2020 @01:39PM (#24213322)
Never underestimate the power of marketing.
Re:Most “mandatory requirements” in corporations are imaginary by lostmsu on Wednesday August 19, 2020 @01:53PM (#24213548)
Are MacBooks any good for graphics? :-O
Re:Most “mandatory requirements” in corporations are imaginary by robbyking on Wednesday August 19, 2020 @04:10PM (#24215647)
It was Hotwire.com.
Re:Most “mandatory requirements” in corporations are imaginary by simonebrunozzi on Wednesday August 19, 2020 @11:01AM (#24211046)
I can only imagine the grin on your face :)
Re:Most “mandatory requirements” in corporations are imaginary by the8472 on Wednesday August 19, 2020 @07:21AM (#24209225)
> but getting to the reason might require un-peeling a few org layers to since the people enforcing the policy will not be the people who wrote the policy.

The issue is that all the policy documents often only contain the One True Way to achieve their goals, while the goals remain unstated. The documents should always come with a rationale. And appending "exceptions may be granted for equivalent or better processes" to requirements would also help. I was faced with a password "security policy" that pretty much only whitelisted SHA2 + salting for password hashing. We were using a time-hard (not memory-hard though) password hashing function instead and several levels of auditors were effectively asking us to downgrade to comply with their policy without even understanding the difference.

It's terribly demotivating to have to argue with people enforcing policy they do not understand and erodes any willingness to engage with those policies instead of seeing them as theater and working around them.

Re:Most “mandatory requirements” in corporations are imaginary by hnick on Wednesday August 19, 2020 @09:37AM (#24210209)
> The issue is that all the policy documents often only contain the One True Way to achieve their goals, while the goals remain unstated. The documents should always come with a rationale.

A reason can be argued against while a policy must just be followed. It's probably by design, because as soon as you put a reason that becomes a target and people start to get ideas about why it doesn't apply to them. Much like when web companies disable your account and won't say exactly why. Not gonna take the risk you prove them wrong, are they?

It would be nice though if all laws had a purpose included.

Re:Most “mandatory requirements” in corporations are imaginary by fjwefjh on Wednesday August 19, 2020 @12:14PM (#24212068)
Or policy writers copy n pasted something off web.

In my Mega Tech corp, we have security team that has created hodge podge of conflicting policies. For example, they ask some applications to be internal network only and other are accessible via web. But they can never provide their reasoning and get annoyed when we ask any details.

The worst part is that some of their policies directly contradict with each other. For example, policy is to never run as root inside docker container but then there are some applications provided by them that runs as root in docker. And every time you use it, you have to remind them that these are their apps or else they will ask you to stop running it as root.

Finally, I had pleasure of talking with one of their Security and Compliance expert. They could not even knew how to list file perms in Linux, and other a lot of basic ideas. This person clearly had memorized interview questions but had clearly no understanding of those concepts.

Only way to hide their incompetence is act elite and don't explain their reasoning.

Re:Most “mandatory requirements” in corporations are imaginary by dragonwriter on Wednesday August 19, 2020 @11:11PM (#24219489)
> Or policy writers copy n pasted something off web.

The fact that policy sponsors are more than anything looking to a single answer to end debate and establish uniformity is why policy writers can copy and paste stuff from the web and get it adopted as policy without a clear rationale connected to the organization’s particular circumstances. They aren't conflicting, alternative explanations.

Re:Most “mandatory requirements” in corporations are imaginary by thaumasiotes on Wednesday August 19, 2020 @11:08AM (#24211123)
> It's probably by design, because as soon as you put a reason that becomes a target and people start to get ideas about why it doesn't apply to them.

There's more to it than that. There are two separate groups of reasons:

1. The reasons a policy was put in place. ("Why did we do this?")

2. The reasons a policy succeeds. ("Why is this a good idea?")

You can know the reasons in group 1. But nobody cares about those. What matters are the group 2 reasons, and they were probably never known in the first place.

Re:Most “mandatory requirements” in corporations are imaginary by hinkley on Wednesday August 19, 2020 @12:01PM (#24211860)
I was working in a throughout computing problem domain. About the time I got there, some asshole in HR had everyone’s (current and former employees) tax information on their work laptop and lost it. Tens of thousands of people, because there was no policy against putting such information on portable equipment.

And as far as I’m aware there still isn’t. No, within the year (might have been a lawsuit, I can’t recall) new policy became everyone’s machine has whole disk encryption. Including engineering. So my software was instantly 30% slower, and a half a day added to setting up any new machine. I don’t know how many times I had to explain that it’s not our code that got slower, the whole company got slower. It took me months of work to get us back to zero.

That person should have been run off and anyone in their dept caught doing the same should have been put on probation. I don’t know how you figure that it’s “fair” for everyone to suffer for the mistakes of one member. In a small team setting? Perhaps. But not for something like this.

Re:Most “mandatory requirements” in corporations are imaginary by compiler-guy on Wednesday August 19, 2020 @02:35PM (#24214250)
Thinking about the policy in terms of punishments and fairness isn’t the right approach. Something happened that cost the company a great deal of resources, so the company is trying to prevent such a thing from happening again.

It may be doing a poor job at that, but it isn’t punishing you and it isn’t about fairness. It’s trying to prevent a future mistake. And because the company is a single entity, it is the company choosing to bear the cost.

It may make your job harder and they may not modify its expectations properly after imposing this cost on you, but that isn’t punishment or fairness. It is poorly thought out systems.

Re:Most “mandatory requirements” in corporations are imaginary by hinkley on Wednesday August 19, 2020 @05:40PM (#24216969)
"Something must be done. This is something, so we will do it."
Re:Most “mandatory requirements” in corporations are imaginary by hnick on Wednesday August 19, 2020 @07:49PM (#24218260)
I don't know if encryption was the right policy response here (it seems to be a very good idea regardless due to theft/hacking possibilities), but I'm OK with this sort of policy sometimes.

Full disk encryption is a fair response because it won't be feasible to enumerate every type of situation that results in sensitive data being put on the laptop (such as temporary files or source code). If someone was going to just add tax numbers to a list it leaves a lot out; if they say "sensitive data" it leaves a lot open to interpretation; if they list everything they can think of it'll be impossible to properly comply while still getting work done.

So perhaps it was a heavy handed approach handed down mindlessly, but it could also have been someone looking at the bigger picture. Knowing the intent as others said would help.

Re:Most “mandatory requirements” in corporations are imaginary by sciurus on Wednesday August 19, 2020 @08:11PM (#24218415)
You act like this policy was intended as punishment instead of as risk mitigation.

Mandating full disk encryption is easy for IT to enforce. A policy of not putting sensitive information on laptops is valuable, but difficult to enforce. Encryption is a sound way to reduce the risk of harm when that policy is inevitably broken.

Full disk encryption also been the company-wide policy of everywhere I've worked in recent memory, fwiw.

Re:Most “mandatory requirements” in corporations are imaginary by moonbug on Wednesday August 19, 2020 @03:59PM (#24215511)
so your job involved none of the company's IP?
Re:Most “mandatory requirements” in corporations are imaginary by jt2190 on Wednesday August 19, 2020 @12:02PM (#24211884)
I’d add another that’s nice to have:

3. The outcome we expect. (“What will happen if this is working.”)

Re:Most “mandatory requirements” in corporations are imaginary by IncRnd on Wednesday August 19, 2020 @01:40PM (#24213339)
How does that differ from choice #1, 'The reasons a policy was put in place. ("Why did we do this?")'?

A policy's expected outcome is correlated with why a policy was put in place.

Re:Most “mandatory requirements” in corporations are imaginary by the8472 on Wednesday August 19, 2020 @06:09PM (#24217316)
A policy might be put into place because a single event. The expected outcome can drastically differ depending on who writes the policy. E.g. it could be "this type of attack won't succeed again" vs. "even if this or a similar kind of attack succeeds it won't expose our entire data"
Re:Most “mandatory requirements” in corporations are imaginary by IncRnd on Wednesday August 19, 2020 @06:17PM (#24217410)
That's my exact point. A policy isn't random but created for an effect.

As an examnple: If an HN disclosure leaks passwords and email addresses into the public domain, imposing a policy control is _meant_ to have the effect that such a disclosure would not happen again, or if it does to have a limited scope.

Re:Most “mandatory requirements” in corporations are imaginary by whatshisface on Wednesday August 19, 2020 @10:06AM (#24210471)
On the other hand, a reason can convince people, while a policy can be avoided, worked around or ignored while creating zero feelings of guilt.
Re:Most “mandatory requirements” in corporations are imaginary by ardy42 on Wednesday August 19, 2020 @10:48AM (#24210924)
> On the other hand, a reason can convince people, while a policy can be avoided, worked around or ignored while creating zero feelings of guilt.

Though, I'd imagine that, in many cases, adding reasons would turn a policy pamphlet into a textbook.

This seems like one of those areas where there are unavoidable tradeoffs:

* clear, concise, and rigid policies are easy to communicate and enforce, but frustrate people with better ideas.

* clear, concise, and flexible polices invite a lot of noise from people who think they know more than they do (e.g. can I use my own custom password hash I invented? It has more bits so it must be more secure.). Enforcement is also harder, since now you have to track exceptions.

* policy reasoning is harder to communicate, may never get read, and may actually discourage reading the policy.

Re:Most “mandatory requirements” in corporations are imaginary by whatshisface on Wednesday August 19, 2020 @10:53AM (#24210973)
You could have one pamphlet with the policy, and a separate book with the reasoning, and instruct people to check the book when proposing a change or exception. Then all of the lazy compliant people could have their brevity, and the crackpots and geniuses would both get the explanatory text they needed.
Re:Most “mandatory requirements” in corporations are imaginary by dragonwriter on Wednesday August 19, 2020 @11:26PM (#24219571)
> You could have one pamphlet with the policy, and a separate book with the reasoning, and instruct people to check the book when proposing a change or exception

Very often part of the purpose of the policy is to end debate about how to handle an issue, and to get the “crackpots and geniuses” to STFU.

That's not a motivation that policy sponsors usually want in print, though.

Re:Most “mandatory requirements” in corporations are imaginary by ardy42 on Wednesday August 19, 2020 @12:50PM (#24212575)
> You could have one pamphlet with the policy, and a separate book with the reasoning, and instruct people to check the book when proposing a change or exception.

That's still a significant trade-off: putting together a book with the reasoning would be a lot more expensive than just creating the pamphlet. Your organization might not be able to afford the cost, period, or your boss may not agree to spend all that money just to make a minority of engineers happy in a few narrow cases. Then there's the question of how many people would actually consult the book of rationales; maybe it'd only be a handful.

I'm guessing most organizations tend to pursue a "minimum viable policy" tradeoff: spend as little effort as possible to create a policy that addresses a particular set of high-priority problems (since that is easily justifiable), and ignore more theoretical concerns like worker education and the personality preferences of certain kinds of individuals.

Re:Most “mandatory requirements” in corporations are imaginary by whatshisface on Wednesday August 19, 2020 @12:55PM (#24212649)
I'd explain why you're misconceiving the tradeoff, but we have a policy against omitting policy rationales, and that's that. ;)

>Then there's the question of how many people would actually consult the book of rationales; maybe it'd only be a handful.

Well, it's supposed to only be a handful: the handful of people who know more than the policymaker.

Re:Most “mandatory requirements” in corporations are imaginary by hinkley on Wednesday August 19, 2020 @12:05PM (#24211912)
It’s almost as if there is no single technique for reaching all members of a target audience...

You need two documents, minimum. One with rules, others to justify them.

Re:Most “mandatory requirements” in corporations are imaginary by dragonwriter on Wednesday August 19, 2020 @11:20PM (#24219541)
> On the other hand, a reason can convince people,

Policies very often have official reasons for just this propaganda purpose, but it's worth noting that the reasons cited for the purpose of motivating compliance are often chosen for the specific purpose of how well they are anticipated to motivate compliance and not how well they reflect the actual reasons the policy is adopted, and thus they often are not in practice a good tool for understanding how to challenge the policy effectively.

Re:Most “mandatory requirements” in corporations are imaginary by hnick on Wednesday August 19, 2020 @08:16PM (#24218456)
I think it depends on the person. For myself (and probably many people with the hacker mindset), I don't like useless rules and want a justification or I tend to think I "know better" which is of course sometimes true and sometimes not.

I used to think this was a rebellious streak but perhaps it's just from that desire to know how things work. Absent a reason, I'll find my own.

A lot of people don't care either way, rules make life simple so there's no need to complicate it further.

Re:Most “mandatory requirements” in corporations are imaginary by dragonwriter on Wednesday August 19, 2020 @11:09PM (#24219472)
> A reason can be argued against while a policy must just be followed.

And if you talk to people directing policy efforts (who are often not the ones writing, or even actively choosing, policy but generally are the ones formally signing off), you often don't have to dig very far to find that settling discussions is as important of a rationale for the policy as any of the others. This obviously conflicts with ideals like continuous improvement, but it's true lots of places including those with nominal commitments to continuous improvement.

Re:Most “mandatory requirements” in corporations are imaginary by pavon on Wednesday August 19, 2020 @12:05PM (#24211915)
There is also the concern of letting perfect be the enemy of good. For every developer that correctly integrates a better password storage scheme, there will be dozens that use something worse. Consistently standardizing on something that is good enough might be a net win and avoid the overhead and risk of verifying that other approaches are as good or better. Easier to evaluate/amend the policy periodically than to evaluate every single password storage instance.

This is a common issue in policies. If you try to accommodate every possible situation then the policy becomes incredibly complicated and difficult to understand let alone follow. If you have a simple policy that is easy to understand, there will inevitably be exceptions where the policy doesn't make sense.

Re:Most “mandatory requirements” in corporations are imaginary by edoloughlin on Wednesday August 19, 2020 @07:32AM (#24209302)
several levels of auditors were effectively asking us to downgrade to comply with their policy without even understanding the difference

The auditors' policy? Are you sure? An auditor's job is to check if you're doing what you say you should be doing. If you're arguing with an auditor then you're essentially arguing with your own organisation without any hope winning the argument.

Re:Most “mandatory requirements” in corporations are imaginary by ath0 on Wednesday August 19, 2020 @07:42AM (#24209367)
Not really a fair assessment.

An auditor's job is often to check if you're doing what an external standard says you should be doing (SOC 2 => AICPA trust principles; FedRAMP => NIST 800-53, etc.).

Unfortunately, these external standards may be written vaguely and while you may have policies that define X as Y, the auditor doesn't have to accept your answers. For example, when PCI requirement 5 says "Deploy anti-virus software on all systems commonly affected by malicious software (particularly personal computers and servers).", your policy may say "antivirus is not required inside containers that run on platforms like GKE, as these are not commonly affected by malicious software." It's very likely you'll have a discussion about your interpretation of that requirement.

Re:Most “mandatory requirements” in corporations are imaginary by viraptor on Wednesday August 19, 2020 @08:04AM (#24209551)
PCI also suggests a hardened system image, for example CIS and consistency checking like Aida. I'm getting tired of explaining that CIS (and other) "hardened" images just flip a few options and install lots of crap that can actually increase risk. E.g. You don't need cron? Haha, it's scored in the CIS benchmark, now you're running it.

I don't mean to just single out CIS as bad, but recently I learned that Ubuntu CIS docker images contain Aida, cron, and sysctl configuration. Yes, you pay for that. I'll be making fun of that for a long time.

Re:Most “mandatory requirements” in corporations are imaginary by lazyant on Wednesday August 19, 2020 @12:16PM (#24212091)
Not responding to this, just using the example. It can be easily argued that adding AV software to (some) servers increase their surface attack and reduce their security (leaving alone performance and other AV issues).
Re:Most “mandatory requirements” in corporations are imaginary by edoloughlin on Wednesday August 19, 2020 @08:04AM (#24209548)
So every team gets to argue with the auditors? Seems like the people writing the policy should do that so there's one argument instead of n.
Re:Most “mandatory requirements” in corporations are imaginary by ath0 on Wednesday August 19, 2020 @10:08AM (#24210487)
Sounds like you've mostly worked in perfectly-sized and structured corporations, where the auditors and policy-writers were perfectly connected to changing product, business and technical needs; well-staffed with policy writers and architectural governance committees who have the time, skill and background to have regular, even-handed tradeoff conversations when these issues occur, and where the engineering teams are prepped and able to engage in those conversations well.

Are they hiring?

Re:Most “mandatory requirements” in corporations are imaginary by edoloughlin on Wednesday August 19, 2020 @12:16PM (#24212096)
Unfortunately, they have an audited policy of not hiring sarcastic people.
Re:Most “mandatory requirements” in corporations are imaginary by dimitrios1 on Wednesday August 19, 2020 @09:35AM (#24210191)
Actually, you are both half right half wrong. If GP was talking about internal audit, they are correct. If you are talking about external audit, then you are correct. If you are lumping both audit functions into one, you are both wrong. Big difference between the two.
Re:Most “mandatory requirements” in corporations are imaginary by hobs on Wednesday August 19, 2020 @09:05AM (#24209945)
No, they check if you're doing what an external standard that you purport to follow is being followed.

You dont have to claim that you follow some standard that actually makes you less secure, you are just not going to be able to sell to clients who are also sheep in this manner (read: everyone.)

Re:Most “mandatory requirements” in corporations are imaginary by the8472 on Wednesday August 19, 2020 @07:43AM (#24209380)
Multi-national corporation. The auditing department and the ones writing the policy aren't even on the same continent. So it is all internal and "our own policy" in a sense, but so far removed that I might as well be talking to an external bureaucracy. By coincidence we later learned about the contact person within our own sub-org who would be responsible for forwarding change requests on those policies. The auditors themselves didn't see that as their responsibility, even when you explicitly asked them to do so.
Re:Most “mandatory requirements” in corporations are imaginary by PeterisP on Wednesday August 19, 2020 @09:26AM (#24210107)
It's definitely not the responsibility of auditors even if you explicitly ask them to do so.

In essence, the auditors are there to evaluate whether certain assertions are true. E.g. the company is asserting that they are doing X because they have a policy that X must be done. If it turns out that the internal communication within the company is screwed up and some teams are following the policy and some are not, then the claim is false and the core job of the auditors is to detect and note this. Detecting such discrepancies the main reason for why such an audit (often external,, and if internal, then mostly independent, not reporting to the audited departments) is requested. It's not their job to fix this or decide who's in the wrong - the initial claims are found to be false, and that's not okay no matter if the policy should be changed or will be changed. It does not matter how (and if) the company negotiates changes to the policy, it does not excuse the misleading claims of "X is being done" if actually the company is doing Y instead of following the stated policy. When the management has fixed this (or claims to have fixed this) one way or another, then the auditors should re-evaluate whether the claims are true now.

Re:Most “mandatory requirements” in corporations are imaginary by the8472 on Wednesday August 19, 2020 @11:01AM (#24211054)
Compliance serves a purpose and is not an end unto itself. So if you only enforce the rules even when they achieve the opposite of the underlying goal then you are goodhart's law personified. So even assuming for the moment that it's not the auditor's job to evaluate the rules themselves then at the very least they should escalate all the way back to those who write the rules if an inconsistency between rule and underlying goal is found. There's no point of having a separate channel for such communication because a particular issue for which it is relevant cannot be resolved (without missing the underlying goal) until the rule is clarified.
Re:Most “mandatory requirements” in corporations are imaginary by hinkley on Wednesday August 19, 2020 @11:52AM (#24211741)
Goal and value statements are a hallmark of effective leadership, and even people who don’t know this seem to know it on an unconscious level. It can make some people who don’t have “it” very defensive if you try to address the elephant in the room.

I’m not going to tell you how to accomplish the goal, but I’m going to tell you what we are trying to do and the manner in which we want to get there.

Re:Most “mandatory requirements” in corporations are imaginary by orblivion on Wednesday August 19, 2020 @07:50PM (#24218264)
I wonder if there's a value in simplicity of policy. Just like with coding. Sometimes you decide not to add more features or make something more efficient because it would make the code harder to maintain. If you have one blanket policy at your company, it cuts down on conversations. Case in point: you said that auditors don't understand the benefit of better hashing functions. If the policy allowed for "equivalent or better" maybe it would cause the confusion in different departments with different auditors many times over. If this is the case, though, I agree that this should be listed as the rationale, because I can imagine it's demotivating when people are required to do a worse thing for no apparent reason.
Re:Most “mandatory requirements” in corporations are imaginary by thaumasiotes on Wednesday August 19, 2020 @02:03PM (#24213719)
> I was faced with a password "security policy" that pretty much only whitelisted SHA2 + salting for password hashing. We were using a time-hard (not memory-hard though) password hashing function instead and several levels of auditors were effectively asking us to downgrade to comply with their policy without even understanding the difference.

You can comply without downgrading by just applying the SHA2 hash after your time-hard hash.

Re:Most “mandatory requirements” in corporations are imaginary by the8472 on Wednesday August 19, 2020 @02:22PM (#24214008)
That's possible but it would mean unnecessarily changing security-critical code. I'd again have to make sure to use constant-time comparisons of the different output, migrate the existing data or require users to reset their passwords and so on. All to tick a box.

Ultimately we pretty much did that, switched to scrypt which is based on sha2 and pointed to the standard saying it's sha2-based. But that does not change the fact that the policy imposes incorrect requirements on teams. SHA2 is not appropriate for password hashing.

Re:Most “mandatory requirements” in corporations are imaginary by thaumasiotes on Wednesday August 19, 2020 @03:35PM (#24215157)
> I'd again have to make sure to use constant-time comparisons of the different output

Why? What would this mean? You have a flow like this:

1. User sends "password".

2. Time-hard hash processes "password" into some hex value, HASHT. No comparison is done.

3. SHA2 processes HASHT into some other hex value, SHAHASH. You compare SHAHASH to the user's stored hashed password.

But even in step 3, you don't need constant-time comparisons. What purpose would they serve?

Assume the attacker knows your full hashing algorithm -- they can compute SHAHASH for any input password. (Maybe your salt is equal to the username, say.) That's enough to use a standard timing attack against early-abort comparison to learn the first byte (or other comparison unit) of SHAHASH.

But to learn the second byte, you need to provide a large number of hashes which all have the correct first byte. This can't be done. (It can, but you'll have to generate around 256 times as many hashes as you can use.) To learn the third byte, you need to provide a large number of hashes which all have the correct first two bytes. This is even more impossible. (In fact, you may recognize this problem as being the proof-of-work that Bitcoin requires.) The whole point of using a cryptographic hash in the first place is that we can't predict the outcome of a hash! Constant-time comparisons are something you need when you're comparing an attacker-controlled value to a secret value, but that never occurs here.

Re:Most “mandatory requirements” in corporations are imaginary by the8472 on Wednesday August 19, 2020 @05:52PM (#24217137)
Perhaps I was thinking of verifying API tokens. But see, I made a mistake while reasoning about security code. Don't make me do that more often than necessary, one day it'll go wrong.
Re:Most “mandatory requirements” in corporations are imaginary by dustingetz on Wednesday August 19, 2020 @10:26AM (#24210680)
As explained in the book "Moral Mazes: The World of Corporate Managers", the goals are unstated on purpose, due to the Principal Agent Problem.
Re:Most “mandatory requirements” in corporations are imaginary by icedchai on Wednesday August 19, 2020 @03:53PM (#24215419)
Are the people "enforcing" the policy going to actually look at the code? Probably not. Just tell them what they want to hear so they can check their box. If it comes up again, just tell them it was a mistake. Sorry, I thought we were using SHA2... we're really using more-secure-thing.
Re:Most “mandatory requirements” in corporations are imaginary by heelix on Wednesday August 19, 2020 @09:31PM (#24218940)
For every dumb rule, you always find out someone did something even more stupid.
Re:Most “mandatory requirements” in corporations are imaginary by qznc on Wednesday August 19, 2020 @07:52AM (#24209453)
An example, I'm unable to resolve so far:

ISO 26262 includes the requirement to prevent “implausible values, execution errors, division by zero, and errors in data flow and control flow” (8.4.4). I'm confident the division by zero aims at integer division because the result is undefined. For floating point, division-by-zero is perfectly fine and well defined by IEEE 754.

Nevertheless, our safety folks require us to enable the traps and shut down the device in case a floating division by zero occurs. This is stupid because a division by a very small number has the same effect as division by zero. However, since it is explicitly mentioned in ISO 26262 nobody has the balls to allow it officially.

I don't even want to estimate how many man-months have been burned to fix such "defects".

Re:Most “mandatory requirements” in corporations are imaginary by tonyarkles on Wednesday August 19, 2020 @08:32AM (#24209716)
Somewhat recent experience doing robotics work really highlighted the dangers of dividing by small numbers. As a robot arm approaches a singular configuration, the matrix used to calculate motor torques starts to get very bad and, left unaddressed, will likely result in some pretty wild behaviour.

I would argue that dividing by very tiny numbers is also something that you should probably be catching, since the output very large numbers are likely not going to do what you’re expecting...

Re:Most “mandatory requirements” in corporations are imaginary by sixstringtheory on Wednesday August 19, 2020 @12:17PM (#24212107)
Keywords to google for those interested: well-conditioned [matrix or function], gimbal lock, wrist flip.

There are some cool videos of wrist flips online, and I’ve heard of a pickup truck being thrown by an articulated arm on a factory floor due to it.

Sounds worth the precaution, given the right context!

Re:Most “mandatory requirements” in corporations are imaginary by aliswe on Wednesday August 19, 2020 @08:30AM (#24209705)
Mandatory additional detailed info: Division by zero in floating point equals to Infinity because in a floating point data structure there is space to represent such a value. For integers, there is no such information and therefore an exception should be thrown.

For a 32-bit float, the following are true:

    Positive infinity: 011111111(and then 23 zeroes)
    Negative infinity: 111111111(and then 23 zeroes)
    NaN:               x11111111(and then anything except all zeroes)
    ... x being either 0 or 1.
Source: https://en.wikipedia.org/wiki/IEEE_754-1985#Positive_and_neg...
Re:Most “mandatory requirements” in corporations are imaginary by AnIdiotOnTheNet on Wednesday August 19, 2020 @10:07AM (#24210480)
Mathematically speaking though, infinity is not the correct answer to x/0 anyway. It's just a usefully incorrect result in a lot of situations.
Re:Most “mandatory requirements” in corporations are imaginary by renewiltord on Wednesday August 19, 2020 @02:48PM (#24214451)
That's true for a lot of IEEE-754. 1/0 is defined in it in a useful way. Just as 1/3 is defined in a useful way that is not equivalent to its mathematical property.
Re:Most “mandatory requirements” in corporations are imaginary by rcoveson on Wednesday August 19, 2020 @03:01PM (#24214659)
It's not the correct answer for division of the reals. For division of IEEE 754 floats, it is the correct answer, because division in that context is defined that way.
Re:Most “mandatory requirements” in corporations are imaginary by colejohnson66 on Wednesday August 19, 2020 @10:39AM (#24210820)
Well, it’s incorrect when dividing by 0, yes. But when you do the limit as the bottom factor approaches 0, it makes sense.

So, below, the first one is defined, while the second one isn’t.

    lim_{x->0+} 1/x == +Infinity
    1/0 != (anything)
Re:Most “mandatory requirements” in corporations are imaginary by corty on Wednesday August 19, 2020 @11:24AM (#24211320)
Yes, but thats only a small part of the story, your limit only works if the numerator is constant, positive and > 0. Actually, the correct answer for lim{x->0} a/x is really "anything" and "strongly depends on a and da/dx"...

So in general, assuming anything like \infty for a division by zero is wrong wrong wrong.

Re:Most “mandatory requirements” in corporations are imaginary by colejohnson66 on Friday August 21, 2020 @09:52AM (#24234872)
Sorry if I wasn’t clear. I was not implying that any a/b where b approaches 0 is always +infinity. I was simply saying that a/0 isn’t defined, but that in the case of 1/x (positive 0), it is somewhat defined as positive infinity.
Re:Most “mandatory requirements” in corporations are imaginary by BeetleB on Wednesday August 19, 2020 @01:25PM (#24213091)
IEEE 754 handles all the cases you mentioned - it doesn't always prescribe Inf.
Re:Most “mandatory requirements” in corporations are imaginary by nybble41 on Wednesday August 19, 2020 @12:14PM (#24212071)
That depends on the numerator:

     lim_{x->1+} (x^2-1)/(x-1) == 2
Of course ideally evaluating this particular formula for x == 0 would give 0/0 which IEEE FP defines as NaN, but you could also get a non-zero finite number divided by zero due to rounding for x ≅ 1 and then the default result of +Infinity would be very far from the correct answer. Any situation where you might come close to a 0/0 or ∞/∞ term requires very careful consideration since there is very little separation between a NaN result and ±Infinity.
Re:Most “mandatory requirements” in corporations are imaginary by BeetleB on Wednesday August 19, 2020 @01:42PM (#24213370)
I worked briefly in the ISO 26262 space. While I don't have a copy of it in front of me, my understanding was not so much that you must prevent division by zero, as much as it is that you handle division by zero appropriately. Appropriately means that you can show that if you get a divide by zero, safety is not compromised. If I get an Inf or a NaN in a calculation involving cruise control, and I do nothing to handle it, do you think it will be OK?

More formally, if you have a potential division by zero and get an Inf (or NaN in case it's 0/0), you have to show what impact this will have. Can it result in a safety violation? If yes, what ASIL level would this result in? Based on this, you define your mitigation. It seems the safety folks have defined the mitigation to be "shut down the device". If you can show that there is a simpler mitigation, or that a mitigation is not needed (i.e. has no safety impact), then they should back off. This mitigation does need to be noted and documented, though.

Of course, this could be an organizational issue: Perhaps the safety folks are being the safety gatekeepers as a small portion of their job, so they are not willing to spend time to deal with nuances. I was the guy responsible for safety for my team, and it sucked - but I was doing it full time so I could analyze scenarios. The challenge was that the developers were not well versed with the ISO standard (had never read it), and it was a small portion of their job, and so they kept arguing.

> This is stupid because a division by a very small number has the same effect as division by zero.

As others have pointed out, this is not true. There is a big difference between a very large result and Inf. And of course, if a very large result could lead to a safety violation, then you need to handle it.

> For floating point, division-by-zero is perfectly fine and well defined by IEEE 754.

Keep in mind that conformance to the IEEE 754 standard is often not complete. Don't assume your language (or your libraries) are fully conformant, unless they are advertised as such.

Even if the ISO 26262 standard seems to have definitive language, I seem to recall there is a portion of the standard that allows you to waive requirements if the requirement makes no sense in your use case. There is a procedure to do it (documenting, etc).

FWIW, we did not handle Inf or NaN or divide by zero anywhere. We were writing a general purpose library for auto manufacturers, and it was up to them to decide where/how it would be used (called "Safety Element Out of Context" in the standard). Since we did not know the context, we argued that we can't assess if a division by zero would be hazardous, and merely noted in the documentation where it could occur. It's up to the folks who buy our libraries to then do that analysis. We only took care of things like showing there were no known crashes or hangs.

Re:Most “mandatory requirements” in corporations are imaginary by qznc on Thursday August 20, 2020 @05:34PM (#24229287)
What I meant by "the same effect" is that division by zero or by a small number can both result in Inf.

You are correct that it is possible in general. However, in this specific project, the decision was to shut down the device for safety reasons if the CPU detects a floating point division by zero. In my opinion this reduces the availability of the functions unnecessarily.

Re:Most “mandatory requirements” in corporations are imaginary by bonzini on Friday August 21, 2020 @02:56PM (#24237783)
> This is stupid because a division by a very small number has the same effect as division by zero.

It doesn't, it cannot ever return NaN.

Re:Most “mandatory requirements” in corporations are imaginary by globular-toast on Wednesday August 19, 2020 @09:18AM (#24210034)
Just because division by zero produces a value doesn't mean the value means anything or should ever have been obtained. Division by a very small number and division by zero should NOT have the same effect. That is the error which you're supposed to catch by not dividing by zero in the first place.
Re:Most “mandatory requirements” in corporations are imaginary by Spooky23 on Wednesday August 19, 2020 @08:44AM (#24209800)
The other principle is separation of duties. Policy is made by people who aren't the practitioners so that the interests of the organization are ahead of the whim or convenience of the practitioner. People who served in the military usually get this concept, as it's more obvious that there is a long line of stupid actions on random soldiers' part that leads to a longer line of preventative rules.

I'd also say that when I worked on a program for a big company that interfaced with alot of small companies and startups a few years, the startups in particular had really awful practices. The "bullshit" compliance checklists for security revealed awful practices that present real risks. The big company was more vulnerable to systemic risk due to inflexibility, the small companies are more vulnerable to individual risks due to employee action or lack of controls.

Re:Most “mandatory requirements” in corporations are imaginary by heymijo on Wednesday August 19, 2020 @12:50PM (#24212568)
The big company was more vulnerable to systemic risk due to inflexibility, the small companies are more vulnerable to individual risks due to employee action or lack of controls.

This is incredibly well said and worth highlighting.

Re:Most “mandatory requirements” in corporations are imaginary by twhitmore on Wednesday August 19, 2020 @06:04AM (#24208798)
Management works by creating processes and systems. There are always inaccuracies and imperfections in how these are targeted, and inefficiencies resulting.

Yet creating processes and systems is the expected task of management -- it's a key way to scale.

I'm fairly much averse to process myself, but have been occasionally involved.

Re:Most “mandatory requirements” in corporations are imaginary by ISL on Wednesday August 19, 2020 @10:54AM (#24210992)
The critical bit is to continuously evaluate whether or not the processes and systems are achieving the mission of the organization.

In my, academic, world, the core problem is that there is no overarching mission against which the process/system can be evaluated. We have 5-10 important goals of the institution/system and multiple sub-organizations with wildly different emphasis on each goal.

Re:Most “mandatory requirements” in corporations are imaginary by mehrdadn on Wednesday August 19, 2020 @06:32AM (#24208926)
> Chesterton's fence

Is there a "reverse" version of this where you do understand the reasoning, explain clearly why it doesn't apply anymore, but the other side just refuses to think for themselves and just sticks with the status quo because it must've been done with good reason and they don't want to second-guess it?

Re:Most “mandatory requirements” in corporations are imaginary by yodelshady on Wednesday August 19, 2020 @07:18AM (#24209204)
I believe the phrase is "jobsworth", as in "more than my".

The point of the article is that's kind of correct - the cost (risk) of deregulating is concentrated, but the benefit is distributed. There needs to be some way to capture the value-add of removing a rule.

But if you do that the easiest way - turning the global metric of productivity into a target - then managers will asset strip, fire security (ahem, Mozilla), and walk off with a fat bonus (short-term productivity is up!) before people realise what's left is a the empty shell of a company.

And that's why good management is hard.

Re:Most “mandatory requirements” in corporations are imaginary by mehrdadn on Wednesday August 19, 2020 @07:24AM (#24209247)
Learned a new (British?) word today, thanks!
Re:Most “mandatory requirements” in corporations are imaginary by noisy_boy on Wednesday August 19, 2020 @06:37AM (#24208956)
Quite often the other side is perfectly capable of thinking for themselves. They just don't want to lose their job on account of that one common-sense approval in case things go south. Self-preservation etc.
Re:Most “mandatory requirements” in corporations are imaginary by vharuck on Wednesday August 19, 2020 @11:26AM (#24211365)
Re:Most “mandatory requirements” in corporations are imaginary by anoncake on Wednesday August 19, 2020 @07:44AM (#24209389)
Cargo-culting? At least it's similar.
Re:Most “mandatory requirements” in corporations are imaginary by danaris on Wednesday August 19, 2020 @08:05AM (#24209555)
> In BigCorps, if there's a stupid requirement, there's usually a reason for the stupid requirement to be there in the first place

Yes, but that doesn't mean it was ever a good reason, or that the reason still applies.

In a very large number of cases—like the one mentioned in the article—the primary reason is to let the company's management feel more "in control" of their low-level employees.

In a lot of (closely related) cases, it's straight-up racism, sexism, or classism. (Frankly, one can easily make a case that the working-from-home prohibitions fall into that category—they derive from an assumption that low-level employees are lazy and want to avoid work as much as possible, because they're analogous to the assembly-line employees of yesteryear, and thus assumed to be lower-class...which means lesser beings.)

Re:Most “mandatory requirements” in corporations are imaginary by Aeolun on Wednesday August 19, 2020 @05:55AM (#24208761)
I think the problem with this logic is it hinders a hundred people on a daily basis to prevent one person from doing something stupid once a year.

That’s just not great ROI.

Re:Most “mandatory requirements” in corporations are imaginary by serioussecurity on Wednesday August 19, 2020 @06:10AM (#24208835)
I've seen individual engineers make a mistake that caused 100 engineer's salary worth of damage.
Re:Most “mandatory requirements” in corporations are imaginary by moritonal on Wednesday August 19, 2020 @07:33AM (#24209314)
"Unfortunately, one of the inputs to the command was entered incorrectly and a larger set of servers was removed than intended. The servers that were inadvertently removed supported two other S3 subsystems." [1]

1. https://aws.amazon.com/message/41926/?ascsubtag=e7c5af5933bd...

Re:Most “mandatory requirements” in corporations are imaginary by alexchamberlain on Wednesday August 19, 2020 @06:26AM (#24208903)
I suspect we all have. The question is rather: how much would it have cost to prevent that mistake?

The flip side is the insurance argument: given a big enough organisation, a mistake like that will happen, even if the probability of each individual mistake is very low. So assuming one of these will happen, what can you do to reduce the impact or to reduce the latency of fixing such a mistake?

Re:Most “mandatory requirements” in corporations are imaginary by Aeolun on Wednesday August 19, 2020 @08:38AM (#24209762)
Indeed, but did those 100 engineers increase the company bottom line by 10% more because they weren’t hindered by too much red tape, and is that value a multiple of their salary?

Also, do you expect mistakes of that magnitude to keep being made?

Re:Most “mandatory requirements” in corporations are imaginary by leprechaun1066 on Wednesday August 19, 2020 @12:06PM (#24211939)
The Knight Capital error really messed them up. https://www.reuters.com/article/us-knightcapital-results/kni...
Re:Most “mandatory requirements” in corporations are imaginary by gjvc on Wednesday August 19, 2020 @06:45AM (#24208992)
I would love to know more about the details of this example :-)
Re:Most “mandatory requirements” in corporations are imaginary by gwd on Wednesday August 19, 2020 @07:17AM (#24209197)
So the company I work for made the front page of HN last year for a security breach. I won't go into details, but I will say one factor was a particular instance where security was overlooked for many years due to convenience.

In response, the company has now sort of swung the other way: lots of things that have a perfectly valid reason and are reasonably safe have been forbidden or suddenly have needed to be justified in the face of extreme skepticism.

That wasn't a case of a single engineer causing 100x engineers worth of damage, but it was the case where something made hundreds of people's jobs a tiny bit easier for two decades, then caused a massive public loss of face and who knows how much reputational damage.

And I'd be willing to bet that a fair number of HN readers work at a company which has at least one system with similar properties (a bit more convenient, a bit less secure) to the one implicated in our security breach; but failure is a once-a-decade event, and their company isn't nearly that old yet. Would those engineers defend that setup using the argument from this article?

Re:Most “mandatory requirements” in corporations are imaginary by dtech on Wednesday August 19, 2020 @10:49AM (#24210931)
Was it the Twitter internal account management tool?
Re:Most “mandatory requirements” in corporations are imaginary by gwd on Wednesday August 19, 2020 @12:00PM (#24211851)
Nope. :-)
Re:Most “mandatory requirements” in corporations are imaginary by cecilpl2 on Wednesday August 19, 2020 @10:50AM (#24210944)
Here's another famous example where the damage was thousands of person-years of salary: https://www.henricodolfing.com/2019/06/project-failure-case-...
Re:Most “mandatory requirements” in corporations are imaginary by DaiPlusPlus on Wednesday August 19, 2020 @07:24AM (#24209240)
Re:Most “mandatory requirements” in corporations are imaginary by DEADBEEFC0FFEE on Wednesday August 19, 2020 @06:05AM (#24208804)
Anyone who has spent a bit of time trying to calculate the lost productivity caused just the meetings needed to discuss breaches (internal, accidental), knows it's great ROI.
Re:Most “mandatory requirements” in corporations are imaginary by corty on Wednesday August 19, 2020 @06:12AM (#24208844)
Everyone greatly overestimates ROI in their own area of expertise and greatly underestimates costs in the rest.

You might be right in some special instance, but generally you are not. One example: Sending files via Email is a security problem. So you prohibit this via settings, virus scanners, appliances, etc. Now you've solved the emailed worm problem. However, you've just created a "how do we move files/data/screenshots/..." problem for the whole company. Now everyone will need their own special solution for everything, support will need a screenshot upload tool because you cannot just email them screenshots anymore, marketing won't be able to do images in mails anymore, external people won't have access to internal file shares, etc.

Re:Most “mandatory requirements” in corporations are imaginary by iso1631 on Wednesday August 19, 2020 @08:27AM (#24209678)
And you end up creating far more security holes as people work around it.

Shadow IT is great, it makes companies actually work rather than go bust.

Re:Most “mandatory requirements” in corporations are imaginary by dtech on Wednesday August 19, 2020 @10:52AM (#24210961)
Please tell this to my companies IT department. They've finally moved to Azure and Onedrive with it, but are still forbidding any files downloaded to devices or email attachments being send to external addresses because otherwise it's unsecure.

So everyone is still using WeTransfer/Dropbox/whatever like they were in the years before.

Re:Most “mandatory requirements” in corporations are imaginary by iso1631 on Wednesday August 19, 2020 @02:45PM (#24214417)
We keep a low profile. Separate network, very limited interaction with "corporate IT" (which is outsourced). We keep infosec onside by making our liason feel we are across things. Allows us to sidestep a lot of problems, because ultimately in a large company people don't have to

Took me 15 years to realise that incompetence is at worst ignored, and often leads to promotions.

I've spent 3 years telling corporate IT they have a problem with a router config that limits throughput, we got 3mbit rather than 1Gbit. They spent 3 years insisting it wasn't them, and it was the upstream ISP. I even managed to get read only snmp access, and generated cacti graphs of their router showing 400M (iperf2 in udp mode, so 400kbit/ms) going in on port channel 1, but not emerging on the ISP interface.

My shadow-IT deparement spent 3 years paying for a completely separate network connection to bypass the corporate IT one and meet our requirements (easy to do when it's a remote branch office in another country), other departments just suffered it. It was the backup link so only used about 1 day in 10.

Eventually a senior member of (non-tech) staff resigned over the issue and it started being taken more seriously.

The way this system is designed (giving the front door to corporate IT) was done over my objections, and the objections of many others, but on paper it was good. Corporate IT provide shiny SLAs (which mean squat).

Last week, 12 months after the resignation and the beginning of taking it seriously, it had been escalated through 4 different layers of corporate IT, and eventually they came back and said "we've found an errant access list and removed it, and it's now fixed".

That's it. 3 years telling them what the problem was, 3 years of being ignored, and what happens? Certainly no blame for the idiots that made the decision to use this, no comeback on corporate IT provider, but if people find out about shadow IT they kick up a fuss (so the trick is to keep quiet and keep good personal relations with potential pain points).

Oh yes, we outsourced our corporate IT. Obviously there's no money coming back, I suspect we'll get a bill.

Re:Most “mandatory requirements” in corporations are imaginary by DrAwdeOccarim on Wednesday August 19, 2020 @06:29AM (#24208914)
I appreciate you're giving an example, but this is pretty much solved at most big companies currently with OneDrive (or any other flavor of cloud storage). For external sharing, you just select if the link can be seen external to the org.
Re:Most “mandatory requirements” in corporations are imaginary by astura on Wednesday August 19, 2020 @08:03AM (#24209541)
Doesn't SharePoint trivially solve all this?
Re:Most “mandatory requirements” in corporations are imaginary by Aeolun on Wednesday August 19, 2020 @08:49AM (#24209833)
I don’t think I’ve ever heard Sharepoint and ‘trivially solved’ in the same sentence before.

The problem with using sharepoint is that now you have sharepoint, and people will start using it, with all attendant horrors.

Re:Most “mandatory requirements” in corporations are imaginary by HelloNurse on Thursday August 20, 2020 @08:40AM (#24222592)
SharePoint is fairly good at sharing files: it allows upload by drag and drop, it supports versioning and approval of documents with a decent user interface, it offers a reasonable organization of users and permissions. Running SharePoint is anything but trivial, but with some discipline it can actually solve problems for end users.
Re:Most “mandatory requirements” in corporations are imaginary by corty on Wednesday August 19, 2020 @08:15AM (#24209613)
For external people likely not, usually Sharepoint would be behind some VPN and Firewall. Some cloud service like Dropbox might work if allowed (which it often isn't). And then there will often be the resulting sprawl of various services: this for secret internal stuff, that for external people, yet another thing for marketing, etc.
Re:Most “mandatory requirements” in corporations are imaginary by Aeolun on Wednesday August 19, 2020 @08:45AM (#24209805)
This just tells us that we shouldn’t discuss breaches so much? My one experience with a breach has been that the whole process around it was a collosal waste of everyone’s time.
Re:Most “mandatory requirements” in corporations are imaginary by taneq on Wednesday August 19, 2020 @05:58AM (#24208771)
It's a great ROI if that one stupid thing a year is someone pushing your company's codebase and all your trade secrets to a public repo.
Re:Most “mandatory requirements” in corporations are imaginary by Aeolun on Wednesday August 19, 2020 @08:51AM (#24209843)
By the same logic it’s good to have your company located in an armored bunker underground on the off chance that someone nukes the city you are in.

I realize the chances are a bit different, but it illustrates the point.

Re:Most “mandatory requirements” in corporations are imaginary by RcouF1uZ4gsC on Wednesday August 19, 2020 @05:58AM (#24208768)
Never underestimate the damage one person doing something stupid once can do.
Re:Most “mandatory requirements” in corporations are imaginary by bryanrasmussen on Wednesday August 19, 2020 @06:59AM (#24209064)
I actually think this whole one person doing one stupid thing per year argument is grossly underestimating the amount of stupid available.

Stupidity is one of humanity's greatest renewable resources.

Re:Most “mandatory requirements” in corporations are imaginary by notimetorelax on Wednesday August 19, 2020 @05:58AM (#24208772)
Depends on the impact of a single erroneous action. I’ve seen cases when folks would push to GitHub passwords (that should be kept in git to start with).
Re:Most “mandatory requirements” in corporations are imaginary by bryanrasmussen on Wednesday August 19, 2020 @06:57AM (#24209054)
right, pushing github passwords leads to GDPR breach in end - anything preventing GDPR breach in the end is probably a great ROI.
Re:Most “mandatory requirements” in corporations are imaginary by Maxion on Wednesday August 19, 2020 @06:02AM (#24208787)
Depends a lot on the company and what it's mission is, not every company needs to be able to move quickly on every front.
Re:Most “mandatory requirements” in corporations are imaginary by HenryBemis on Wednesday August 19, 2020 @06:02AM (#24208785)
I believe it's all about Security (C-I-A).

To mitigate this issue, on paper, an (usually) HR policy writes "do not do non-work related stuff with your work computer". And since many people ignore this rule, because "why have a second laptop?", the next best thing is to route all traffic from your laptop through the company, and weed out the GigHubs and GitLabs of this world (in the same manner that they block all sex-drugs-rocknroll stuff).

You can't blame a company for wanted to protect itself against a disgruntled employee that wants to push the (example - not applicable to your company) ebanking software code out in the open.

That said.. why would a person use the corporate computer for their (allow me the use of the word) 'hobby'? Unless it's for charity work, most companies don't appreciate spending resources (time, money, equipment) on other things.

Re: Chesterton's Fence - didn't know it had a name, thank you for this!

Re:Most “mandatory requirements” in corporations are imaginary by Perseids on Wednesday August 19, 2020 @06:47AM (#24209006)
> You can't blame a company for wanted to protect itself against a disgruntled employee that wants to push the (example - not applicable to your company) ebanking software code out in the open.

The thing is, they can't, not if my PC is still usable for day to day work. For a legitimate user, the ways to extricate data are endless (e.g. tunnel out via DNS, embed into video streams (for customer training or something), hell, even simple stuff like embedding data into the monstrous modern MS Office files should fly under the radar). The real value comes from making certain that a) only those that need access, get access (e.g. why do I have read/write access to the sales file folder as a developer?) and b) minimize the result of a breach ahead of time, which often coincides with doing good work in general. For instance, don't lie to your customers on a regular basis, treat your employees respectfully, and – regarding your example – write closed source software as if it was open source the whole time. It's not as if attackers need the source code to fuzz your software for vulnerabilities.

On a principled basis, I really dislike the world view where the employees have to be constantly prevented from getting the better of the company. If you don't trust me enough to surf on news sites during my time off at work, you should not trust me with software development, where laziness has often far worse consequences than not doing any work at all.

Re:Most “mandatory requirements” in corporations are imaginary by dx034 on Wednesday August 19, 2020 @07:41AM (#24209361)
These protections never really work against people who really want to get data out. Worst case you could just take pictures of your screen and read text back via OCR.

But most employees would never know how to do this and even if, the threshold is high to go to such lengths. Most companies primarily want to prevent users from sending out data by mistake or via malware, since these are probably >99% of the reasons for data loss.

I also dislike companies restricting employees. But I also know people from our IT department and the incidents they have to fight on a daily basis. If you don't restrict your network and company computers, you'll very quickly end up with malware, randsomware, leaked data etc.

Re:Most “mandatory requirements” in corporations are imaginary by Perseids on Wednesday August 19, 2020 @09:33AM (#24210166)
I think we're mostly in agreement.

The original scenario HenryBemis painted involved source code being leaked, so I think it's fair to either assume the employee is technically competent, or should not have access to it in the first place. Also, their scenario involved disgruntled employees, so on the other end of the spectrum, if you have, say, sales representatives which want to take out their customer database, then it's well in their motivation spectrum to snap a few hundred smartphone pictures of Excel or Outlook with a pdf "scanning" app to get a nicely printable address book. Sure, it's not perfect, but it can still be damaging as hell. Basically: Don't rely on data exfiltration to fail.

But the reason I've bothered to write the first comment, is that it's such a huge productivity drain to develop software on a locked down machine. I'll think twice or thrice before taking on a position where I don't have root access to my computer.

I concur most non-technical employees don't need (or should have) more than the equivalent of a Chromebook.

Re:Most “mandatory requirements” in corporations are imaginary by blackflame7000 on Wednesday August 19, 2020 @07:05AM (#24209120)
The problem is that not all warning signs rise to a fireable offense and in todays sue happy climate even at will employment has restrictions that protect workers rights
Re:Most “mandatory requirements” in corporations are imaginary by zeepzeep on Wednesday August 19, 2020 @06:10AM (#24208839)
> That said.. why would a person use the corporate computer for their (allow me the use of the word) 'hobby'?

Because my work computer is around 100 times faster than my personal one.

Re:Most “mandatory requirements” in corporations are imaginary by anticensor on Wednesday August 19, 2020 @06:17AM (#24208863)
I have the opposite situation: My personal computer is faster .
Re:Most “mandatory requirements” in corporations are imaginary by munk-a on Wednesday August 19, 2020 @06:24AM (#24208894)
Assuming both are laptops and you don't have some insane personal computer - you should seriously examine why your workplace is skimping on a few hundred dollars extra on a machine that might save you, an employee with a salary in the tens of thousands (or higher) a few days of waiting for things to load, render or compile a year.

There certainly is a logic around not wasting money where it'd do no good - but companies that are tight with employee capital expenditures make me really nervous. It's a thing I've avoided consciously in employers since my thirties - if you don't value me enough for a decent keyboard, a chair, and a sufficiently performing computer - then you don't have anyone who is sane at evaluating RoI at your upper echelons.

Re:Most “mandatory requirements” in corporations are imaginary by majewsky on Wednesday August 19, 2020 @11:21AM (#24211285)
My work computer and personal computer may be roughly on par as far as the spec sheet goes, but my personal computer does not have McAfee, so it's at least 100 times faster.
Re:Most “mandatory requirements” in corporations are imaginary by anticensor on Wednesday August 19, 2020 @06:30AM (#24208916)
No, both are desktops; and I work at computer engineering department of a (not so research-focussed) state university as an academic, with my specialisation being low-level software engineering; not at a software company. Even lab computers are not so better than my personal computer, except for the supercomputing lab.
Re:Most “mandatory requirements” in corporations are imaginary by skocznymroczny on Wednesday August 19, 2020 @08:34AM (#24209738)
Even if the work machine has comparable specs to personal computer, it's much slower. Every machine is fast, but put antivirus software on it, backup solution, 10 "corporate security" products which monitor and log every move and even the strongest machine slows to crawl.
Re:Most “mandatory requirements” in corporations are imaginary by OkGoDoIt on Wednesday August 19, 2020 @01:12PM (#24212888)
My work computer would be substantially faster than my personal computer if it wasn’t bogged down by so much IT crap. In practice my personal computer substantially faster to get anything done because I have to fight it so much less.
Re:Most “mandatory requirements” in corporations are imaginary by mamon on Wednesday August 19, 2020 @07:03AM (#24209102)
I really wish I could use my personal laptop at work, but now it is hard, because GDPR laws mandate that I would need to take additional security measures and could be held responsible for any data leak. Using company issued laptop avoids the problem - all responsibility rests on my employer's shoulders.
Re:Most “mandatory requirements” in corporations are imaginary by dx034 on Wednesday August 19, 2020 @07:42AM (#24209368)
And having two computers is just annoying. I dislike when companies prevent me from using my computer for personal stuff (esp web surfing). But if I was in charge, I also think I wouldn't take that risk and prohibit use outside work. The risk just doesn't justify the benefit for the employee.
Re:Most “mandatory requirements” in corporations are imaginary by scarface74 on Wednesday August 19, 2020 @10:31AM (#24210742)
Then buy a faster personal computer? The resources I have freely available at work are infinitely more than I have at home, but that doesn’t mean I can set up my own Netflix competitor on it.
Re:Most “mandatory requirements” in corporations are imaginary by wdb on Wednesday August 19, 2020 @08:21AM (#24209646)
I love these requirements at work! Yes, I need to buy my own computer, but now I can leave my work laptop in the office.

Which helps avoiding working late as partner expects you to be on time for dinner, and as you don’t need the work laptop at home as it’s not shared also as a personal laptop :)

I swear that’s main reason employers allow you to use your work laptop for personal use too. As you will have your work laptop with you at home so they can let you easier work weekends etc

Re:Most “mandatory requirements” in corporations are imaginary by JTbane on Wednesday August 19, 2020 @10:58AM (#24211018)
>You can't blame a company for wanted to protect itself against a disgruntled employee that wants to push the (example - not applicable to your company) ebanking software code out in the open.

It's pretty dumb to block gitlab when you employee can just... copy the codebase to an external drive?

Re:Most “mandatory requirements” in corporations are imaginary by sfifs on Wednesday August 19, 2020 @09:51PM (#24219056)
> why would a person use the corporate computer for their (allow me the use of the word) 'hobby'?

Doesn't have to be hobby. A lot of corporate code these days is based on open source libs. What if you fix a bug and want to push upstream?

Re:Most “mandatory requirements” in corporations are imaginary by MikeTaylor on Wednesday August 19, 2020 @08:53AM (#24209853)
Side issue, but I have cause to mention Chesterton's Fence so often that it's become a real frustration that there is no Wikipedia article about it — only this essay about why Wikipedia contributors should honour it. I wish there was an actual article I could point to when I want people to know about it.

(Why don't I just make one? I have basically given up on making substantial contributons to Wikipedia since the Deletion Police took over the asylum. There's a 90% probability that if I did spend a couple of hours writing a good article, someone would come along within a week and spend a couple seconds deleting it. It's out of control.)

Re:Most “mandatory requirements” in corporations are imaginary by shalmanese on Wednesday August 19, 2020 @09:11AM (#24209989)
Re:Most “mandatory requirements” in corporations are imaginary by hrafn on Wednesday August 19, 2020 @09:00AM (#24209901)
You could use this redirect as a link: https://en.wikipedia.org/wiki/Chesterton%27s_fence
Re:Most “mandatory requirements” in corporations are imaginary by kotrunga on Wednesday August 19, 2020 @08:56AM (#24209877)
What is this Wikipedia "Deletion Police"? I haven't heard of quality content being consistently deleted.
Re:Most “mandatory requirements” in corporations are imaginary by jfengel on Wednesday August 19, 2020 @09:15AM (#24210018)
I often hear it called Deletionism, and there is a Wikipedia article about it:

https://en.wikipedia.org/wiki/Deletionism_and_inclusionism_i...

It cites a quote from Paul Graham (cofounder of Y Combinator) that begins "Deletionists rule Wikipedia."

Re:Most “mandatory requirements” in corporations are imaginary by gpanders on Wednesday August 19, 2020 @02:30PM (#24214144)
Farnam Street has a good write-up: https://fs.blog/2020/03/chestertons-fence/
Re:Most “mandatory requirements” in corporations are imaginary by DanBC on Wednesday August 19, 2020 @09:00AM (#24209902)
> Why don't I just make one? I have basically given up on making substantial contributons to Wikipedia

You don't have to put it up on Wikipedia. You could put it on Neocities or Medium or wherever.

Re:Most “mandatory requirements” in corporations are imaginary by brianmcc on Wednesday August 19, 2020 @10:58AM (#24211021)
It's "cool" to move fast, break things. It's less cool to tread carefully and do due diligence.

People love to use folksy stories to justify the former (the one about the monkeys for example - https://workingoutloud.com/blog/the-five-monkeys-experiment-...).

I really like Chesterton's Fence as a counter-story to it, not to stop meaningful change from actually happening but to neutralize decision-by-best-folksy-story from over-ruling other options unchallenged, and allowing case-by-case thinking to prevail.

Re:Most “mandatory requirements” in corporations are imaginary by rlwinm on Wednesday August 19, 2020 @11:08AM (#24211122)
> For instance, there's a restriction at my workplace (not a software company, a regular old industry fortune 500) which prevents git installs from pushing to any non corporate GitHub repo from our work machines.

Someone has to say it.

I’ll admit to accidentally pushing some of my employer’s code to GitHub.

The code was a fork of one of my GitHub repositories and I pushed to the wrong remote. I deleted the resulting commits afterwards and no PII was leaked but it’s a valid concern for employers.

Re:Most “mandatory requirements” in corporations are imaginary by mfenniak on Wednesday August 19, 2020 @11:50AM (#24211700)
> For instance, there's a restriction at my workplace (not a software company, a regular old industry fortune 500) which prevents git installs from pushing to any non corporate GitHub repo from our work machines.

Oh my! As I have struggled with security incidents caused by people either accidentally publishing GitHub repos that are "public" rather than "private", or pushing corporate code to their own repos (that are... you guessed it, "public"), I have long looked for another IT department that has grappled with this problem. GitHub Support hasn't helped, appealing to public forums hasn't helped. But here, a sign that my problem isn't unique!

Of course, the solution sucks. sigh

Re:Most “mandatory requirements” in corporations are imaginary by robszumski on Wednesday August 19, 2020 @12:07PM (#24211954)
I can report in on the container version of this. Docker would not accept patches from Red Hat about Docker Hub being the default push location. They wouldn't even accept to make this configurable. Our enterprise customers didn't even want it trying, regardless of if it was blocked at the network level.

Quay.io makes all pushes private by default, to protect from this type of behavior. If you accidentally typo, you are protected.

Re:Most “mandatory requirements” in corporations are imaginary by watwut on Wednesday August 19, 2020 @06:03AM (#24208794)
> A more productive use of time would be to understand the reason for the policy, document out why it doesn't apply to your case and then attempt to get approval.

My experiences with big organizations is that the above is complete absolute waste of time, unless you are in some kind of high level position already.

Re:Most “mandatory requirements” in corporations are imaginary by brokenmachine on Thursday August 20, 2020 @02:44AM (#24220540)
100%.
Re:Most “mandatory requirements” in corporations are imaginary by runarberg on Wednesday August 19, 2020 @02:47PM (#24214447)
True, there is probably a reason for some stupid requirement, but that reason might still be stupid.

Remember that upper management is people, and as people they have their own biases, fallacies, ignorance, etc. They are just as prone to make wrong decisions as you are. In fact in an area of your expertise, they are indeed more prone to make a wrong decision out of simple ignorance or bias. If you think a requirement from your area of expertise is stupid, it probably is a stupid requirement. If you can’t see a reason for that requirement, there probably isn’t a good one.

The fact that the decision to make this stupid requirement comes from people in power gives you even more reason to question the validity of the requirement. People that hold high position and a great amount of power often face less scrutiny and questionable decisions made by them are far less criticized, then similar decisions made by people of less power.

Re:Most “mandatory requirements” in corporations are imaginary by globular-toast on Wednesday August 19, 2020 @09:14AM (#24210009)
> In BigCorps, if there's a stupid requirement, there's usually a reason for the stupid requirement to be there in the first place

I disagree. I've worked in a BigCorp and many requirements were in place not due to reason but due to feelings and inertia. The "butts in seats" requirement was one of the main ones. Even after showing my boss that I could at the very least work equally as effectively from home, he still felt it wasn't OK for me to work at home more than once a week. And never underestimate the power of inertia. Things are this way, they've always been this way.

Re:Most “mandatory requirements” in corporations are imaginary by scarface74 on Wednesday August 19, 2020 @10:35AM (#24210781)
I just left a company that was trying to rush us back into an open office post Covid. As if it weren’t bad and noisy enough pre-Covid.

It kind of threw that whole “we are in this together. Accept your 10% pay cut.” bullshit out of the window. Especially when all of the management had separate offices.

Re:Most “mandatory requirements” in corporations are imaginary by michaelcampbell on Wednesday August 19, 2020 @08:16AM (#24209619)
> In BigCorps, if there's a stupid requirement, there's usually a reason for the stupid requirement to be there in the first place

Sometimes, this is to be able to hire the exactly one person they want to hire, but HR policies or some law requires it be an "open bid" system. So the tailor the requirements such that only the one person can qualify, and they can justify the hiring and the letter of the law.

Re:Most “mandatory requirements” in corporations are imaginary by m463 on Thursday August 20, 2020 @12:47AM (#24219982)
I wish I could find the article, but I think Joel on Software (?) had something once about bigger companies adding on things like how some people stand by the door turning around and checking their wallet and keys carefully before going out. or some similar analogy.
Re:Most “mandatory requirements” in corporations are imaginary by kevin_thibedeau on Wednesday August 19, 2020 @01:10PM (#24212849)
Who authorized you to push OS conributions on company time?
Re:Most “mandatory requirements” in corporations are imaginary by swiley on Wednesday August 19, 2020 @07:05AM (#24209115)
This shouldn’t need to be enforced by software. You really don’t have any business accessing a personal git repo from a coorperate machine; you’re spending time twice (stealing) and it’s a good way to lose ownership of IP.

Furthermore this probably makes officially allowed open source contributions much more difficult.

Re:Most “mandatory requirements” in corporations are imaginary by blackboxlogic on Wednesday August 19, 2020 @07:31AM (#24209299)
We depend on some open source tools. When my project is blocked by a bug in one of them, it absolutely is my job to fix it.
Re:Most “mandatory requirements” in corporations are imaginary by swiley on Thursday August 20, 2020 @11:36AM (#24224333)
Maybe I could have phrased that better but I think you and I agree.
Re:Most “mandatory requirements” in corporations are imaginary by vorpalhex on Wednesday August 19, 2020 @09:18AM (#24210036)
And how am I supposed to patch the OSS libraries I'm using otherwise?