Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 23 |
Nodes: | 6 (0 / 6) |
Uptime: | 50:05:25 |
Calls: | 583 |
Files: | 1,138 |
Messages: | 111,306 |
For latest version of INN2 in Debian stable.
I think using ckpasswd is the most viable option for authentication since it is simple to add and remove users and it is a flat text file without database bugs and vulnerabilities.
I need to prevent all non-authenticated users from posting to newsgroups and authenticate via ckpasswd.
How do I configure INN2 so that I can add users with ckpasswd and force INN2 to authenticate via ckpasswd?
If there is a better method I am all ears. Please don't suggest some 3rd party program that is not included in the Debian stable repos. Please don't suggest something that uses a database or some other attack surface generator. I'm not interested in complicated stuff like that.
I added this to readers.conf:
auth: "/usr/lib/news/bin/auth/passwd/ckpasswd -f /etc/news/userdb"
I created a test user and got auth failure.
~ htpasswd -nbd test test > /etc/news/userdb
Hi,I pasted this into readers.conf, removing all other lines. I still get the message, "authentication will fail."
I added this to readers.conf:
auth: "/usr/lib/news/bin/auth/passwd/ckpasswd -f /etc/news/userdb"
What is the whole contents of your readers.conf file?
It needs at least something like:
auth "users" {
auth: "ckpasswd -f /etc/news/userdb"
default: "<unauthenticated>"
}
access "authenticatedpeople" {
users: "*"
newsgroups: "*"
}
access "restrictive" {
users: "<unauthenticated>"
newsgroups: "!*"
}
See https://www.eyrie.org/~eagle/software/inn/docs/readers.conf.htmlIt's not that I need an explanation of the rights--I need an explanation of configuration that will actually work. An example of a working configuration that is working in real life on an active install would be helpful.
The rights for authenticated people (and for unauthenticated people)
have to be explained.
I created a test user and got auth failure.
Here, if you successfully authenticate with the "test" user, his
assigned identity is "test" in the "users" keyword of access blocks.
When authentication fails, the identity is "<unauthenticated>" (the
default value of the auth block).
My goals are simple:~ htpasswd -nbd test test > /etc/news/userdb
More secure hashes are recommended, like ones obtained with:
openssl passwd -5 test
https://www.eyrie.org/~eagle/software/inn/docs/ckpasswd.html
Authentication works with the below configuration in readers.conf.
I suppose INN is choosing the first one that applies ?
I needed to include the full path to ckpasswd as it is not in system path.
I also needed to make sure I was entering into mode reader before authenticating.
I will follow your advice for a more secure password hashing scheme.
The default one does look rather weak.