41–50 of 75 posts
Earlier quoted context omitted.
patrick[at]priceintelligently[dot]com Always happy to help where I can when it comes to pricing. PC
The man, the myth, the legend. He’s going to roast your pricing but I’m sure you’ll grow a ton from it.
You need Patrick from PriceIntelligently to analyze your pricing page. Maybe tweet at him or Hiten Shah and see if either will help. I'd recon they would suggest you keep 2 tiers and add a call us tier for b2b enterprise. I see where decently sized companies would pay a lot more than $10/month/user to ensure their sensitive docs can't be stolen. I certainly am no expert but if the product works as it seems this shoul…
I like how they don't flaunt crypto terms all over the place. Calling encrypted content "gibberish" is fun. And I think it's a genius use-case for Service Workers. From their security page[0]: "we're using a relatively new web technology (Service Workers) to install some code which can't be changed without setting off a warning to you. That code then keeps taps[sic] on all other code, and checks that it matches the p…
To be precise: If it works as described, it makes it (a little? substantially? orders of magnitude?) more difficult for third parties to modify the code.
"Certain" is not a word used in security, IME.
few questions: - here [0] "All documents are encrypted before they leave your computer" how then one can collaborate as in gdocs (from the pic it seems like that) - what key do you use for encrypting the docs? is it the user password? if so it can't be recoverd (as dashlane for example [1]) is this the approach? PS: the login seems broken https://www.airborn.io/app [0] https://www.airborn.io/docs/security [1] https:/…
- When you create a collaboration link, it contains an encryption key. (You can additionally also set a password.) All messages sent to the server by collaborators are then encrypted with those. The collaboration algorithm is currently quite simple, and paragraphs are locked when editing them. In the future we'd like to use a P2P algorithm, e.g. using Y.js. [1] - When you sign up, the page downloads a file on your PC…
Having the password recovery keys, can you decrypt user passwords? Does that matter in this scenario?
Earlier quoted context omitted.
- When you create a collaboration link, it contains an encryption key. (You can additionally also set a password.) All messages sent to the server by collaborators are then encrypted with those. The collaboration algorithm is currently quite simple, and paragraphs are locked when editing them. In the future we'd like to use a P2P algorithm, e.g. using Y.js. [1] - When you sign up, the page downloads a file on your PC…
> When you lose your password, we send you your password recovery key and you can decrypt your password with it. Having the password recovery keys, can you decrypt user passwords? Does that matter in this scenario?
On the document editor, is it just me or are you missing a blockquote control? Also, is there a reason you're using inline styles to do italics and bold instead of the specific tags for those things? (Deleted question you answered downthread.)
You can create a blockquote element by pressing Tab, although it won't have any special styling. If you want, you could add some CSS in Raw view. I'll look into making a control for this specifically, although IIRC browser support for blockquotes in contenteditable is a bit inconsistent. Regarding inline styles, I don't remember why, sorry. It might again have been to fix some inconsistency between browsers.
I like how they don't flaunt crypto terms all over the place. Calling encrypted content "gibberish" is fun. And I think it's a genius use-case for Service Workers. From their security page[0]: "we're using a relatively new web technology (Service Workers) to install some code which can't be changed without setting off a warning to you. That code then keeps taps[sic] on all other code, and checks that it matches the p…
> you can be certain To be precise: If it works as described, it makes it (a little? substantially? orders of magnitude?) more difficult for third parties to modify the code. "Certain" is not a word used in security, IME.
Earlier quoted context omitted.
> you can be certain To be precise: If it works as described, it makes it (a little? substantially? orders of magnitude?) more difficult for third parties to modify the code. "Certain" is not a word used in security, IME.
Very true. You probably still need to trust that the developers' Github accounts aren't compromised. I was looking at their repo[0] for this Service Worker verification, and their "So what's the problem this solves?" section confuses me, as it doesn't explain the how. :/ [0] https://github.com/airbornio/signed-web-apps
That section attempts to explain how web apps work today, if you don't use that library. Reading the entire thing back, I agree that the how is never explained very well, although https://www.airborn.io/docs/security does explain it.
Nice idea, but the design of this leaves a lot to be desired.