Recall: DAST related issue

[GUO Leo (BST/ECS2-CN) via Cygwin]

GUO Leo (BST/ECS2-CN) would like to recall the message, "DAST related issue ".

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

RE: DAST related issue

[GUO Leo (BST/ECS2-CN) via Cygwin]

Hi ,

I can not start DAST ,Every time after running for a while , the start process 
would suddenly Flashback. Please refer 1st &2nd file attached

Even with restart /follow some methods on docupedia, still can not resolve this 
problem ;
Few assistance about this aspect available ,After checking related access & 
DAST WI tips , no problem & hints found
After several trail , I reinstall DAST , some bugs appear at install interface 
, please refer 3rd attached file .
Could you do me a favor how to eliminate this or get DAST reinstalled ?


Best regards,

Leo GUO

Engineering Consumer Sensors 2 of BST China (BST/ECS2-CN)
Bosch Automotive Products (Suzhou) Co., Ltd. | No. 126, Su Hong Xi Road
Suzhou Industrial Park | Suzhou P.R.China | P.R.CHINA
Tel. +86 512 6890-7273 | leo@cn.bosch.com

Registered Office: Suzhou, Registration Court: State Administration of Industry 
& Commerce, P.R.China
Board of Directors: Yudong Chen, Georges Andary, Ying Zhang
​

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: Cygwin setup reporter as malware

[Bill Stewart via Cygwin]

On Wed, Dec 7, 2022 at 9:21 AM Sylwester Rutkowski wrote:

The setup-x86_64.exe is reported as malicious at
> https://www.virustotal.com/gui/file/edd0a64dc65087ffe453ca94b267169b39458a983b29ac31320fcaa983d0f97e/detection
>
> Can this be resolved somehow?


This is, of course, a false positive.

There are basically two things you can do:

1. Exempt it from your scanner.

2. Report it to the vendor as a false positive.

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: Cygwin setup reporter as malware

[Dan Harkless via Cygwin]

On 12/7/2022 8:20 AM, Sylwester Rutkowski via Cygwin wrote:Hi,

The setup-x86_64.exe is reported as malicious at 
https://www.virustotal.com/gui/file/edd0a64dc65087ffe453ca94b267169b39458a983b29ac31320fcaa983d0f97e/detection

Can this be resolved somehow?


No.  It's normal and common for software like Cygwin, which has the 
power to be used maliciously (as opposed to, say, a Minesweeper game or 
something), to have false positives on VirusTotal for a handful of 
vendors.  I've never heard of SecureAge or Trapmine (hmm, maybe it 
*would* flag Minesweeper...), and I'm pretty well educated in the 
anti-malware space, so if it were me, I'd just ignore those false 
positives and pay attention to the credible AV software results (and the 
Community Score).


If you have some corporate policy requiring things to have 0 detections 
on VirusTotal or something, your only recourse is to contact the 
SecureAge and Trapmine vendors and convince them somehow to fix their 
false positives.


--
Dan Harkless
http://harkless.org/dan/


--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Performance regression in cygwin 3.4.0

[tryandbuy via Cygwin]

Reading from stdin is very slow when a process runs outside of Cygwin Terminal.

Steps to reproduce:
1. Create "test.txt" file using python code:
long_text = "10" * 2500
with open(r'test.txt', 'w') as f:
for i in range(5000):
f.write('KEY%03d: %d => %s\n' % (i % 100, i, long_text))

2. Install "cygwin" package version > "3.3.6-1"
3. Open windows command prompt (cmd.exe)
4. Enter command:
type test.txt | c:\cygwin64\bin\wc.exe -l

When running the same command (use cat instead of type) on the Cygwin Terminal, 
no performance issues observed.

The last version of cygwin package without issues: 3.3.6-1
Versions of cygwin package with issues: 3.4.x - 3.5.x

P.S. I tested this combinations of pipings:
cygwin_prog | win_prog# no issues
win_prog | cygwin_prog# has issues when running in windows command prompt, 
no issues in Cygwin Terminal
cygwin_prog | cygwin_prog # has issues  when running in windows command prompt, 
no issues in Cygwin Terminal


-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

RE: [EXTERNAL] Re: gcc -pg broken after cygwin update?

[Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin]

> contains patches dropping W7 and W8 support:

Hmm... I understood that "dropping support" was not something that would 
_require_ newer OS,
but that it may not work (or not guaranteed to work, patches not checked for 
compatibility, etc)
on the older OSes...  Are you saying that W7 and W8 would be actively rejected? 
 (Like some
M$ products do so now.)

Anton Lavrentiev
Contractor NIH/NLM/NCBI


-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Cygwin setup reporter as malware

[Sylwester Rutkowski via Cygwin]

Hi,

The setup-x86_64.exe is reported as malicious at 
https://www.virustotal.com/gui/file/edd0a64dc65087ffe453ca94b267169b39458a983b29ac31320fcaa983d0f97e/detection

Can this be resolved somehow?

Thanks,
Sylwester


-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: gcc -pg broken after cygwin update?

[Corinna Vinschen via Cygwin]

On Dec  7 15:05, Daniel Abrahamsson via Cygwin wrote:
> > On Dec  7 12:50, Corinna Vinschen via Cygwin wrote:
> > > On Dec  7 08:58, Daniel Abrahamsson via Cygwin wrote:
> > > > Hi,
> > > > 
> > > > This morning I updated cygwin, and after that gcc started producing 
> > > > errors like this:
> > > > 
> > > > >  gcc -Wall -Wextra -Werror -pedantic -Wno-unused-parameter -g -pg 
> > > > > -DVERBOSE -c -o ../obj/.o .c
> > > > > gcc -o ../bin/ ../obj/.o -pg
> > > > > /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: 
> > > > > ../obj/.o: in function `exit_eval_failure':
> > > > /home/daab/dev/someproj/src/.c:17: undefined reference to 
> > > > `__fentry__'
> > > > [...]
> > > Thanks for the report.
> > > 
> > > This is a dumb bug I introduced into the build system in 3.4.0.  I fixed
> > > that in the git repo, but the automated build of the matching test
> > > [...]
> > Automated builds have been picked up again and the Cygwin test package
> > 3.5.0-0.17.g95f5b0a62036 should be available later today.  You can
> > install it using setup.exe, just like any other test release.
> >
> > Don't forget to install the matching cygwin-devel package, too, that's
> > the one containing the library libgmon.a, which is what gets linked in
> > with `gcc -pg'.
> 
> I can confirm 3.5.0-0.17.g95f5b0a62036 solves the issue with the "-pg"
> flag. Thank you!

Thanks for your feedback!


Corinna

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: [EXTERNAL] Re: gcc -pg broken after cygwin update?

[Corinna Vinschen via Cygwin]

On Dec  7 14:47, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > provided you run at least Windows 8.1
> 
> Why would that be a requirement?

Test releases are created from the master branch which already
bumped version to 3.5.0 and contains patches dropping W7 and W8
support:

https://cygwin.com/pipermail/cygwin-announce/2022-December/010821.html


Corinna

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

RE: gcc -pg broken after cygwin update?

[Daniel Abrahamsson via Cygwin]

> On Dec  7 12:50, Corinna Vinschen via Cygwin wrote:
> > On Dec  7 08:58, Daniel Abrahamsson via Cygwin wrote:
> > > Hi,
> > > 
> > > This morning I updated cygwin, and after that gcc started producing 
> > > errors like this:
> > > 
> > > >  gcc -Wall -Wextra -Werror -pedantic -Wno-unused-parameter -g -pg 
> > > > -DVERBOSE -c -o ../obj/.o .c
> > > > gcc -o ../bin/ ../obj/.o -pg
> > > > /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: 
> > > > ../obj/.o: in function `exit_eval_failure':
> > > /home/daab/dev/someproj/src/.c:17: undefined reference to 
> > > `__fentry__'
> > > 
> > > If I drop the "pg" flags from the compilation and linking stages, 
> > > everything works.
> > > 
> > > I typically update cygwin packages once per week, but now it has been
> > > maybe a month since I last updated. As far as I can tell from the
> > > cygwin-announce archives, there has not been any gcc updates in that
> > > period, but I do note that cygwin itself has been updated. Could that
> > > be related?
> 
> > Thanks for the report.
> > 
> > This is a dumb bug I introduced into the build system in 3.4.0.  I fixed
> > that in the git repo, but the automated build of the matching test
> > release cygwin-3.5.0-0.17.g95f5b0a62036 is currently not building due to
> > some hiccup on cygwin.com.  I'll send a new mail as soon as this is
> > fixed and you can test it (provided you run at least Windows 8.1).
>
> Automated builds have been picked up again and the Cygwin test package
> 3.5.0-0.17.g95f5b0a62036 should be available later today.  You can
> install it using setup.exe, just like any other test release.
>
> Don't forget to install the matching cygwin-devel package, too, that's
> the one containing the library libgmon.a, which is what gets linked in
> with `gcc -pg'.

I can confirm 3.5.0-0.17.g95f5b0a62036 solves the issue with the "-pg" flag. 
Thank you!

Regards,
Daniel

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

RE: [EXTERNAL] Re: gcc -pg broken after cygwin update?

[Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin]

> provided you run at least Windows 8.1

Why would that be a requirement?

Anton Lavrentiev
Contractor NIH/NLM/NCBI


-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: gcc -pg broken after cygwin update?

[Corinna Vinschen via Cygwin]

On Dec  7 12:50, Corinna Vinschen via Cygwin wrote:
> On Dec  7 08:58, Daniel Abrahamsson via Cygwin wrote:
> > Hi,
> > 
> > This morning I updated cygwin, and after that gcc started producing errors 
> > like this:
> > 
> > >  gcc -Wall -Wextra -Werror -pedantic -Wno-unused-parameter -g -pg 
> > > -DVERBOSE -c -o ../obj/.o .c
> > > gcc -o ../bin/ ../obj/.o -pg
> > > /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: 
> > > ../obj/.o: in function `exit_eval_failure':
> > /home/daab/dev/someproj/src/.c:17: undefined reference to 
> > `__fentry__'
> > 
> > If I drop the "pg" flags from the compilation and linking stages, 
> > everything works.
> > 
> > I typically update cygwin packages once per week, but now it has been
> > maybe a month since I last updated. As far as I can tell from the
> > cygwin-announce archives, there has not been any gcc updates in that
> > period, but I do note that cygwin itself has been updated. Could that
> > be related?
> 
> Thanks for the report.
> 
> This is a dumb bug I introduced into the build system in 3.4.0.  I fixed
> that in the git repo, but the automated build of the matching test
> release cygwin-3.5.0-0.17.g95f5b0a62036 is currently not building due to
> some hiccup on cygwin.com.  I'll send a new mail as soon as this is
> fixed and you can test it (provided you run at least Windows 8.1).

Automated builds have been picked up again and the Cygwin test package
3.5.0-0.17.g95f5b0a62036 should be available later today.  You can
install it using setup.exe, just like any other test release.

Don't forget to install the matching cygwin-devel package, too, that's
the one containing the library libgmon.a, which is what gets linked in
with `gcc -pg'.


Thanks,
Corinna

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: gcc -pg broken after cygwin update?

[Corinna Vinschen via Cygwin]

On Dec  7 08:58, Daniel Abrahamsson via Cygwin wrote:
> Hi,
> 
> This morning I updated cygwin, and after that gcc started producing errors 
> like this:
> 
> >  gcc -Wall -Wextra -Werror -pedantic -Wno-unused-parameter -g -pg -DVERBOSE 
> > -c -o ../obj/.o .c
> > gcc -o ../bin/ ../obj/.o -pg
> > /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: 
> > ../obj/.o: in function `exit_eval_failure':
> /home/daab/dev/someproj/src/.c:17: undefined reference to 
> `__fentry__'
> 
> If I drop the "pg" flags from the compilation and linking stages, everything 
> works.
> 
> I typically update cygwin packages once per week, but now it has been
> maybe a month since I last updated. As far as I can tell from the
> cygwin-announce archives, there has not been any gcc updates in that
> period, but I do note that cygwin itself has been updated. Could that
> be related?

Thanks for the report.

This is a dumb bug I introduced into the build system in 3.4.0.  I fixed
that in the git repo, but the automated build of the matching test
release cygwin-3.5.0-0.17.g95f5b0a62036 is currently not building due to
some hiccup on cygwin.com.  I'll send a new mail as soon as this is
fixed and you can test it (provided you run at least Windows 8.1).


Thanks,
Corinna

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

gcc -pg broken after cygwin update?

[Daniel Abrahamsson via Cygwin]

Hi,

This morning I updated cygwin, and after that gcc started producing errors like 
this:

>  gcc -Wall -Wextra -Werror -pedantic -Wno-unused-parameter -g -pg -DVERBOSE 
> -c -o ../obj/.o .c
> gcc -o ../bin/ ../obj/.o -pg
> /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: 
> ../obj/.o: in function `exit_eval_failure':
/home/daab/dev/someproj/src/.c:17: undefined reference to `__fentry__'

If I drop the "pg" flags from the compilation and linking stages, everything 
works.

I typically update cygwin packages once per week, but now it has been maybe a 
month since I last updated. As far as I can tell from the cygwin-announce 
archives, there has not been any gcc updates in that period, but I do note that 
cygwin itself has been updated. Could that be related?

Regards,
Daniel

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple