From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) by mail.toke.dk (Postfix) with ESMTPS id 72D2892200C for ; Sun, 30 Jan 2022 17:45:59 +0100 (CET) Authentication-Results: mail.toke.dk; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=SwEyP3Pw Received: by mail-ej1-x636.google.com with SMTP id a8so35424005ejc.8 for ; Sun, 30 Jan 2022 08:45:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Hwc2937p2tALPKWYyGxpVD+ftxLxcsv5KBFYxNS7nXo=; b=SwEyP3PwDhpeLox7IsVG1bLIV2d8tU7UI7P2ZWCElrKWlXVvHM+A+waLW9aQMLQ/Li uUVMmp9m7MFBE2+AvlC9NZUVG8eq96JR6YUdkqxtxRSpkCfbTvLPA9FR4dqFxQeFT1XE M2U/K55rcvOVOvsn6NYwfVzGFD+ryv3eBCH74UvJFygJ9qFsrIupzjM8gm0E75Wub8fg z3qEbGkt+NeLSzoresCR6XdIUe48wXhUvCaZMF/Jrx3J/qLP5arWwK0/KSnrY10lmXh1 9p/UeL2MiGbmcVrYUPiar0dGIycy0MP5tVcvKAtng1Y9CyY3XhWgppAv7o82LwIkRweb jirQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Hwc2937p2tALPKWYyGxpVD+ftxLxcsv5KBFYxNS7nXo=; b=E369OMwF4+Zn+AfLro5cc7McuOtvdyl69J1xiP1NhKkiPf0SdOQq+hRbCEi7kQEP8F iUHNFuOrCdcHAWowpMNPUEZFo2MVjCZGN9km2+02qnkyzVAPLR/zIFcfdSCkJoiIJyYK XCL3KWIKvX4vkhTIRaFkcShiOAHGv6QCqoxUzLA+K+vVjPTspPQXjX/JYBVeMWJNLkjg 3kA6U/mgeKtBAodoA0FZFW4b172qyQVJE4fw4IqHHerQMCDQhnHvI6fzgu8Sww8N+ha6 Jmtg5v3azgHmeZDXjNKT5x+qR4dpVxemmfkwobj9gcyDdJ/2Tl/B2jPL4Exs5/1uUMsm tLVg== X-Gm-Message-State: AOAM531qdFIqAzV6Cm1/LXILCYdQzCK0FJhktXaUDXgVdDNzHZD+XNQG MIf4eymDr/CvjahyD6H7FQKK+bpnaUumOSj2Vzjhuol+1Hs= X-Google-Smtp-Source: ABdhPJwO/81VK5Qa71K/OIqtNn/0qUvGj2UM5ao9EBbJMV7L94U6x/6kvZlUN9Rad8GQUcGY8qr0VuLnNw9E7S1TU7U= X-Received: by 2002:a17:907:7ba3:: with SMTP id ne35mr5554712ejc.128.1643561157540; Sun, 30 Jan 2022 08:45:57 -0800 (PST) MIME-Version: 1.0 References: <877dah9nyn.wl-jch@irif.fr> In-Reply-To: <877dah9nyn.wl-jch@irif.fr> From: Dave Taht Date: Sun, 30 Jan 2022 08:45:46 -0800 Message-ID: To: Juliusz Chroboczek Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Message-ID-Hash: TKO4OUVVRUJIV4BMMQ4RBD5KRXT4BE3C X-Message-ID-Hash: TKO4OUVVRUJIV4BMMQ4RBD5KRXT4BE3C X-MailFrom: dave.taht@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: galene@lists.galene.org X-Mailman-Version: 3.3.5 Precedence: list Subject: [Galene] Re: Peer-to-peer file transfer in Galene List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: https://webtorrent.io/ was pretty neat. thx for going back to having fun with galene, btw. using computers should be fun! On Sun, Jan 30, 2022 at 8:40 AM Juliusz Chroboczek wrote: > > Hi, > > I've been trying to refrain from adding too many features that are not > related to videoconferencing, but given the lack of simple to setup > peer-to-peer file transfer protocols, I've given in on this one. > > In order to send a file to a member of the group, just type "sendfile use= r" > and follow the prompts. > > This is stricly peer-to-peer: the server is only used for signalling > (exchanging IP addresses and cryptographic keys). The protocol is > somewhat convoluted (and undocumented), in order to satisfy the following > properties: > > - rejecting an offered file does not disclose your IP address to the pe= er; > - there is an application handshake at the end, so the sender has > reliable feedback on whether the file went through. > > Of course, sending or accepting a file does disclose your IP address -- > that's the nature of peer-to-peer. > > While the protocol is reasonably secure (SCTP over DTLS), anyone who > controls the server can trivially set up an MITM attack. As always, > please set up your own server if you're exchanging sensitive data. > > It's not very efficient. On the sender side, we manually chop the data > into 16kB chunks (so that we don't run afoul of SCTP limitations). Even > worse, on the receiver side, the whole file is kept in memory (since > Chrome does not support RTCDataChannel.binaryType being set to "blob", an= d > since no browser supports streaming received data to disk). Still, it > should be sufficient for sharing your slides during a presentation or > sending funny pictures during a boring lecture. > > -- Juliusz > _______________________________________________ > Galene mailing list -- galene@lists.galene.org > To unsubscribe send an email to galene-leave@lists.galene.org --=20 I tried to build a better future, a few times: https://wayforward.archive.org/?site=3Dhttps%3A%2F%2Fwww.icei.org Dave T=C3=A4ht CEO, TekLibre, LLC