charlie.
November 22nd, 2006, 03:35 AM
A few years ago, I had never heard of Linux.
A few months ago, I had never used Linux.
A few weeks ago, I had only used Linux from the command line, through SSH, on a single Intranet web-server.
A few days ago, this all changed!
I have moved 99% of my development-and-administration work flow to my shiny-new-edgy-desktop. My Linux server is still up and kicking and doing a whole lot more than serving its original reason for being: our corporate Intranet. I've even ported my C++ code to Linux, learned sCons and bludgeoned my project into a state where it compiles, links, run and passes the tests on GCC 4.1. Perhaps there's some hope for Tux after all.
Operating systems are like cars. Once you've upgraded, you can't go back to that old bucket-o'-bolts. This is becoming increasingly apparent - every time I have to fight with my Windows desktops and domain controller on this network. I have seen a future for Linux on my network and my No.1 goal is to kill Active Directory. (AD is actually not the problem, it's all the **** that you have to run to make it work, like M$ solutions for DHCP and DNS that simply don't work properly or stop working intermittently for no apparent reason!)
My first goal is to learn a bit more about authentication (specifically distributed authentication schemes) on Linux - how it's supposed to be done. I started down this path by reading up on passwd, then an old dinosaur called NIS or Sun Yellow Pages. Neither of these appeared to be (A) modern or (B) particularly secure. I'm not quite sure where to go next.
What authentication systems should I be researching? Which ones are used today? In this age, the age of SSH and Kerberos, I expect something a little more elegant than NIS, with its unencrypted traffic and text file data storage.
Ultimately, I will have to find a way to allow my windows clients to authenticate against my Linux directory service.
Please help me know where to look next.
A few months ago, I had never used Linux.
A few weeks ago, I had only used Linux from the command line, through SSH, on a single Intranet web-server.
A few days ago, this all changed!
I have moved 99% of my development-and-administration work flow to my shiny-new-edgy-desktop. My Linux server is still up and kicking and doing a whole lot more than serving its original reason for being: our corporate Intranet. I've even ported my C++ code to Linux, learned sCons and bludgeoned my project into a state where it compiles, links, run and passes the tests on GCC 4.1. Perhaps there's some hope for Tux after all.
Operating systems are like cars. Once you've upgraded, you can't go back to that old bucket-o'-bolts. This is becoming increasingly apparent - every time I have to fight with my Windows desktops and domain controller on this network. I have seen a future for Linux on my network and my No.1 goal is to kill Active Directory. (AD is actually not the problem, it's all the **** that you have to run to make it work, like M$ solutions for DHCP and DNS that simply don't work properly or stop working intermittently for no apparent reason!)
My first goal is to learn a bit more about authentication (specifically distributed authentication schemes) on Linux - how it's supposed to be done. I started down this path by reading up on passwd, then an old dinosaur called NIS or Sun Yellow Pages. Neither of these appeared to be (A) modern or (B) particularly secure. I'm not quite sure where to go next.
What authentication systems should I be researching? Which ones are used today? In this age, the age of SSH and Kerberos, I expect something a little more elegant than NIS, with its unencrypted traffic and text file data storage.
Ultimately, I will have to find a way to allow my windows clients to authenticate against my Linux directory service.
Please help me know where to look next.