Oper login issue about inspircd-docker

[DracoMilesX]

Ah ok thanks for the information got it to work now with ''.

Might as well be a suggestion that it automatic converts to hashed password? Dunno if it's even possible or requires to much work.

Still odd that it didn't accept the password for plain text and hashed from the opers.conf the first time. But w/e. The variables work

This container doesn't include anope or am I missing something?

[SISheogorath]

Oh, it is possible a misunderstanding.

You have to provide the hashed password. Not the cleartext one.

To create one, connect to the InspIRCd and use /mkpasswd hmac-sha256 yourpassword.

[SISheogorath]

After a check back I noticed that the documentation is not clear about it. Well extend it :)

[SISheogorath]

This container only contains InspIRCd. But @Adam- and me also work on an anope container.

We build the whole setup following most of the best practices of Docker official images and provide one process per container. Current ETA for a basically usable Anope container is 2 weeks.

You can already link Anope to this container by mounting your link configs to /inspircd/conf.d/. It'll automatically included.

[SISheogorath]

@DracoMilesX can you check the possible fix for this issue:

https://github.com/Adam-/inspircd-docker/blob/fix/issue-49/README.md

Would you say it's easier to find out, what you have to enter there?

[DracoMilesX]

@SISheogorath Yeah that looks better. Personally I would change the description to:

Hashed oper password

The wording kinda feels odd with the "for usage with /oper"

and modify the "/oper username password" to "/oper username plaintextpassword"

But this might just be me going full retard.

[SISheogorath]

Thanks for the feedback :) I think the example is a better solution than providing longer example values to replace :)