Skip to content

Expected behavior when no config files exist #34

@verdverm

Description

@verdverm

What is the expected behavior when neither of the identity files exist?

It seems that the NonExist errors are ignored and a default value is returned.

I'm trying to build some auth with fallback and the lack of error means I have to be aware of what files you are checking and make sure they don't exist.

From https://pkg.go.dev/github.com/kevinburke/ssh_config#GetStrict

The returned error will be non-nil if and only if a user's configuration file or the system configuration file could not be parsed, and u.IgnoreErrors is false.

I would expect that if neither file is found, then it should "fail to parse" and I would get an error.

Could we add some logic to https://github.com/kevinburke/ssh_config/blob/v1.1.0/config.go#L247 to return an error when both methods fail to find a file to parse?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions