Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide an HTTP interface, RM digest auth enforcement #641

Open
karlsebal-mcs opened this issue Feb 5, 2025 · 1 comment
Open

Provide an HTTP interface, RM digest auth enforcement #641

karlsebal-mcs opened this issue Feb 5, 2025 · 1 comment

Comments

@karlsebal-mcs
Copy link

karlsebal-mcs commented Feb 5, 2025

Please provide an http interface. Enforcing digest auth in the way it is done atm means restricting to one user and one password — which is not very secure at all, beside Apache claiming digest being even less secure than basic auth1. Running heritrix behind a proxy providing basic auth by itself and offloading the TLS makes this enforcement just a waste of computation power and developer time.

Thank you!

Footnotes

  1. This module implements HTTP Digest Authentication (RFC2617), and provides an alternative to mod_auth_basic where the password is not transmitted as cleartext. However, this does not lead to a significant security advantage over basic authentication. On the other hand, the password storage on the server is much less secure with digest authentication than with basic authentication. Therefore, using basic auth and encrypting the whole connection using mod_ssl is a much better alternative. src

@ato
Copy link
Collaborator

ato commented Feb 5, 2025

I would accept a pull request that added options to disable TLS and authentication provided they had suitably scary names. I would advise extreme care when disabling authentication, even if firewalled or bound to localhost, as the Heritrix UI allows execution of arbitrary code.

Also agree that since digest auth is deprecated it would be nice if basic was supported too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants