192 karma · joined June 18, 2021
But there has to be a very good reason. Such as theft, or actual security worries.
I’m all for DNS instead of IP’s, but we need to stop encoding too much information into names…
It’s been my understanding that for corporate use, only a single one should be issued because:
1: There’s an establish support team in your org that can always issue a new one (except for a few edge cases, super critical things) 2: You can’t trust users with 2 devices
For private use, nr. 1 would not be true so the recommendation rightly is to issue 2.
The Bible however, does actually forbid it: Exodus 20:4
I seem to remember that Jehovas Witnesses actually practice this as they take the words of the Bible literally.
I’m by no way an expert on theology, mainly interested on a hobby level, so take what I say with a grain of salt.
If the devices are locked down to a degree that you cannot do your dev (aka your job), that should be brought up with management. Of course, it’s easier said than done xD
I’m personally a fan of locked down corporate devices and then either dedicated laptops or cloud vms for development.
It’s not necessarily an easy problem to solve though
It’s a nightmare from a privacy point, but its also a problem for the InfoSec tools… How do they distinguish between an unmanaged private device on a private network or a unmanaged device on a corporate network?
For the employer to open/read such communication would be highly illegal, akin to opening others private snail mail.
I do believe that this also extends to corporate issued phones and computers. Especially since you’re automatically taxed for “private use” of such equipment when assigned.
Of course, given enough data that has been changed can potentially allow you to deduce how that data was changed and thus revert it, at which point it would become PII again and you’d have a problem… but that’s probably a fringe scenario
Sure, passwords and credit card info is obscured with your methodology, but names, dates of birth, sexual orientation, telephone numbers, email and ip will remain unique. This uniqueness is what allows you to potentially identify a person given enough data.
In Denmark, every child was (I’m not sure if they still are actually?) registered at birth by the local parish in so called “church books”.
With these “databases” in hand, the SS had a neat list of all names, and the approximate location of peoples homes.
Those lists were used to identify and prosecute jews.
The Brand Protection department hold an enormous amount of political power internally - they rival, if not outright eclipse, Legal…
They WANT people in the office. They just opened up nla new Copenhagen office and opened up their corporate headquarters in Billund. They are also the largest real-estate holder (or, their owners Kirkbi is) in Billund - They pretty much own the entire city.
They do rely on the “coolness” factor of working for LEGO though. Many people work there because their parents did or because they think it’s cool.
They generally treat their employees very nice and I’d have no problem recommending them as a employer.
It’s still a multinational enterprise though, with all the problems that it entails (corporate restructuring every 2-3 years, anyone?)
These positions will most likely (I’m not employed there anymore so this is just a guess) be for their new Copenhagen office, London office or Shanghai. They also just recently opened up their new corporate headquarters in Billund and will be looking to put people there.
Tech talent is hard to come by in Denmark in general these days, but The LEGO Group has had additional issues with finding talent. The reason for this is that they insist people move to Billund - something no sane Dane would ever do, unless they really, really wanted to work for LEGO.
Their rates are “fine” though. Far from being the best, but fine. Their benefits are awesome though.
Last I heard, they were forcing people back to the office in a “hybrid” setup. 2 days remote, 3 days in the office.
They’ve also traditionally have low employee churn - 10, 20 and 40 yearn anniversaries are very, very common.
He’s been expelled from the Debian project/community (source: https://www.debian.org/News/2021/20211117) and he’s in pretty bad standing with Free Software Foundation Europe.
I feel like the article missed out on mentioning one key thing: Using a deny-list doesn’t work. It’s much more viable to default block and allow the stuff you know you’ll allow. Defaulting to allow and blocking stuff you don’t want is how you end up being owned by rot13.
Please note that that is not what I’ve meant. I’ve updated my comment with a bit more info.
Run some test on the list before using it, to make sure your own assets isn’t mentioned in there. If you don’t, you end up creating a DOS vulnerability in your system :D
Depending on how this project is structured, it wouldn’t have to process your GDPR request.
Edit: I was only partially correct. According to Article 2, Point 2C, the regulation (GDPR) does not apply to the processing of personal data “ by a natural person in the course of a purely personal or household activity”
So if this project can be viewed as a personal project (which I suppose it could, in theory…), then it wouldn’t have to comply.
At another place, ~400 employees, we’re allowed to have team managed projects (that we can customize to our hearths content) and company managed projects.
For enterprise use, I can highly recommend Crowdstrike Falcon.
In Kubernetes, secrets are base64 encoded, so they are quite secure.
The only protection I can think of is:
* The occasional glance at your screen.
* Injection attack (to some degree)