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

unclear when config values are stored/used/etc. #4

Open
zenfish opened this issue Dec 23, 2022 · 0 comments
Open

unclear when config values are stored/used/etc. #4

zenfish opened this issue Dec 23, 2022 · 0 comments

Comments

@zenfish
Copy link

zenfish commented Dec 23, 2022

Perhaps the pyipmi.conf file should be updated only on successful attempts? I'm not sure the big win on caching the last unsuccessful attempt. In addition once it's written to, it seems to not fill in values for sections that aren't valid/just defaults, like after a -I lanplus command the -I lan gets filled in with nonsense.

The using cached passwords is interesting... I'm on the fence myself, but if you're going to do it, I'd say you may as well go all the way, and save for individual IPs/hosts within the various interfaces, like:

[lan]

     [10.0.0.1]
        user = root
        password = root123
        auth = md5
        port = 623

    [192.0.168.1]
        user = admin
        password = admin
        auth = md5
        port = 666
....

(Maybe have a --dangerous flag to save passwords for all hosts ;))

You could also put behavior variables in the [global] section, like [always-force], [CIPHER_SUITE], [port] (can be overridden by individual targets), etc., etc.

(I'm not sure what the no_ping option means.)

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

No branches or pull requests

1 participant