3 ms·

Indeed. The amount of "new tech" around auth leaves me head scratching. So many of the problems these start-up types are trying to solve have been solved by som

Indeed. The amount of "new tech" around auth leaves me head scratching. So many of the problems these start-up types are trying to solve have been solved by something like a well maintained Active Directory 10+ years ago. Group permission, PAM, SSO, etc. It's like these developers have never been exposed to Active Directory ever in their life...

TeMPOraL 5y ago
The other day I got around to finally learn some COM/DCOM, and realized Windows had microservices built in for 2+ decades, and with better protocols and security...
- flukus 5y ago
  Recently I ported a suite of 30 year old c/c++ programs, each one was deployable and runable on their own and communicated via sockets, microservices from the early 90's. Likewise FaaS doesn't add much that couldn't be done via apache cgi in the 90's.
  - dvfjsdhgfv 5y ago
    Was the communication encrypted?
- dvfjsdhgfv 5y ago
  How long ago did you learn that? Because back in the day I didn't know even one developer who wouldn't curse when working with DCOM/Corba implementations because of convoluted complexity, bugs, and problems with debugging.
  - TeMPOraL 5y ago
    Less than a year ago. I've been using it a little here and there for almost two decades - DirectX is accessed and operated through COM API - but I never bothered to actually learn it in depth, until I had to jump straight into debugging obscure errors in an application that used a DCOM-based service. > Because back in the day I didn't know even one developer who wouldn't curse when working with DCOM/Corba implementations because of convoluted complexity, bugs, and problems with debugging. Yeah, I got that impression about COM through osmosis over the years. But come to think of it, isn't the exact same thing happening with the current trend of microservices, and super-convoluted stacks of Docker containers and Kubernetes? So perhaps the problem ultimately wasn't with COM per se :).
908B64B197 5y ago
Windows isn't used in academia. So you get new grads that are re-inventing the wheel.
dvfjsdhgfv 5y ago
I'm not sure I understand your comment. Active Directory is Microsoft's proprietary tech that is a modification of the Kerberos standard, reimplemented most notably in Samba, but client solutions (open and proprietary) also exist. Group permissions predate AD by decades, PAM by a few years. SSO in today's form is a web phenomenon, so a web-oriented solution makes more sense, and there is a lot of work being done in this direction.
- throwaway0xa 5y ago
  >Active Directory is Microsoft's proprietary tech that is a modification of the Kerberos standard And LDAP, and some DNS, and certs, etc. It's not just Kerberos; you're sounding ignorant here. >Group permissions predate AD by decades No one said otherwise, but it goes beyond basic POSIX groups with things like nested groups, delegated group permissions, etc. >SSO in today's form is a web phenomenon So is AD's... Basically, you're proving my point.

TeMPOraL 5y ago

The other day I got around to finally learn some COM/DCOM, and realized Windows had microservices built in for 2+ decades, and with better protocols and security...

flukus 5y ago
Recently I ported a suite of 30 year old c/c++ programs, each one was deployable and runable on their own and communicated via sockets, microservices from the early 90's. Likewise FaaS doesn't add much that couldn't be done via apache cgi in the 90's.
- dvfjsdhgfv 5y ago
  Was the communication encrypted?
dvfjsdhgfv 5y ago
How long ago did you learn that? Because back in the day I didn't know even one developer who wouldn't curse when working with DCOM/Corba implementations because of convoluted complexity, bugs, and problems with debugging.
- TeMPOraL 5y ago
  Less than a year ago. I've been using it a little here and there for almost two decades - DirectX is accessed and operated through COM API - but I never bothered to actually learn it in depth, until I had to jump straight into debugging obscure errors in an application that used a DCOM-based service. > Because back in the day I didn't know even one developer who wouldn't curse when working with DCOM/Corba implementations because of convoluted complexity, bugs, and problems with debugging. Yeah, I got that impression about COM through osmosis over the years. But come to think of it, isn't the exact same thing happening with the current trend of microservices, and super-convoluted stacks of Docker containers and Kubernetes? So perhaps the problem ultimately wasn't with COM per se :).

908B64B197 5y ago

Windows isn't used in academia. So you get new grads that are re-inventing the wheel.

dvfjsdhgfv 5y ago

I'm not sure I understand your comment. Active Directory is Microsoft's proprietary tech that is a modification of the Kerberos standard, reimplemented most notably in Samba, but client solutions (open and proprietary) also exist. Group permissions predate AD by decades, PAM by a few years. SSO in today's form is a web phenomenon, so a web-oriented solution makes more sense, and there is a lot of work being done in this direction.

throwaway0xa 5y ago
>Active Directory is Microsoft's proprietary tech that is a modification of the Kerberos standard And LDAP, and some DNS, and certs, etc. It's not just Kerberos; you're sounding ignorant here. >Group permissions predate AD by decades No one said otherwise, but it goes beyond basic POSIX groups with things like nested groups, delegated group permissions, etc. >SSO in today's form is a web phenomenon So is AD's... Basically, you're proving my point.