From the section titled "Motivation": "Copying files through Dropbox is not secure against the Dropbox server [and results in ...]"
Let's say a user encrypts a file outside of Dropbox, using a program of the user's choice, then she transfers the encrypted blob to Dropbox.
Is the author suggesting this is "not secure against the Dropbox server". I am not a Dropbox user. I know it was originally for syncing folders and they orginally used an rsync library and that is about all I know. Pardon the ignorance.
Magic Wormhole by default uses hardcoded host:port for a rendezvous server and a transit server operated by [undisclosed].
"The URL of a public server is baked into the library for use as a default, and will be freely available until volume or abuse makes it infeasible to support."
This Github page is only for the client, not the servers.
In the section titled "Dilation", we are reminded that MW is store and forward by default, not direct connection.
How are messages stored on the default public MW server operated by [undisclosed] "secure against [undisclosed]" in a way that messages stored with Dropbox are not "secure against Dropbox". Maybe the author only uses MW with private MW servers, not public ones run by other people. Then his comment about Dropbox would make sense. However I have to wonder, how many new MW users are running their own servers.
Let's say a user encrypts a file outside of Dropbox, using a program of the user's choice, then she transfers the encrypted blob to Dropbox.
Is the author suggesting this is "not secure against the Dropbox server". I am not a Dropbox user. I know it was originally for syncing folders and they orginally used an rsync library and that is about all I know. Pardon the ignorance.
Magic Wormhole by default uses hardcoded host:port for a rendezvous server and a transit server operated by [undisclosed].
"The URL of a public server is baked into the library for use as a default, and will be freely available until volume or abuse makes it infeasible to support."
This Github page is only for the client, not the servers.
In the section titled "Dilation", we are reminded that MW is store and forward by default, not direct connection.
How are messages stored on the default public MW server operated by [undisclosed] "secure against [undisclosed]" in a way that messages stored with Dropbox are not "secure against Dropbox". Maybe the author only uses MW with private MW servers, not public ones run by other people. Then his comment about Dropbox would make sense. However I have to wonder, how many new MW users are running their own servers.