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

111–120 of 151 posts

Re: Introducing 1Password for Teams

#111

Post by newman314 »

jpgoldberg wrote: post #47
Titanous wrote: post #38

Earlier quoted context omitted.

Is there a reason why you're using RSA over Curve25519? RSA is old and rusty at this point and there's no good reason that I know of to be using it in new cryptosystems. To a much lesser extent I also have the same question about using AES-GCM over Poly1305/ChaCha20.

Yep. There is very definitely a reason. You might not like it, but there is. For the moment we need a client that runs reasonable well in web browsers. As libraries become more available or the nature of our clients change, we can switch. We certainly look forward to having the smaller keys that ECC will give us. We are aware of tweet-nacl, but we are trying to avoid the number of external JS libraries we would need.…

Why not give us the option to choose? That way, shops that have more recent crypto in place can start taking advantage sooner rather than later.

Re: Introducing 1Password for Teams

#112

Post by newman314 »

AGRob wrote: post #97
klinquist wrote: post #80

Really exited for this - was literally just looking to put a vault on a shared drive (yuck)... The pricing does seem a bit high (the same price as google apps!). We're a startup with an engineering team of ~12 and only two or three of us pay for 1password right now. If we had 1password teams, I'm sure I could convince management to include pro versions of 1password for Mac & iPhone with every new employee as part of…

Hi there! Note that pricing is not completely finalized just yet, and we will be offering different pricing tiers. In addition, a subscription to 1Password for Teams would replace the price of the individual apps, not add to it. So, you would be getting free upgrades for the client apps while you are subscribed to 1Password for Teams. I hope that helps! Rob AgileBits

1password has always been pricy and I've been a happy user. But please please entertain having realistic enterprise pricing. If so, I can get an org of several hundred people on it.

Heck, if you offer a good enough deal, I might be able to get a whole bunch of sister companies on it too.

Re: Introducing 1Password for Teams

#113

Post by headwayoldest »

newman314 wrote: post #108
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

While you are taking feedback, I would love for 1password to be able to add ssh keys and other important security bits of info.

I use secure notes for that, personally.

Re: Introducing 1Password for Teams

#114

Post by newman314 »

headwayoldest wrote: post #113
newman314 wrote: post #108

Earlier quoted context omitted.

While you are taking feedback, I would love for 1password to be able to add ssh keys and other important security bits of info.

I use secure notes for that, personally.

I was thinking tighter integration than that.

Imagine if ssh private keys could be stored inside 1Password. It would become a ssh-agent replacement.

No real reason to leave ssh private keys scattered on different user directories anymore.

Re: Introducing 1Password for Teams

#115

Post by jpgoldberg »

baldfat wrote: post #18
jpgoldberg wrote: post #11

Earlier quoted context omitted.

There is absolutely no "lock in" if you try out the beta. Our sign-on process uses a modified form of SRP. (See the draft white paper). It is not a traditional "authentication" process and so can't use other SSOs.

I won't recommend this to my company since I run 4 Linux boxes and there is no native Linux support (Means DEB, RPM and a TAR)

The web app runs in Chrome, Firefox, and Opera. But nothing native yet.

Re: Introducing 1Password for Teams

#116

Post by jpgoldberg »

coldtea wrote: post #39
baldfat wrote: post #18

Earlier quoted context omitted.

I won't recommend this to my company since I run 4 Linux boxes and there is no native Linux support (Means DEB, RPM and a TAR)

Not really a threat -- if they don't provide Linux support, then they know and accept already that people running Linux won't buy or recommend it.

It's more of a threat to us than you describe. If a potential team of N people have k members who need a Linux client, then that might cost us N customers, not just k.

Re: Introducing 1Password for Teams

#117

Post by jpgoldberg »

evincarofautumn wrote: post #59

We really could’ve used this at the startup where I worked a few years ago. We were using the, uh, analog equivalent: a manila folder full of handwritten passwords locked in the founder’s filing cabinet.

I remember doing that in the 90s. There was the "password book" locked away in a location I won't disclose in case they still do it that way.

We all used SSH public keys (this was kind of new back then), so really only needed to consult the password book on certain reboots.

Re: Introducing 1Password for Teams

#118

Post by duncan_bayne »

AGRob wrote: post #74
duncan_bayne wrote: post #53

... provided your team doesn't include anyone using Linux. I asked them whether they had any plans to support Linux recently and got a disappointing "no comment" type of reply. Not impressed.

Sorry you were less than impressed. We can't really discuss future plans, but we are working to mature the 1Password for Teams web client into a fully functional client that can add, edit, and delete items. The whole thing is still in beta right now, but it's definitely on our must-do list. The web client runs in Chrome, Firefox, and Opera, so Linux users will definitely be able to access it there. That's our immedia…

Actually, now that I think about it, why on earth can't you discuss future plans?

Re: Introducing 1Password for Teams

#119

Post by tb303 »

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

Earlier quoted context omitted.

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 gr…

Hi Kyle, thank you for participating in this conversation. I am sure everyone here appreciates it.

It is true that as an android dev one has to implement many things themselves. It's an unpleasant part of developing for Android that Google does very little to address.

The simplest approach you could take would be to copy and implement the design patterns presented in Google's material design guidelines. Yes, it is unfortunate they are guidelines and not SDK. However, there are enough patterns to provide a superior experience to the jumbled mess of an application that it is right now.

https://www.google.com/design/spec/material-design/introduct...

- Use the FAB for "search" since it is the most frequent user action. - Use the navigation drawer https://www.google.com/design/spec/patterns/navigation-drawe...

This is just a 1 minute recommendation and of course open to argument. However, simply redoing the app in a generic style adhering to these guidelines would be a drastic improvement.

Thank you in advance for doing an android app in the first place.

Re: Introducing 1Password for Teams

#120

Post by tb303 »

AGKyle wrote: post #88
untog wrote: post #84

Earlier quoted context omitted.

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

Fingerprint unlock is good. Material is good. But this part is important: Get search into the toolbar, and out of the menu.
Post reply on HN