EasyOS version 2.3.2, June 22, 2020

[belham2]

Note for BarryK (and maybe others), in case it helps:

Apparently the latest chromium browser (oct 2019) has had a virus currently called 'parasite' created and released for it.

Can you supply the link about this virus please? I googled but can't find it anywhere.

wiak

Try something other than google then, I got 23 responses from duckduckgo and others from other search engines, since chrome/chromium is a google product .....

Something is weird here.

It doesn't matter what search engine is used (Google, DuckDuckGo, Startpage, Bing, etc) there are no search returns, let alone 23 of them as scsijon notes, for anything related to an Oct 2019 Chromium release and a virus currently called "parasite" afflicting it.

Scsijon, however you know about this 'parasite' thing, can you please provide a direct search result link? So that I can then forward it along to the Chromium-dev team to make them aware of this evidently critical problem?! No one there knows anything about what you're talking about.

Thank you.

[Sage]

there are no search returns

Oh yes there are. You need to polish your searching skills. Got to incorporate " Computer Virus" and " Chromium", inter alia, into your search criteria otherwise you get the more obvious medical answers & co.

[rcrsn51]

@Sage: Did you read the stuff you found? Is there anything there to support scsijon's report?

If so, provide a specific link.

[belham2]

@Sage: Did you read the stuff you found? Is there anything there to support scsijon's report?

If so, provide a specific link.

Rcrsn51,

He can't.

Because there doesn't seem to be any.

No links exist, but the mysterious 'parasite' Chromium killer is real.


Long live Area 51 believers

[Sage]

@Sage: Did you read the stuff you found? Is there anything there to support scsijon's report?

Yes, I did - at least half a dozen. Seasoned db users shouldn't have any trouble locating them. But if you PM me, I'll send a personalised selection/assessment - tomorrow.

[Rodney Byne]

To Barry,
Just wondered if this page on Chromium
is any help for info;

https://chromium.woolyss.com/#linux

Though no mention of EasyOS, but while rummaging around
the web, spotted a few comments on false positives.
Also have you tried running ClamAv?

This is probably a crunch-time immunity test situation
for your brain child.
Regards, R.

[scsijon]

sorry folks,

i'm away from base for a day or two, helping to packup a 1920's artdeco chandelier that had a fall (all 0.9m dia and 3.6m tall of it) so it can go to be repaired. Three months work for the specialists, not me, i'm not that good (or have the equipment to do it all).

It's strange that others can't find this information, maybe there is some sort of blocking going on. I'll provide a few links when i'm back home if still needed. They wern't blaming chromium though, clearly stating that chromium was considered to be a opensource alpha of chrome (googles closed system browser), but it did seem to be a nasty set of reports and only one fix though.

[jamesbond]

NOTICE:
Alfons reported that https sites do not work with Chromium. That is, SSL is broken.

I can't see why, so have removed 2.1.5. I have no idea what has changed since 2.1.3 that could have caused this. Will work on it, hopefully the next release isn't too far away.

Barry, do you have a standalone libnss/libnspr installed, or do you depend on seamonkey to provide these two? If it is the latter, you can probably solve the problem by installing standalone libnss/libnspr. I have read it somewhere (but cannot find the reference again now) that SM 2.49.5 comes with updated libnss/libnspr which probably contains API-breaking changes for anything other than itself. I have just a report from FD64 thread where jake29 reported that he updated SM to 2.49.5 and it breaks his chrome (thanks jake29!); and that installing libnspr/libnss fixes it.

If you already are using standalone libnss/libnspr - well then please ignore this post

[tom22251]

jamesbond,
you are a stable genius!!!

I just removed these links from /usr/lib/
libnspr4.so
libnss3.so
libnssckbi.so
libnssdbm3.chk
libnssdbm3.so
libnssutil3.so

and now chromium is working like new!
Thank you, and thank you Barry!

[belham2]

NOTICE:
Alfons reported that https sites do not work with Chromium. That is, SSL is broken.

I can't see why, so have removed 2.1.5. I have no idea what has changed since 2.1.3 that could have caused this. Will work on it, hopefully the next release isn't too far away.

Barry, do you have a standalone libnss/libnspr installed, or do you depend on seamonkey to provide these two? If it is the latter, you can probably solve the problem by installing standalone libnss/libnspr. I have read it somewhere (but cannot find the reference again now) that SM 2.49.5 comes with updated libnss/libnspr which probably contains API-breaking changes for anything other than itself. I have just a report from FD64 thread where jake29 reported that he updated SM to 2.49.5 and it breaks his chrome (thanks jake29!); and that installing libnspr/libnss fixes it.

If you already are using standalone libnss/libnspr - well then please ignore this post

Thanks, Jamesbond!

Just now fooled around in one of my laptop Fatdog installs, and bingo.

As for the conspiracy-mystery 'parasite' malware theory, especially that the Chromium-Dev Team (or even Google) was suppressing search results about it, as we say to the kids: puff goes the magic dragon.

Barry, hope you put 2.1.5 back up soon. The Chromium thing is easy for us to fix (thanks to JamesB). Want to try some new things with 2.1.5! Sometimes I still can't believe how far EasyOS has come over the past year.

[BarryK]

In a rush again... just popping into the forum to announce Pyro 1.2.5 released:

http://bkhome.org/news/201910/easyos-py ... eased.html

Thanks for the feedback about the Chromium SSL problem. I will get onto that tomorrow and the next Buster should be released soon thereafter.

Note, 1.2.5 has SM 2.49.5, but compiled to use system nss/nspr.

[BarryK]

@Sage: Did you read the stuff you found? Is there anything there to support scsijon's report?

Yes, I did - at least half a dozen. Seasoned db users shouldn't have any trouble locating them. But if you PM me, I'll send a personalised selection/assessment - tomorrow.

What about this:

https://www.pandasecurity.com/mediacent ... ium-virus/

I'm running Chromium right now, in a container, Pyro 1.2.5. What rufwoof suggested, about a fresh start each time -- it might be a good idea to be able to take a snapshot of the container, then specify every time that the chromium container is started in the future, it reverts to that snapshot.
Yeah, might implement that.

[rcrsn51]

That link does NOT describe a virus named "parasite" that attacks your Chromium install.

It describes an altered version of Chromium that is installed in your system by some malware.

[BarryK]

jamesbond,
you are a stable genius!!!

I just removed these links from /usr/lib/
libnspr4.so
libnss3.so
libnssckbi.so
libnssdbm3.chk
libnssdbm3.so
libnssutil3.so

and now chromium is working like new!
Thank you, and thank you Barry!

I am running Easy Pyro 1.2.5 on one of my laptops, it has SM 2.49.5 and Chromium works fine.

Buster 2.1.3 also has SM 2.49.5 I think, but I compiled these to use the system nss and nspr.

For Buster 2.1.5, I used the official SM binary. Reason for this was my compile asked if want to remember password, when one is entered, and I answer "never for this site", but then it asks again next time. Whereas, the official binary works correctly.

Anyway, the official binary is compiled with it's own nss/nspr libs, and the 'pinstall.sh' script in the PET, sees this and creates symlinks to them.

Thanks for the feedback, now I know the cause of the problem and how to fix it.

[Rodney Byne]

To Barry,

Re Pyro 1.2.5
I found a bug with SM in the container.

It spontaneously dies with little excuse.
Add-ons then removed to retry.
When Preferences is clicked it dies instantly.
Regards, R.

[tom22251]

To Barry,

I forgot to tell that the removal of symlinks
was done in Buster 2.1.5 with SM-2.49.5.

Chromium_75.0.3770.142-bk1_amd64.sfs was
used in /opt/

simple script in /usr/bin:
chromium
exec /opt/Chromium/chromium --test-type --no-sandbox "$@"

Testing once again, it turns out only
libnss3.so
libnssutil3.so
are bad.

These four are good,
libnspr4.so
libnssckbi.so
libnssdbm3.chk
libnssdbm3.so
so I've put them back.

Thank you again for your exellent creations.

Tom

[BarryK]

The fix has been applied for Chromium, and Easy Buster 2.1.6 is released, see blog announcement:

http://bkhome.org/news/201910/easyos-bu ... eased.html

Known bugs:

1:
network-manager-applet, the tray applet, crashed a couple of time when I was messing around with wifi. I don't know what specifically caused the crash.

wifi is very odd on my desktop tower PC. I access the Internet via phone hotspot, using a Panda Wireless PAUO5 300mbs usb dongle on the PC, and I found it to be very unreliable when connected via a usb cable. Also unreliable when plugged into a usb3 socket which is a PCIe card. Had to plug it directly into a usb2 socket on the motherboard. All very odd.

Let me know if you experience problems with nm-applet and wifi.

2:
I was testing rolling back to an earlier version on my tower PC. This is a frugal install on a hd partition, and I have been upgrading it for some months.

When I chose to roll back to an earlier version of easy, got an "out of memory" message in the boot partition. This is a 640MB vfat partition, and easy.sfs got truncated to only 119MB, its full size is about 500MB.
It should have fitted, but I think there is a limitation with vfat -- if do a 'cp' to over-write the previous easy.sfs, it seems to temporarily need more space.

So the fix will be to firstly delete the old easy.sfs, then copy the replacement. Will check that out.

[rwishlaw]

An unbelievably flawless, absolutely perfect install of FreeBASIC. All dependencies are in EasyOS Buster 2.1.6 with the corresponding devx installed.

I downloaded

FreeBASIC-1.07.1-ubuntu-18.04-x86_64.tar.xz

from the last entry at the bottom of the page

https://www.freebasic.net/forum/viewtop ... =1&t=27885

unpacked it and ran

./install.sh -i

Done !

[bobtron]

I also seem to have a problem with WIFI reliably connecting...using a "WI-PI" USB dongle plugged into USB 2.0 port on Lenovo ThinkCentre desktop...Chromium reports "ERR_NAME_RESOLUTION_FAILED"
Seamonkey just reports"Page Load Error"...hmm
Also tried to install "cursor_themes-1.1.pet from PPM repo (also local from file) and PPM "Error,...,pet failed to install...as well as various icon themes (same failed to install msg)
anybody else?

[scsijon]

@Sage: Did you read the stuff you found? Is there anything there to support scsijon's report?

Yes, I did - at least half a dozen. Seasoned db users shouldn't have any trouble locating them. But if you PM me, I'll send a personalised selection/assessment - tomorrow.

Sorry for that folks, but helping with some major work took precidence. I only had an hour to read it before I had to go, but the notice about it did come from a reliable group and I thought it did sound like barry's problem and he should be notified.

Sites such as 2-spywhere.com, howtoremove.guide, 2-viruses.com, virusguides.com, supprimer-spyware.com, enigmasoftware.com, commentcamarche.net, novirus.uk with some calling it a virus, some calling it a malware parasite and others just calling it 'parasite' being the name of the virus list it.

I suspect they got in a hot bother due to it's sudden appearance with the new (oct 2019) release, what it does, and how involved it was to remove, however I believe it is a problem that needs dealing with anyway.

?Someone said that the chromium team didn't know about it, I think, could they give me a url or site address for their bug tracking please, I shall check with my source as I did expect them to be notified about it at least.

Doing some reading about chromium this evening (I don't use it as I prefer firefox), I still think they have security problems to sort out.