Ruby library infected ???
Hello! Today i have updated 64-bit Cygwin and my antivirus gave me an alert: --- cut --- FilenameRiskAction Risk Type Original LocationComputerUser Status rational.so Trojan.ADH Pending AnalysisFile; Virus C:\cygwin64\lib\ruby\2.0.0\mathn\ FEDINW7X64 p.fedin Infected --- cut --- Can anybody recheck this ? Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia
SSH key for upload access
Name: Dr. Volker Zell Package: tzcode BEGIN SSH2 PUBLIC KEY Comment: 2048-bit RSA, converted by vzell@leila from OpenSSH B3NzaC1yc2EDAQABAAABAQDIvwAJ4xrZ72Com6eAhaCgUVd+lQqWtWCi1TNN8q Wdzpj1L3CjDtZBCXto73SM6N73KjWkT+7Abo76DDGu67HtXVx670QmlaGCEz4Gjr5nhG/9 8uA4DCz1g8FOdjpR3ydPfsexidNLqPGSpW2Xc9ZN9SEGKCuYn9m8917I5o8oWgLbA515xs DrDFExNGh3sOCZIhao7gi92uALcO7R4Xc808geRlYEv8qSU6cWO93QZin1ZNkWVXE+1CjJ tkIDdYBeRQ7TIAyv7mIgQs1aVEWuSp/aqpS2cnb7QPxIFK+F9GVVgrO5TUFrsbPFylQKb2 GwJuCWV1+ARR3I9h4lMcl7 END SSH2 PUBLIC KEY
Re: SSH key for upload access
On 2014-11-10 08:09, Dr. Volker Zell wrote: Name: Dr. Volker Zell Package: tzcode BEGIN SSH2 PUBLIC KEY Comment: 2048-bit RSA, converted by vzell@leila from OpenSSH B3NzaC1yc2EDAQABAAABAQDIvwAJ4xrZ72Com6eAhaCgUVd+lQqWtWCi1TNN8q Wdzpj1L3CjDtZBCXto73SM6N73KjWkT+7Abo76DDGu67HtXVx670QmlaGCEz4Gjr5nhG/9 8uA4DCz1g8FOdjpR3ydPfsexidNLqPGSpW2Xc9ZN9SEGKCuYn9m8917I5o8oWgLbA515xs DrDFExNGh3sOCZIhao7gi92uALcO7R4Xc808geRlYEv8qSU6cWO93QZin1ZNkWVXE+1CjJ tkIDdYBeRQ7TIAyv7mIgQs1aVEWuSp/aqpS2cnb7QPxIFK+F9GVVgrO5TUFrsbPFylQKb2 GwJuCWV1+ARR3I9h4lMcl7 END SSH2 PUBLIC KEY Key added. -- Yaakov
Re: Ruby library infected ???
On 2014-11-10 07:04, Pavel Fedin wrote: Today i have updated 64-bit Cygwin and my antivirus gave me an alert: --- cut --- FilenameRiskAction Risk Type Original LocationComputerUser Status rational.so Trojan.ADH Pending AnalysisFile; Virus C:\cygwin64\lib\ruby\2.0.0\mathn\ FEDINW7X64 p.fedin Infected --- cut --- Can anybody recheck this ? https://cygwin.com/faq/faq.html#faq.setup.virus -- Yaakov
Re: Ruby library infected ???
Hello, Yaakov. Monday, November 10, 2014, 20:42:20 you wrote: https://cygwin.com/faq/faq.html#faq.setup.virus Oops, i am really sorry for hitting the FAQ and doing things absolutely opposite to what's suggested. :( Real programmers never have time to read docs... -- Kind regards, Pavel
cygwin beta packages
Two minor nits: The current beta packages contain a . in the release number. That dot is chopped off along with the anything that follows in some places during install in setup.exe. A better naming scheme would use a letter there, so perhaps 0b8 (I know that this doesn't produce problems since I've been packaging snapshots for local installation that way for a long time). Also, can the cygwin-devel package please get a source: line in setup.ini? Without it, I can't correctly parse setup.ini and I don't really want to special-case it. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: cygwin beta packages
Ken Brown writes: Apparently setup.exe doesn't parse the data for the cygwin package correctly, and its dependencies therefore don't get taken into account in computing the dependency order. To decide that, a formal definition of what is a permissible release number is required and I don't think that's written down someplace. I'm not sure if that's only in genini.pl, but when you manage to increment the releases to have second digits, sometimes these get sorted the wrong way (-1 before -10 IIRC). Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: cygwin beta packages
On 11/10/2014 1:31 PM, Achim Gratz wrote: Two minor nits: The current beta packages contain a . in the release number. That dot is chopped off along with the anything that follows in some places during install in setup.exe. A better naming scheme would use a letter there, so perhaps 0b8 (I know that this doesn't produce problems since I've been packaging snapshots for local installation that way for a long time). This probably explains the strange results reported in https://cygwin.com/ml/cygwin/2014-11/msg00055.html https://cygwin.com/ml/cygwin/2014-11/msg00180.html in which the base-cygwin package comes very late in the dependency order, and so its postinstall script gets run late. Apparently setup.exe doesn't parse the data for the cygwin package correctly, and its dependencies therefore don't get taken into account in computing the dependency order. You can see this by putting '#define DEBUG 1' in package_db.cc before building setup.exe. The setup log then shows the order in which packages are visited while building the dependency order. base-cygwin ought to be visited immediately after cygwin, but it is only visited much later (if the test version of cygwin is being installed). I had just discovered this and was trying to figure out why, when your mail arrived. Ken
Re: perl-5.18.2-1
On 11/4/2014 11:25 AM, Achim Gratz wrote: Ken Brown writes: I think Reini is talking about the changes introduced by Yaakov and subsequently followed by others (including me). But as long as you're getting the credit anyway, are you willing to adopt perl? We seem to be at an impasse otherwise. The last time Reini talked about the 64bit version of Perl he mentioned he was chasing a serious bug (I don't remember what it was and it may already be moot). I can try to build Perl starting from his 32bit packge, but I would really like to start from where Reini left off for 64bit if that's possible. I probably can't test the result as thouroughly as Reini would have done. I searched the archives, and I found the following two messages from Reini https://sourceware.org/ml/cygwin-apps/2014-03/msg00010.html https://sourceware.org/ml/cygwin/2014-05/msg00511.html in which he mentioned problems with sockets. He didn't specify how serious the problems were. Reini, can you give Achim whatever information he needs in order to continue from where you left off? Ken
Re: cygwin beta packages
On Nov 10 22:24, Achim Gratz wrote: Ken Brown writes: Apparently setup.exe doesn't parse the data for the cygwin package correctly, and its dependencies therefore don't get taken into account in computing the dependency order. To decide that, a formal definition of what is a permissible release number is required and I don't think that's written down someplace. I'm not sure if that's only in genini.pl, but when you manage to increment the releases to have second digits, sometimes these get sorted the wrong way (-1 before -10 IIRC). This only happens in genini AFAIK, not in upset. But the dependency issues might really be related to the test release version numbers. Yaakov is digging into upset ATM. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpd_g334RMyz.pgp Description: PGP signature
Re: cygwin beta packages
On 2014-11-10 12:31, Achim Gratz wrote: The current beta packages contain a . in the release number. That dot is chopped off along with the anything that follows in some places during install in setup.exe. Which places exactly? We could just fix this in setup instead. -- Yaakov
