Great, thanks Slaven!
Em sexta-feira, 26 de abril de 2019 08:02:42 BRT, Slaven Rezic
escreveu:
> Slaven Rezic hat am 6. April 2019 um 10:14 geschrieben:
>
>
> > Andreas Koenig hat am 6. April
> > 2019 um 08:27 geschrieben:
> >
> >
> > > On Fri, 5 Apr 2019 23:32:11 -0300,
Em 06/04/2019 03:27, Andreas Koenig escreveu:
> I was wandering if there is anything we could do to avoid having the
> same thing happening. Of course, there is very little we could do if
> something like that happened at the code repository, but there are at
> least two things
On 06/04/2019 03:32, Alceu Rodrigues de Freitas Junior via
cpan-testers-discuss wrote:
Hello guys,
Did you have the chance to read about this backdoor found in a popular
Ruby gem?
https://www.zdnet.com/article/backdoor-code-found-in-popular-bootstrap-sass-ruby-library/
I was wandering if
> On Fri, 5 Apr 2019 23:32:11 -0300, Alceu Rodrigues de Freitas Junior via
> cpan-testers-discuss said:
> Hello guys,
> Did you have the chance to read about this backdoor found in a popular
> Ruby gem?
>
It would be excellent, but not trivial, to wrap all smoke tests in some
sort of security policy.
In the example below, this wrapper would look for attempts to reach out
over the network, or ports being opened by the code.
This could be compared to something defined by the author, either via
Hello guys,
Did you have the chance to read about this backdoor found in a popular
Ruby gem?
https://www.zdnet.com/article/backdoor-code-found-in-popular-bootstrap-sass-ruby-library/
I was wandering if there is anything we could do to avoid having the
same thing happening. Of course, there
