I'm working on a new release with some fixes
A universal P2P file sharing client for Windows
Brought to you by:
raspopov
Menu
▾
▴
#236 I'm working on a new release with some fixes
new
nobody
None
worksforme
Builds
trivial
2.7.10.2
task
2024-04-22
2022-10-05
No
Hi guys!
I was a Shareaza happy user for decades. Now I try to give something back to the community.
I "adopted" the project and did some changes from the Ivan previous fork.
Project page is: https://github.com/ansani/Shareaza
I released beta builds for 32 and 64 bits (https://github.com/ansani/Shareaza/releases)
Current focus is to speedup build system and the app client using last libraries and compiler releases.
I also mantains a buglist/wishlist.
After the speedup I will start to fix bugs opened in this forum. If you have other bugs with different priorities please add to the GitHub issues page (https://github.com/ansani/Shareaza/issues)
Thank you,
Salvatore
Hi!
I also enabled discussions in the GitHub page: https://github.com/ansani/Shareaza/discussions
Hello Salvatore Ansani,
Good to know! I have also been a happy user since 2005! Is there a possibility this will become the official? Or is this not what you want? Isn't it better to work on the official version instead of forking a fork from a fork?
Last edit: Prennie 2023-08-04
Is this your company? https://www.vice.com/en/article/z3vame/government-spyware-firm-that-put-rogue-apps-on-play-store-goes-bankrupt
What gives you that impression kevogod?
It was my previous company.
Because the ivan386/Shareaza:master is not the right one. The last and most updated one is ivan386/Shareaza:ipv6, which I forked and updated.
Ah, GitHub shoes the "master" branch by default instead of the most recent one.
Reports for your GitHub builds from VirusTotal:
* iShareaza_2.7.10.5_x64_Release_2023-09-23.exe 5/71 (Kaspersky: Trojan-Spy.Win32.Bobik.pis)
* iShareaza_2.7.10.5_Win32_Release_2023-09-23.exe 8/62 (Kaspersky: Trojan-Spy.Win32.Bobik.ptw)
I tried to build your repo and got the next artefact:
* iShareaza_2.7.10.5_x64_Release_2024-02-09.exe 1/70
I suggest you before publishing continuously rebuild the sources and upload them to VirusTotal until it shows no false positives.
BTW it is a questionable idea to add Boost to NuGet packages and put it all 4GB in the source archive. The Zlib package is broken at the moment.
All releases are built using GitHub Agent (https://github.com/ansani/Shareaza/actions) **I don't build anything manually. **
Anyway, I will add the VT step on GitHub.
About the Boost package, I'm using the latest release available on NuGet, so I'm able to build it in every build node of GitHub (or any other CI/CD flow). The source doesn't contains the BOOT package but only a reference for it (if you mean instead the sources zipped in the release section of GitHub then it's normally to find it, as the purpose is to take a snapshot of the evironment that built the final artifact).
What do you mean for Zlib? I'm using a NuGet prebuilt package compatible with all depends.
I opened a specific issue on GitHub: https://github.com/ansani/Shareaza/issues/138.
I have seen a few promising forks (Envy was the last one I used) but watched them all stall.
Lack of users or interest, who knows, but I would suggest that maybe using the shareaza forum for a unified point of release info and feedback may be useful for user awareness.
BTW. Have you found a replacement for the LimeWire schemas ?
Never trust Salvatore Ansani, he is a cracker, he was arrested, he spies and he uses trojans and other malware: https://www-corrieredellacalabria-it.translate.goog/2019/05/22/hacker-di-stato-arrestato-il-calabrese-amministratore-di-e-surv/
As replied in your “technical ticket” #237, sources are freely available on my GitHub account, so anyone (a bit smarter than you, of course) can check for viruses, trojans, and stupidity...
Thank you for your “valuable” contribution...
The cracker <grin></grin>