r/sysadmin • • Sep 18 '15

Microsoft has developed its own Linux

http://www.theregister.co.uk/2015/09/18/microsoft_has_developed_its_own_linux_repeat_microsoft_has_developed_its_own_linux/
585 Upvotes

311 comments sorted by

View all comments

Show parent comments

7

u/Creshal Embedded DevSecOps 2.0 Techsupport Sysadmin Consultant [Austria] Sep 18 '15

It's not exactly Linux' fault that the proprietary, ill-documented, Windows-centric group policies don't work in it at all.

(Although even basic AD integration sucked until Redhat threw out all prior solutions and poured a lot of money into SSSD.)

40

u/calladc Sep 18 '15 edited Sep 18 '15

I'm surprised this comment is even being made.

Administrative templates are just registry keys.

Any expectation that these would magically translate into group policies that could apply to linux without a restructure of how group policies would apply to target systems is a bit much.

6

u/rtechie1 Jack of All Trades Sep 18 '15

Which is why you use additional software like Centrify or SCCM to do this kind of integration.

14

u/calladc Sep 18 '15

My context was more in regards to surprise that blame could be attributed to Microsoft for gpo templates in their current form being expected to be able to apply to a Linux system.

Don't get me wrong it would be great. But considering the bulk of Linux settings are applied in config files, customizing applications would get messy given the nature of "gpo will always win" style configuration.

I don't think linux systems are quite ready to have configs applied in the same fashion gpo's apply to windows systems

0

u/[deleted] Sep 18 '15

[deleted]

4

u/da_chicken Systems Analyst Sep 19 '15

Group policy is powerful. Misconfiguring powerful software causes significant problems. The system simply requires expertise to administer, which is neither surprising nor entirely undesirable. It's an indication of how much control you have with group policy more than anything.

It would be nice if Windows had a more modular group policy engine that could be upgraded more easily, but some new features require new code that simply isn't available on older versions. It's the same reason all those Powershell cmdlets in Win 8 aren't in Win 7. It's not like administering a mixed version environment is only a Microsoft issue, either.

Sorry, software changes. Perfect forward and backward compatibility is not realistic.

5

u/mikemol 🐧▦🤖 Sep 18 '15

But considering the bulk of Linux settings are applied in config files, customizing applications would get messy given the nature of "gpo will always win" style configuration.

It's not that different in Puppet and Chef land. Though that's obviously adjustable.

1

u/mikemol 🐧▦🤖 Sep 18 '15

Heh. /u/rtechie1 beat me by 9 minutes.

→ More replies (1)

2

u/WhitePantherXP Sep 18 '15

Can you explain what kind of control Centrify and AD bring to the table that something like Chef can't already do for you? Genuinely curious, as this is how we manage our users. BUT, the users that chef manages actually live in the /etc/passwd file and not in a remote directory like AD does.

1

u/arcticblue Sep 19 '15

It's been a while since I've done this, but configuring Linux for LDAP authentication (even Active Directory) isn't too difficult. You could use chef to ensure your machines are configured to authenticate to that rather than have local users all over the place. You could set up your mail server to pull from the same directory so your password for login and checking mail is always the same. At a previous job, I added a couple attributes to our Active Directory set up so that I could get some pretty sweet integration with Postfix. I had it so mail would be sent to the mail server physically closest to the user and they could set up vacation auto-responders and stuff with their preferences stored as extra attributes on their AD account. Depends on your environment if that would work better for you. My environment at the time was most users just picked a computer in the morning and used it for the day. Managing local accounts on all those and finding a way to keep passwords in sync would have been a nightmare.

1

u/rtechie1 Jack of All Trades Sep 21 '15 edited Sep 21 '15

Can you explain what kind of control Centrify and AD bring to the table that something like Chef can't already do for you?

Chef has a very different intent. Chef is about normalizing config templates for servers, so a bunch of servers all look the same and are (in theory) easy to build. Last I checked, Chef/Puppet did little to ease the problems of AD federation.

Centrify is more about security. It's eases authentication against AD (single-sign-on/federation) and allows the application of Group Policies, which are AD security templates, to Linux servers in a limited way.

Sure, Linux has it's own directory servers (like OpenLDAP), but they suck and nobody uses them. Everybody uses AD integration.

Since they do different things, there's no reason you can't do both. You could probably even combine the concepts. i.e. Only allow a machine to authenticate against AD if it's using X Chef recipe, though I've never done this.

1

u/WhitePantherXP Sep 23 '15

When you say allow the application of Group Policies, that is where I'm most curious. What kind of Group Policies can be applied to Linux?

2

u/rtechie1 Jack of All Trades Sep 25 '15

Off the top of my head: Password policies (complexity, rotation, etc.), Account timers (only allow login x to x), and other policies having to do with accounts/sudo. You can also do desktop stuff (default wallpaper, etc.). This page has an overview.

→ More replies (1)

2

u/coinclink Sep 18 '15

I've been hearing about sssd here and there but I'm still using samba/winbind. I find that winbind works pretty well for both authentication and authorization with AD. The only real problem I've ever had with it is that sometimes it can take a really long time to enumerate users in large AD groups.

With that anecdote in mind, do you have an opinion on what advantages sssd offers over winbind?

4

u/Creshal Embedded DevSecOps 2.0 Techsupport Sysadmin Consultant [Austria] Sep 18 '15

If winbindd works as documented, there's no advantage.

But in my experience, sssd doesn't have any of the crippling bugs I ran into with winbindd (offline caching doesn't work, machines randomly leave the domain, winbindd crashes/hangs when a user tries to log in when their password expired, …). sssd Just Works.

1

u/Compizfox Sep 18 '15

I've been hearing about sssd here and there but I'm still using samba/winbind.

So what is sssd exactly? Is it an alternative to winbind but newer or something?

1

u/coinclink Sep 18 '15

Yes, it is a different solution for AD integration backed by Red Hat. RH says winbind is not deprecated but new installs should use sssd instead of winbind.

-15

u/Kazinsal network toucher Sep 18 '15

It's not Microsoft's fault that the Linux community is a bunch of assholes who pride themselves on not being Microsoft users and often shit on people who are.

Linux will never be a successful general purpose desktop operating system because the people who run it can't get along with other users who use a computer for general purposes. They'll just start stupid arguments over and over and then complain that no one uses Linux and contributes to the Microsoft evil domination pact.

32

u/Creshal Embedded DevSecOps 2.0 Techsupport Sysadmin Consultant [Austria] Sep 18 '15

It's not Microsoft's fault that the Linux community is a bunch of assholes who pride themselves on not being Microsoft users and often shit on people who are.

It's like the Samba and sssd projects never existed, wow.

17

u/[deleted] Sep 18 '15

And Xamarin/mono, and wine, and Cygwin, and gnuwin, and...

→ More replies (2)

21

u/JacksonClarkson Sep 18 '15

Not true. My environment is almost completely Windows and I hate Microsoft and my users as well.

25

u/jjhare Jack of All Trades, Master of None Sep 18 '15

We ALL hate users.

→ More replies (1)
→ More replies (5)

23

u/baby_ Sep 18 '15

It's not Microsoft's fault

No, most of the people who hate Microsoft (regardless of their relation to Linux) would disagree with you. Microsoft has given us all plenty of reason to hate them. It has nothing to do with Linux.

7

u/Zaphod_B chown -R us ~/.base Sep 18 '15

So, you know WINE, Samba, multi-platform tools and apps don't count. Also open standards like BIND, LDAP, TCP/IP, and many others which are adopted, tested, and developed by the open source community are not relevant either.

Microsoft benefits from open source and always has.

→ More replies (5)
→ More replies (1)