Mailing List Archive

https://bugzilla.mindrot.org/show_bug.cgi?id=3305

--- Comment #1 from balu <balu.gajjala@gmail.com> ---
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.

--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs

https://bugzilla.mindrot.org/show_bug.cgi?id=3305

--- Comment #2 from balu <balu.gajjala@gmail.com> ---
Created attachment 3503
--> https://bugzilla.mindrot.org/attachment.cgi?id=3503&action=edit
Screenshot

Attached is the screenshot that shows the cygwin output where test
fails with egrep error.

--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs

https://bugzilla.mindrot.org/show_bug.cgi?id=3305

Darren Tucker <dtucker@dtucker.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |dtucker@dtucker.net

--- Comment #3 from Darren Tucker <dtucker@dtucker.net> ---
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.

--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs