Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

Secrets with "\" char could not be opened #42

Open
vicioussn opened this issue Oct 21, 2019 · 3 comments
Open

Secrets with "\" char could not be opened #42

vicioussn opened this issue Oct 21, 2019 · 3 comments

Comments

@vicioussn
Copy link

The problem

If you create secret with "" char in the path, Cryptr cannot view that secret (although it's discoverable).

Environment

  • Cryptr version (or git revision) that exhibits the issue: 0.3.0
  • Desktop OS/version used to run Cryptr: Windows 10
  • Vault version: 1.2.3

Details

Obviously, "" is getting replaced to "/", just as "space" is replaced with underscore.

@jcrowthe
Copy link
Contributor

Hey, I'm not positive I understand as you reference different chars. Are you talking about an empty string being replaced with a forward slash? Or a backslash being replaced with a forward slash?

Vault does not accept backslashes in the names of secrets.

@vicioussn
Copy link
Author

vicioussn commented Jan 27, 2020

Hi!

GitHub removing backslash from my message. So, backslash is getting replaces with forward slash.

Vault does accept backslash in secret names. Take a look:
image

@lucasteinke
Copy link

GitHub removing backslash from my message.

You could use backticks (`code`) to enclose your backslash, gets rendered as \.

The secret in your screenshot gets displayed as something/domain\username but it should be something/domain/\username, is that correct?

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

No branches or pull requests

3 participants