The time now is Tue 19 Jan 2021, 20:45
All times are UTC - 4 |
Page 125 of 172 [2578 Posts] |
Goto page: Previous 1, 2, 3, ..., 123, 124, 125, 126, 127, ..., 170, 171, 172 Next |
Author |
Message |
belham2
Joined: 15 Aug 2016 Posts: 1743
|
Posted: Mon 07 Oct 2019, 11:12 Post subject:
|
|
scsijon wrote: | wiak wrote: | scsijon wrote: | 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.
|
Back to top
|
|
 |
Sage
Joined: 04 Oct 2005 Posts: 5547 Location: GB
|
Posted: Mon 07 Oct 2019, 14:16 Post subject:
|
|
Quote: | 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.
|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 13129 Location: Stratford, Ontario
|
Posted: Mon 07 Oct 2019, 14:45 Post subject:
|
|
@Sage: Did you read the stuff you found? Is there anything there to support scsijon's report?
If so, provide a specific link.
|
Back to top
|
|
 |
belham2
Joined: 15 Aug 2016 Posts: 1743
|
Posted: Mon 07 Oct 2019, 15:06 Post subject:
|
|
rcrsn51 wrote: | @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
|
Back to top
|
|
 |
Sage
Joined: 04 Oct 2005 Posts: 5547 Location: GB
|
Posted: Mon 07 Oct 2019, 15:35 Post subject:
|
|
Quote: | @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.
|
Back to top
|
|
 |
Rodney Byne
Joined: 31 Jan 2014 Posts: 247
|
Posted: Mon 07 Oct 2019, 16:21 Post subject:
A Chromium page |
|
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.
|
Back to top
|
|
 |
scsijon
Joined: 23 May 2007 Posts: 1600 Location: the australian mallee
|
Posted: Mon 07 Oct 2019, 17:57 Post subject:
|
|
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.
|
Back to top
|
|
 |
jamesbond
Joined: 26 Feb 2007 Posts: 3475 Location: The Blue Marble
|
Posted: Mon 07 Oct 2019, 21:58 Post subject:
|
|
BarryK wrote: | 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
_________________ Fatdog64 forum links: Latest version | Contributed packages | ISO builder
|
Back to top
|
|
 |
tom22251

Joined: 08 Oct 2019 Posts: 15
|
Posted: Tue 08 Oct 2019, 05:01 Post subject:
chromium is working |
|
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!
|
Back to top
|
|
 |
belham2
Joined: 15 Aug 2016 Posts: 1743
|
Posted: Tue 08 Oct 2019, 06:44 Post subject:
|
|
jamesbond wrote: | BarryK wrote: | 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.
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9400 Location: Perth, Western Australia
|
Posted: Tue 08 Oct 2019, 07:25 Post subject:
|
|
In a rush again... just popping into the forum to announce Pyro 1.2.5 released:
http://bkhome.org/news/201910/easyos-pyro-series-version-125-released.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.
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9400 Location: Perth, Western Australia
|
Posted: Tue 08 Oct 2019, 09:29 Post subject:
|
|
Sage wrote: | Quote: | @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/mediacenter/malware/chromium-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.
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 13129 Location: Stratford, Ontario
|
Posted: Tue 08 Oct 2019, 09:35 Post subject:
|
|
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.
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9400 Location: Perth, Western Australia
|
Posted: Tue 08 Oct 2019, 09:44 Post subject:
Re: chromium is working |
|
tom22251 wrote: | 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.
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
Rodney Byne
Joined: 31 Jan 2014 Posts: 247
|
Posted: Tue 08 Oct 2019, 13:43 Post subject:
Pyro 1.2.5, bug with SM in container |
|
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.
|
Back to top
|
|
 |
|
Page 125 of 172 [2578 Posts] |
Goto page: Previous 1, 2, 3, ..., 123, 124, 125, 126, 127, ..., 170, 171, 172 Next |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|