Arch Linux User Repository

It looks like you forgot to update the package sums in your last version bump.

Also, the .SRCINFO changes seem wrong.

You don't need to edit the .SCRINFO manually. You can use makepkg --printsrcinfo > .SRCINFO after you have updated the PKGBUILD.

I have updated to slimjet 35.0.2.0

1. Go to https://www.slimjet.com/en/dlpage.php
2. Download ~Package(tar.xz)
3. Copy slimjet_amd64.tar.xz to folder what you want and extract archive.
4. Open terminal at folder slimjet
5. Run script with a code ./flashpeak-slimjet
6. Done!

This is fastest browser. (tested on Windows Starter 32-bit, Intel Celeron N3060, 2Gb RAM ) Now install it on Ctlos (ctlos.github.io)

Current version : Slimjet Version 34.0.2.0 (based on Chromium 98.0.4758.9) (Official Build) (64-bit)

After reading these linked articles, I don't see anything to worry about. This information from 2018 is mostly out of date (you can now use the Duck Duck Go search engine) and the Windows user mentioned there probably had some malware for Windows.

Slimjet has many advantages and it would be good if there was a slimjet package maintainer to update it to the latest version 33.

@beserkk: Okay, the second reference you provided is subjective in my opinion. Those users could have picked up the backdoor from the browser they used to download Slimjet or they may have picked it up beforehand and only noticed it after installing Slimjet. Additionally, all of the users were using Windows, not Linux.

Regarding the first reference that you provided, it appears that that user was also using Windows. Maybe it's a Windows thing?

If you have an account for the Slimjet forums, it would be interesting to see what the Slimjet devs response would be to your findings. I just searched the forums and didn't find anything.

@beserkk: Both references provided are from 2018. Is the information still valid?

@dalto: You might consider reaching out to the Slimjet development team about the issues you're encountering. I also appreciate the work you've done; thank you.

Thanks Dalto for your work up til now! Btw I've just found these pages - https://spyware.neocities.org/articles/slimjet.html and https://borncity.com/win/2018/03/26/is-flashpeak-inc-shipping-slimjet-browser-with-a-backdoor/ - and therefore I have decided to remove Slimjet from my machine today.

I have decided to disown this package.

There are too many concerning things with the upstream packaging of this browser which make me uncomfortable with continuing to provide it to others.

Currently, the files which are on the site as 32.0.4.0 are different than the files that were on the site yesterday as 32.0.4.0. As far as I can tell, there was no notification or explanation of this change. This isn't the first or even the second time this has happened.

While it would be easy enough for me to update the package sums and bump the pkgrel, I just can't get comfortable with that. The purpose of the package sums is to ensure the integrity and validity of the source files. When the same source file versions don't have consistent sums, it makes this process pointless.

If anyone wants to pick up this package and needs help understanding how to update it, feel free to reach out to me.

Validating source_x86_64 files with md5sums... slimjet-32.0.4.0_amd64.deb ... FAILED

On page https://www.slimjet.com/en/dlpage.php for the 64-bit .deb MD5:0E1CA905FE0171733FEF4D70FA0F2922)

while PKGVER has md5sums_x86_64=('e636017dee55595abff84ff1d5f118be')