LANDrop VS protocol

Would like to give a shout out to LANDrop (not affiliated) if the users are on the local network. I use it. It's very good at saturating the link bandwidth and traffic is guaranteed not to exit the firewall.

https://github.com/LANDrop/LANDrop

Related projects:

- FlyingCarpet: direct transfer over local adhoc WIFI: https://github.com/spieglt/FlyingCarpet

- LANDrop: Drop any files to any devices on your LAN: https://github.com/LANDrop/LANDrop

- In-browser file transfer similar to Airdrop: https://snapdrop.net/

- Magic Wormhole: simple file transfer from computer-to-computer over the net: https://github.com/magic-wormhole/magic-wormhole

- Croc: similar to magic wormhole: https://github.com/schollz/croc

- Wormhole: user-friendly in-browser based e2e encrypted file transfer: https://wormhole.app/

Looks like it is not. Maybe someone wants to maintain a fork.

https://github.com/LANDrop/LANDrop/issues/138

iCloud Drives doesn’t break your file structure, you just drop the whole folders to the iCloud Drives, let it sync, and move them out of iCloud Drive to the internal storage on your iPad. Alternatively there’s plenty of other apps that can do local transfer, like https://landrop.app/. Use another cloud drive service like google drives. Or setup file server on your Mac with SMB and connect it on your iPad: https://support.apple.com/en-us/guide/mac-help/mh17131/10.13/mac/10.13

i just use LANDrop. its free and has no size limitations.

=> https://landrop.app/

I've looked... but its seems there isn't an application based solution without requiring app indicator support which is something that eOS doesn't officially have. If you're comfortable modding eOS to have app indicator support you can then use LanDrop or use KDE Connect with an app indicator. You can also use sharedrop.io or snapdrop.net.

Not the fort-knox implementation it claims on the tin.

'LocalSend uses a secure communication protocol that allows devices to communicate with each other using a REST API. All data is sent securely over HTTPS, and the TLS/SSL certificate is generated on the fly on each device, ensuring maximum security.'

How do they achieve maximum security while generating X.509 certs on device?

Let's look; 'https://github.com/localsend/protocol#2-fingerprint'

'When encryption is on (HTTPS), then the fingerprint is the SHA-256 hash of the certificate'

Confusingly there is a HTTP non encrypted mode, and the docs claim the fingerprint only used to avoid discovery collisions.

Out-of-band [visual comparison / QR code scanning step] sharing of fingerprints COULD be acceptable to prevent 'man in the middle' attacks, however the documentation doesn't seem to indicate that this detail is surfaced or shared with the user.