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.

Sign up for GitHub

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

Jump to bottom

[All Beats] Keystore add hangs under Windows #18649

Closed
adriansr opened this issue May 20, 2020 · 6 comments · Fixed by #18654
Closed

[All Beats] Keystore add hangs under Windows #18649

adriansr opened this issue May 20, 2020 · 6 comments · Fixed by #18654
Labels
bug libbeat Team:Integrations Label for the Integrations team v7.7.1 v7.8.0

Comments

@adriansr
Copy link
Contributor

adriansr commented May 20, 2020 •
edited
Loading

Please include configurations and logs if available.

For confirmed bugs, please report:

  • Version: 7.7.0...master

  • Operating System: Windows

  • Discuss Forum URL: n/a

  • Steps to Reproduce:

    • Download 7.7.0 Beat of your choice (.zip)
    • Unpack
    • Run beatname keystore add ES_PWD
    • Answer y to create a keystore
    • In the password prompt, write something and press enter.
    • Nothing happens

The Beat seems stuck at some point. It can be killed by CTRL+C.

image

Reproduced in CMD.exe / Powershell and Windows 2012 - 2019

Works fine in 7.6.2
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 20, 2020
@andresrc andresrc added the Team:Integrations Label for the Integrations team label May 20, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label May 20, 2020
@adriansr
Copy link
Contributor Author

Seems caused by golang/go#36609

@adriansr adriansr changed the title [All Beats] Keystore add hangs under Windows [All Beats] Keystore add hangs under Windows May 20, 2020
@adriansr adriansr mentioned this issue May 20, 2020
Merged
@adriansr
Copy link
Contributor Author

A workaround is to use the -stdin flag

adriansr added a commit to adriansr/beats that referenced this issue May 20, 2020
@adriansr
Update golang.org/x/crypto
ba459a8 
This addresses a problem with crypto/ssh/terminal used as secure input
under Windows.

Fixes elastic#18649
@janniten
Copy link
Contributor

Using old and keystore (from version 7.6.2) and copying into the 7.7 installation also works :)

adriansr added a commit that referenced this issue May 20, 2020
@adriansr
Update golang.org/x/crypto (#18654)
2c90b6a 
This addresses a problem with crypto/ssh/terminal used as secure input
under Windows.

Fixes #18649
@adriansr adriansr mentioned this issue May 20, 2020
Merged
adriansr added a commit to adriansr/beats that referenced this issue May 20, 2020
@adriansr
Update golang.org/x/crypto (elastic#18654)
ea9c6e9 
This addresses a problem with crypto/ssh/terminal used as secure input
under Windows.

Fixes elastic#18649

(cherry picked from commit 2c90b6a)
adriansr added a commit to adriansr/beats that referenced this issue May 20, 2020
@adriansr
Update golang.org/x/crypto (elastic#18654)
2531b41 
This addresses a problem with crypto/ssh/terminal used as secure input
under Windows.

Fixes elastic#18649

(cherry picked from commit 2c90b6a)
@adriansr adriansr mentioned this issue May 20, 2020
Merged
adriansr added a commit to adriansr/beats that referenced this issue May 20, 2020
@adriansr
Update golang.org/x/crypto (elastic#18654)
c3516b5 
This addresses a problem with crypto/ssh/terminal used as secure input
under Windows.

Fixes elastic#18649

(cherry picked from commit 2c90b6a)
@adriansr adriansr mentioned this issue May 20, 2020
Merged
adriansr added a commit that referenced this issue May 21, 2020
@adriansr
Update golang.org/x/crypto (#18654) (#18670)
12ef93c 
This addresses a problem with crypto/ssh/terminal used as secure input
under Windows.

Fixes #18649

(cherry picked from commit 2c90b6a)
adriansr added a commit that referenced this issue May 22, 2020
@adriansr
Update golang.org/x/crypto (#18654) (#18671)
b4ee7d9 
This addresses a problem with crypto/ssh/terminal used as secure input
under Windows.

Fixes #18649

(cherry picked from commit 2c90b6a)
adriansr added a commit that referenced this issue May 22, 2020
@adriansr
Update golang.org/x/crypto (#18654) (#18673)
5dbed58 
This addresses a problem with crypto/ssh/terminal used as secure input
under Windows.

Fixes #18649

(cherry picked from commit 2c90b6a)
@hueyg
Copy link

hueyg commented Jun 12, 2020

I just encountered this today. While the stdin option allows you to get past the locked prompt it does not seem to have entered the correct value for the variable I was storing. Not sure of a way to verify, but I am stuck unless I hard code a password now.

@adriansr
Copy link
Contributor Author

Hi @hueyg ,

This is fixed in version 7.7.1.

If for whatever reason you don't want to upgrade, you can use 7.7.1 to create the keystore and then use the keystore file on an older version. But afaik this problem only affected 7.7.0 so I don't see an issue with upgrading.

leweafan pushed a commit to leweafan/beats that referenced this issue Apr 28, 2023
@adriansr
Update golang.org/x/crypto (elastic#18654) (elastic#18673)
342f2d7 
This addresses a problem with crypto/ssh/terminal used as secure input
under Windows.

Fixes elastic#18649

(cherry picked from commit cfccf22)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug libbeat Team:Integrations Label for the Integrations team v7.7.1 v7.8.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update golang.org/x/crypto adriansr/beats
5 participants
@andresrc @adriansr @elasticmachine @janniten @hueyg