| 1 |
thanks. that's it probably (gcc upgrade). |
| 2 |
|
| 3 |
(didn't record the date, deleted it on spot, |
| 4 |
but i did a gcc upgrade recently) |
| 5 |
|
| 6 |
rgrds, |
| 7 |
cm. |
| 8 |
|
| 9 |
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ |
| 10 |
On Sunday, October 20, 2019 9:10 PM, Nikos Chantziaras <realnc@×××××.com> wrote: |
| 11 |
|
| 12 |
> On 20/10/2019 12:57, Caveman Al Toraboran wrote: |
| 13 |
> |
| 14 |
> > today, i did `ls -a ~` and found the file in title. |
| 15 |
> > its content is here: |
| 16 |
> > https://gist.github.com/2eb82a8e31a3e560abd28a2c8102865f |
| 17 |
> > any idea what is this? and how did i get it? |
| 18 |
> > (i started to worry that it might be related to the |
| 19 |
> > sks key server poisoning. specially that i get no |
| 20 |
> > gpg warnings. could it be that i am poisoning real |
| 21 |
> > good?) |
| 22 |
> |
| 23 |
> That's an automated GCC upgrade and full system rebuild script. I'd |
| 24 |
> expect something like this to be used on a managed server by automated |
| 25 |
> tooling. The filename looks like a typical random temporary filename. |
| 26 |
> |
| 27 |
> What's the date of the file? |
Archives