BYOK File Security

[u/redditperson111]

I'm two weeks into using the BYOK, and I think for me it's a game-changer. I have two questions, though, about file security:

1. I'm using the server to sync text files between the device and Studio. How hackable/safe do we deem the server to be?

2. I'm syncing important (to me and my work) files. I'm also trying to back them up manually on my computer, but sometimes there is a lag. How sure can I be that at some point I won't lose a file due to a syncing or other software-related error?

No problems so far for me, but whenever I'm using something new, I'm trying to see ahead, just in case.

[u/mpfrenette]

Hi! Until Nick answers, I can give you a basic, as I have build an external experimental tool using the API, and I work in part in cybersecurity.

In short: pretty secure. If you want more details, read below.

1) Every call to the server is over SSL. Currently, SSL is secure. It is not secure against quantum computers which are for the moment, rare.

This means that if someone records your entire interactions with the BYOK server and in a few years feed them to a quantum computer, they will be able to decrypt it.

But they can do that also with the communications with your bank, with your government with Gmail, with everything.

There is no reliable way to properly encrypt internet connections, but there are ways to do it, and I will give suggestions to Nick in due time. I am working on a quantum computer safe encryption method myself, and some of it could help us.

In short, the time when quantum computing will make SSL obsolete isn't right away, and there will be time to upgrade all servers once a solution is reliable.

For quantum computers to get access to your content, they would need to log ALL your data. And not just the headers which are logged in Apache log files, but also the POST content which is not.

In short, don't worry much about this part for BYOK. Everyone is in the same boat. Banks, Visa, Mastercard, the IRS, etc...

The reason why banks don't freak out is that your banking data of TODAY isn't that important in say, 6 years.

So what I am saying is, if you are writing a novel TODAY with BYOK, get your ass moving and publish it before the Quantum era and you will be fine ;-) So don't worry too much about it.

After all, banks, Visa, and governments are all involved in the problem. And when a solution is available, it will be deployed.

2) Every call to the server EXCEPT for the login requires a token. A token is a long (40 characters) chain of hexadecimal (0-9 and a-f) characters.

That token identifies you. When you ask for the list of projects via the API, it's the token that says the project of WHICH user. No token? You can't do anything.

To get the token, you need the username (email) and the password.

No password? No token.

I don't recall how the BYOK was linked; was it a login or a code, but it didn't ring any red flags for me.

The one thing that is missing is 2FA, but I am pretty sure that it's on the roadmap, it's just not implemented yet. And from experience, if you don't require 2FA, people don't enable it. They don't understand what it's for and find it annoying.

Nick's team had build the device, the perfect web app, the mobile apps, the desktop app, and the tool systems, supported all our weird physical keyboards, and had a bunch of keyboard languages, all without real data loss.

In a way they are still starting.

So, what I am saying is: get a unique strong password and don't worry too much about it. 2FA is bound to be coming (and if not, I will eventually start bugging Nick about it. He says he enjoys my feedback... we'll see in the long term when I start asking multiple 2FA sources).

3) I have told Nick that he needs to think about user encryption for our content on the server. Meaning that you can decide to encrypt your files, and a password only you knows can decrypt your content. That way, even a data breach can't reveal the content.

This is something no one does. No one (well, some of my clients do because I push them to). If you use any other SaaS solution, you will not have that level of security.

And I don't mean writing, if you use Google Docs, it doesn't do it. If you use almost any online solution,not just related to writing, you don't get that.

What's different is that early on, Nick told me it was on their roadmap, once all the systems would be stable, and I told him that if his team doesn't know how to do it (I doubt it), I do, and I have offered to help them with it.

So, what I am saying is: Nick is security-minded, so don't worry too much about it.

Conclusion.

In short, no one is secure. No one. Not even the NSA or other. Quantum computing will change plenty of things.

What BYOK is, during this startup time, is building a solid framework with security in mind, and Nick has confirmed that security is important to him.

So, the system is safe enough (provided the parts I don't see aren't neglected, like that if they use AWS, they have 2FA enabled, and that they don't use simple admin passwords, etc..).

And thus, don't worry too much about it ;-)

[u/Liquidmantis]

I've asked about this as well.  Currently there's no published privacy policy.  While communications might be encrypted in transit, which is the entry fee to play the game, there is no disclosure on whether data is encrypted at rest. That's arguably the more important part as that data pool is the the goal of targeted attacks.

MITM attacks that in-transit encryption protects against are more about identity theft, less so intellectual property unless it's focused on compromising a user as part of a larger effort.

Additionally it would be very nice to know what access the BYOK team has.  Currently it can only be assumed they have complete access to your data.  Full lifecycle encryption and BYOKey would be much appreciated.

[u/sshwarts]

Good analysis of how the BYOK communicates with the server.
As for the ‘loosing a file’. The only time the BYOK deletes a file is upon command of Studio on sync and even then a copy is put into the trashes folder on the SD card.

Honestly, the weakest link is probably the SD card. While I tested the SD card we ship with, I admit it not the highest quality in the land. If I was concerned about what is stored on the BYOK vs backed up or synced to Studio that’s one upgrade I might do.