| Summary: | keygen-comment.sh failure | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | balu <balu.gajjala> | ||||
| Component: | Regression tests | Assignee: | Assigned to nobody <unassigned-bugs> | ||||
| Status: | CLOSED WORKSFORME | ||||||
| Severity: | minor | CC: | balu.gajjala, djm, dtucker | ||||
| Priority: | P5 | ||||||
| Version: | 8.6p1 | ||||||
| Hardware: | Other | ||||||
| OS: | Windows 10 | ||||||
| Attachments: |
|
||||||
|
Description
balu
2021-04-27 11:39:58 AEST
Just to make it clear.
Without \, it works perfectly fine.
$ egrep "^([0-9]+) SHA256:(.){43} ${comment} (.*)\$" ./ssh-ed25519-fgp
256 SHA256:LitlXmGRuL7VHjLgcZLMVa+OGnAZQZjypegmEFMZwZ0 foo bar (ED25519)
Administrator@balu-saw /cygdrive/c/Users/Administrator/Desktop/balu/openssh/code/master_branch/openssh-portable/regress/temp_test
If I have \ (as in test cases) then it fails
$ egrep "^([0-9]+) SHA256:(.){43} ${comment} \(.*\)\$" ./ssh-ed25519-fgp
Administrator@balu-saw /cygdrive/c/Users/Administrator/Desktop/balu/openssh/code/master_branch/openssh-portable/regress/temp_test
I have "egrep -V" output on my cygwin window in the issue description.
Created attachment 3503 [details]
Screenshot
Attached is the screenshot that shows the cygwin output where test fails with egrep error.
We regularly test the main tree on Cygwin (current version as of a couple of weeks ago) and it passes. (In reply to balu from comment #1) > If I have \ (as in test cases) then it fails [...] > I have "egrep -V" output on my cygwin window in the issue > description. Line continuation with a final backslash is a function of the shell, not of grep. Does your keygen-comment.sh contain only Unix-style newlines and not Windows-style CR/NL ? I could imagine that causing a problem. Closing for lack of followup closing bugs resolved before openssh-8.9 |