You're viewing a single thread.
I no longer waste time.
Because i have already broken all the company security policies.
Protip: convince the IT team that Linux is essential for your development work. Small percentage of the IT team is aware about security on Linux.
It's been ages since I did IT. If I had a user who wanted to run Linux then I knew that, on average, they were going to cause me a lot less headaches with random user issues so I wouldn't mind being flexible. Endpoint security will be different, but a lot of network security is handled through network devices that don't care what the client is.
If I had a user who wanted to run Linux then I knew that, on average, they were going to cause me a lot less headaches with random user issues
In my case, it's the IT team which creates more issues for Linux users.
Whenever they change security policies, they never test it out on Linux and our connection goes down (some VPN/Firewall/DNS policy). It takes ages for us Linux users to convince them that we didn't do any changes on our system and this problem is on their side.
I'm so glad to be away from corporate IT and working with small teams of highly technical people where every request isn't "ok I'll fill out the paperwork" but "Hmm, we could do it like this: " We just created a small network, gapped from everything else, where you can just use the bandwidth but cannot possibly affect the production network. Since our bandwidth utilization is generally around 5% of maximum it's not issue to grab things using a 10Gb chunk of a few hundreds of Gb of bandwidth. The traffic is tagged with a low priority QOS packet so even in the worst case it will never affect network operation.
The solution is simple, all users must now use Linux.
No more it trouble :)
It's like going back a quarter century when all of the ISPs would only officially support Windows or Apple. I'd have to let them know exactly what information I needed (which if I remember right was pretty basic, like 2-3 items) and tell them to trust me to do the rest. Usually there was a little pushback because they wanted to go through their support scripts. I found when I started working in corporate jobs, I'd talk to the IT people and promise to do my own troubleshooting and I just about always was able to run Linux at work. Made for a much more enjoyable, and productive, work day.
Lmao, at my job, if they don't understand, they just block the device from the network. Even if they do give you an exception, you'll still get blocked. They are actually more strict about Linux devices. I have a Linux vm that I do most of my work on. It exists in an ESXi somewhere. The ESXi gets inventoried, so they still know about my VM.
It's sad.