Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing 1Password for Teams

blog.agilebits.com

Post reply on HN
Print view View original

81–90 of 151 posts

Re: Introducing 1Password for Teams

#81

Post by jpgoldberg »

tptacek wrote: post #62
jpgoldberg wrote: post #51

Earlier quoted context omitted.

I think that there are three issues with WebCrypto that people often conflate. But they need to be looked at separately when judging the security of any particular things. 1. Limited algorithms. This is what has use using GCM instead of a stream cipher for our transport layer. 2. It allows developers to shoot themselves in the foot by not enforcing best practices. 3. It encourages crypto delivered over the web. If (3…

(2) is not true of misuse-resistant crypto primitives and libraries, which is kind of the point of Nacl.

Notice I said "almost every other crypto library". I had NaCl specifically in mind with that qualification.

It's no secret how you feel about crypto delivered over the web and run in the browser, but one of the the factors in our choice involved speed and stability of WebCrypto versus tweet-naclNaCl in JavaScript.

NaCl might be a good choice for our transport layer, but we do a lot of encrypting of keys and not just of non-key data. So we needed to make use of .subtle methods every now and then. So if we needed things that NaCl didn't offer, it was simpler to use a single other API/Library than to mix and match.

I am a huge supporter of efforts like NaCl. I'd obviously prefer to be denied the opportunity to shoot myself (and our customers) in the foot than to use tools that are prone to misuse. It would have also been really cool to show off using NaCl. It is the direction we'd like to see the world move. But we couldn't quite swing it this time around.

Re: Introducing 1Password for Teams

#82

Post by 77ko »

AGKyle wrote: post #79
Shebanator wrote: post #77

Earlier quoted context omitted.

Unfortunately 1pw is absolutely terrible on Android. So I was forced to switch to Lastpass even though 1pw is generally superior because I need something that works on all my devices.

Hi! What were the issues you had with the Android application? Feedback is most certainly welcome here so we can try to focus our attention on the areas that are seeing the most sad faces from our users. Thanks! Kyle AgileBits

I recently switched to Android from ios and literally everything on 1password Android is vastly inferior to the ios version. It's like the ios app is developed by a crack team of experts while the Android app is developed by a part time intern working for free.

Re: Introducing 1Password for Teams

#84

Post by untog »

AGKyle wrote: post #79
Shebanator wrote: post #77

Earlier quoted context omitted.

Unfortunately 1pw is absolutely terrible on Android. So I was forced to switch to Lastpass even though 1pw is generally superior because I need something that works on all my devices.

Hi! What were the issues you had with the Android application? Feedback is most certainly welcome here so we can try to focus our attention on the areas that are seeing the most sad faces from our users. Thanks! Kyle AgileBits

Some of it is UI, which may be a little superficial but it doesn't "feel" like an Android app.

I'd also love to see it do something like Facebook Messenger where it provides a button on top of whatever active app is currently running.

Re: Introducing 1Password for Teams

#85

Post by [deleted] »

signal11 wrote: post #70
AGKyle wrote: post #43

Earlier quoted context omitted.

Really don't want to see anyone get down voted here for having an opinion. Different opinions are what drive conversation, so, I won't ignore your concerns here. I'm not super big on the terminology, but I assume on-prem is on-premise, meaning you'd like to self-host. If I have that correct then unfortunately I can't promise anything here. I will most definitely pass this along to our team though so that they know th…

I realise you may not want to do Active Directory, however it is quite common even in small companies -- and you can even get AD via Azure nowadays. Even lots of Mac-only shops have AD. Maybe v1.x doesn't need AD, however it's something the dev team should definitely consider for later versions. Beyond that, it's really upto AgileBits about how much of the large-corporate market they want to cater for (companies like…

[deleted]

Re: Introducing 1Password for Teams

#86

Post by 77ko »

AGKyle wrote: post #79
Shebanator wrote: post #77

Earlier quoted context omitted.

Unfortunately 1pw is absolutely terrible on Android. So I was forced to switch to Lastpass even though 1pw is generally superior because I need something that works on all my devices.

Hi! What were the issues you had with the Android application? Feedback is most certainly welcome here so we can try to focus our attention on the areas that are seeing the most sad faces from our users. Thanks! Kyle AgileBits

Specific Android issues: - The Android keyboard doesn't autofill fields - in ios I could use the share extension and it would attempt to autofill - the search is hidden behind a menu and isn't present at all in the opening screen - have to go into a category - search is broken - doesn't return a list of searched for items as the ios one does, it displays suggestions instead - if I click on a search result and go back to select a search result I have to search again - design is dated. The ios app looks great the Android one looks really old and dated even compared against last years apps

Overall seems to be a low effort app. Not worth the money I paid for it. Considering switching to an alternative which is more Android friendly despite having laid almost a hundred bucks for ios and Mac apps.

Re: Introducing 1Password for Teams

#87

Post by buro9 »

bdwalter wrote: post #12

Our teams would be all over this if they had real linux support.

Agreed.

Lack of native Linux support (even just for an Ubuntu LTS) is holding back usage in both personal and professional use for me.

That there is an Android app makes the lack of a Linux implementation the more baffling.

Re: Introducing 1Password for Teams

#88

Post by AGKyle »

untog wrote: post #84
AGKyle wrote: post #79

Earlier quoted context omitted.

Hi! What were the issues you had with the Android application? Feedback is most certainly welcome here so we can try to focus our attention on the areas that are seeing the most sad faces from our users. Thanks! Kyle AgileBits

Some of it is UI, which may be a little superficial but it doesn't "feel" like an Android app. I'd also love to see it do something like Facebook Messenger where it provides a button on top of whatever active app is currently running.

I suspect you'll be happy with our future updates. It should feel more like an Android application. There's a small preview you can find here:

https://blog.agilebits.com/2015/05/28/fingerprint-unlock-com...

That's fairly old, from May, but it does give a bit of a tease if you're familiar with Android and the look and feel of things.

Kyle

AgileBits

Re: Introducing 1Password for Teams

#89

Post by neilellis »

AGKyle wrote: post #35
neilellis wrote: post #27

At last full NSA support, I've been waiting for this for ages. Really getting tired of having to open my firewall and give them an SSH login.

You're getting down voted and unfortunately that's a bit disappointing. That said I am happy to discuss with you how Teams is setup so that you can fully understand how it works and realize that we (AgileBits) can provide zero access to your data to anyone, including yourself, without the proper credentials (Email, Account Key, and Master Password). You would probably find our white paper on security and privacy very…

I'm actually a huge 1Password fan - my comment was joking but accurate to the point that no-one can guarantee data security in the current climate. How are we to know that any provider has not been coerced by their nation's security services into weakening their own security protocols - and then been slapped with an order forbidding them to discuss said changes (all within known current NSA practices).

None of this is directed at you guys, as I said, big fan. But at a climate that has left consumers concerned, cynical and distrustful of the safety of any of their data.

Remember my credit cards, alarm codes and personal data is within 1Password - the most precious of my data.

I have read the link and the other I have been sent and I will definitely continue using 1Password and I trust you guys as much as I anyone can be trusted at the moment. Certainly it's more safe than writing it down on a pieces of paper right now :-)

Of course one way to being even more transparent (but not necessarily more secure) is to open source your means of securing, transmitting and remote storage; not the whole product of course.

But with a highly funded secretive agency weakening protocols and strong arming companies, what are we to do :-)

Again great product!

Re: Introducing 1Password for Teams

#90

Post by AGKyle »

77ko wrote: post #82
AGKyle wrote: post #79

Earlier quoted context omitted.

Hi! What were the issues you had with the Android application? Feedback is most certainly welcome here so we can try to focus our attention on the areas that are seeing the most sad faces from our users. Thanks! Kyle AgileBits

I recently switched to Android from ios and literally everything on 1password Android is vastly inferior to the ios version. It's like the ios app is developed by a crack team of experts while the Android app is developed by a part time intern working for free.

With respect to our Android developers they have an uphill climb to catch up to iOS. Our iOS application has been in development for something like 4 years now, and several years before that as a previous incarnation (version 4 was a complete rewrite).

Our iOS application also shares a great deal of underpinnings with Mac. That means when our Mac team implements something super great our iOS team gets some of that grunt work for free. Then it becomes an interface deal in many cases which may not be easy at all but at least some of the work was done.

The Android team, well, they have to implement everything themselves and it's simply going to take time. Combine this with UI changes and stuff that mean we have to rewrite existing things to match up with that and it just becomes very overwhelming sometimes. I work on our iOS application and it's incredible the amount of stuff you can do in a short period of time because groundwork has been laid for years. I don't envy our Android developers because they have none of that to work with. I'm sure it's both overwhelming and exhilarating for them.

I guess that's a long answer but really, it's simply going to take some time for our Android developers to catch up. I know it's tough as a user to see one so far ahead of the other but I hope the above information puts some of it into perspective. They'll get there :)

Thanks!

Kyle

AgileBits

Post reply on HN