1.3 FS no go + ransomware alert ? #236
Labels
No Label
android
arch
backlog
blocked-on-external
bug
bugbash
component/bindings
component/bine
component/connectivity
component/cwtch
component/tapir
component/ui
cwtch-1.14
cwtch-1.15
cwtch-beta-1.1
cwtch-beta-1.10
cwtch-beta-1.11
cwtch-beta-1.12
cwtch-beta-1.13
cwtch-beta-1.2
cwtch-beta-1.3
cwtch-beta-1.4
cwtch-beta-1.5
cwtch-beta-1.5.x
cwtch-beta-1.6
cwtch-beta-1.7
cwtch-beta-1.8
cwtch-beta-1.9
design
duplicate
enhancement
flutter
funding-needed
help wanted
hybrid-groups
in-nightly
in-progress
invalid
ios
linux
mac
need-replication-or-investigation
ops
packaging
post-stable
question
questionable
requires-more-effort-than-we-can-spare
rust
scheduled
stable-blocker
tails
testing-needed
tests
tor
waiting-on-fix-confirmation
waiting-on-new-flutter-feature
whonix
windows
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch-ui#236
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi, follow-up to my other post. Tested out another file sharing session. Sender on MacOS Big Sur. Receiver on Windows 11. Both on cwtch 1.3.File was 67 Mb file.
Starting speeds were hovering around 20 kbps.
At about 80% of transmission, uploading speeds progressively deteriorated, to get to 5 kbps after more than 2 hours of uploading.
Next morning, file still didn't finished uploading and speeds were 1 kbps...
Secundo, looking for some sort of log on MacOS console, only thing i could find was this :
So basically an alert from the OS thinking cwtch is ransomware !
So, for me, file-sharing on cwtch just isn't ready for prime time yet, which basically means reverting to onionshare till it's fixed...
On secundo - that's Patrick Wardle's utility RansomeWhere doing its job and reporting that files are being encrypted. All it means is that Cwtch is doing it's job. It's not a value judgement.
There are definitely performance improvements that we can make (and will make afer a few more fundemental issues have been addressed).
It's an experiment for a reason, though on the speed front Tor itself has been suffering from a period of performance issues over the last couple of weeks - https://metrics.torproject.org/torperf-failures.html?start=2021-08-08&end=2021-11-06&server=onion
This is hilarious. Things might improve with the new storage engine I'm in the middle of implementing which should reduce the number encrypted files that Cwtch creates.
But, Cwtch will create encrypted files - to have that as any kind of IoC strikes me missing the forest for the trees.
thx for the feedback. The thing that bothers me is that the share never finishes,it kinda goes into a braindead state and just keeps going at 1 kbps, so a share of >70 Mb after 10 hours still didn't manage to get completed.
@kalos yea that's right, i have that utility running and actually allowed cwtch for doing its thing.
@sarah no problem having cwtch encrypting files, but for the moment file-sharing just isn't usable enough for me to opt in...