Hi Eriberto, Do you *still* want to mark the Severity: as grave after *Jörg Sommer *has explained in https://github.com/neurobin/ shc/issues/23#issuecomment-299035820 that there is a workaround?
Marking Severity: as grave will make shc 3.8.9b-1 for* autoremoval from testing on **2017-05-24* Would it a better option to mark it not so sever, so that for those people depending on shc, can still use it, using the workaround? FTR, the workaround is, setarch `uname -m` -R $SHELL. That will spawn a shell with ASLR disabled, and any command you run from that shell will also have ASLR disabled. On Sun, Apr 30, 2017 at 3:48 PM, Tong Sun <suntong...@users.sourceforge.net> wrote: > > On Sat, Apr 29, 2017 at 7:45 PM, Eriberto <eribe...@eriberto.pro.br> > wrote: > >> I did some tests and I have news. I downloaded the versions 3.8.6 and >> 3.8.7 from upstream homepage and I did a 'make' inside a Sid jail. >> After this, I compiled a shell script. The script compiled by 3.8.6 >> version worked fine, but the script from 3.8.7 (and newer) fails >> (infinite loop). >> > > Oh, that's indeed a good news. > > There are two major fixes after versions 3.8.6 > > - Bug on 64bit systems with expiration dates. > - Fixing a long standing bug making the source not hidden. > > Both are big issues, and I vaguely remember that expiration date was an > issue biting me. I think we need to do more testing before making any > decision. > > Also, CCing *Giacomo Picconi* to see if he has any ideas about the bug > and fix. > > Thanks > >
