Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I am having a great deal of difficulty getting an authentication scheme working for squid.
It seems that Kerberos is necessary to get this off the ground but the /etc/krb5.conf file generates the following error:
"Improper format of Kerberos configuration file while initializing context, aborting"
I have tried editing this file in the following manner:
I have removed a little rant about obfuscated conf files because it serves no purpose, but, honestly, surely this deserves a prize as one of the most obscure configuration formats?
The error message is also completely uninformative; I'm assuming that the /etc/krb5.conf file is at fault?
Also I had to run "krb5_newrealm" to initialise the KDC database.
This give the following useful tips:
Quote:
# krb5_newrealm
This script should be run on the master KDC/admin server to initialize
a Kerberos realm. It will ask you to type in a master key password.
This password will be used to generate a key that is stored in
/etc/krb5kdc/stash. You should try to remember this password, but it
is much more important that it be a strong password than that it be
remembered. However, if you lose the password and /etc/krb5kdc/stash,
you cannot decrypt your Kerberos database.
Loading random data
Initializing database '/var/lib/krb5kdc/principal' for realm 'IQETD.LAN',
master key name 'K/M@IQETD.LAN'
You will be prompted for the database Master Password.
It is important that you NOT FORGET this password.
Enter KDC database master key:
Re-enter KDC database master key to verify:
Now that your realm is set up you may wish to create an administrative
principal using the addprinc subcommand of the kadmin.local program.
Then, this principal can be added to /etc/krb5kdc/kadm5.acl so that
you can use the kadmin program on other computers. Kerberos admin
principals usually belong to a single user and end in /admin. For
example, if jruser is a Kerberos administrator, then in addition to
the normal jruser principal, a jruser/admin principal should be
created.
Don't forget to set up DNS information so your clients can find your
KDC and admin servers. Doing so is documented in the administration
guide.
Don't let anyone tell you that configuring Kerberos is straightforward.
I'm using http://www.ornl.gov/~jar/HowToKerb.html, but it throws up more questions than it actually answers, it gives incorrect syntax and glosses over crucial configuration requirements with barely a mention. (I suspect it is some years out of date).
If anyone knows of a reasonably straightforward walkthrough on installing this complete mess, please post it.
The entire Kerberos project had been concocted in a pub by a group of BOFH looking for a few cheap laughs watching would-be users floundering in a sea of disjointed and obfuscated TLAs (three lettered acronyms). Very amusing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.