5 ms·

Agreed - we offer on-premise (and drive significant revenue from it) at Userify for people who prefer their SSH key management in-house. To be fair to Atlassia

Agreed - we offer on-premise (and drive significant revenue from it) at Userify for people who prefer their SSH key management in-house. To be fair to Atlassian, they basically invented on-prem with SaaS-style pricing (and did us all a great service), and their biggest competitor here (Slack) isn't available on-prem either. Some of these features that you list in Crowd are ironically very similar to missing features in our products, but we're actively working on them -- while not losing focus on being the fastest and easiest key manager to stand up. Running a software business can be challenging -- especially with a myriad of customer environments and feature requests. My feeling is that Atlassian got really big really fast and may have lost sight of their key differentiator -- which, to me, at the time, was pricing and simplicity. It looks like this new product might have brought back their flair on both counts.

solatic 9y ago
For what it's worth, I'd love to try and push Userify at my workplace, but without a trial version to install on-prem, I have nothing to try and persuade people of the value of Userify. Such a trial version should be relatively easy to push out the door - just disable Active Directory / LDAP integration in the trial version. Also, telling on-prem customers to run curl -# https://usrfy.io/upgrade.sh https://usrfy.io/upgrade.sh enterprise |sudo -sE to manually upgrade.... for a security product... completely DOA.
- jamiesonbecker 9y ago
  Awesome, thanks! We definitely offer trial versions to install on-prem with a built-in permanent 10-server license (via a one-liner), and we provide 30 (and sometimes 60) day free trials for however many servers you need for anyone who asks. Converting to production is just a matter of pasting a new key. We could probably make this a bit more clear on our website though (it's buried in our docs section[1]) That is a good point and that doc page is really incomplete. Upgrades are completely automatic in Userify, and without diving too deep into the `curl https | sh` debate :), security conscious are always well advised to do the regular curl > file.sh anyway, even with CA cert checks. Just a good idea. 1. https://userify.com/docs/enterprise/installation/ https://userify.com/docs/enterprise/installation/
  - solatic 9y ago
    > without diving too deep into the `curl https | sh` debate :) So now that it's clear to me that it is possible to do an on-prem install, I decided to look at your curl->sh install script. You guys are basically justifying the fears of our security folks. After grabbing sudo from the user, without asking permission, you pkill NTPD (!), add pool.ntp.org (never mind that we may run our own NTP servers, specifically to remove Internet-based dependencies to lower risk...) and start NTPD again, invoke an install-pip script from a server you don't control (https://bootstrap.pypa.io/get-pip.py https://bootstrap.pypa.io/get-pip.py) without attempting to see if maybe there's a local package of pip available, and then install the EPEL repository. Which is, you know, a perfectly fine repository, but there's a reason why the software included in it isn't included with the official Red Hat repositories and so adding the EPEL repository without asking permission to do so can wreak serious havoc on servers with auto-update scripts installed with the intent to only grab security fixes for installed software. Why can't you guys just open-source some real packaging and respect the sysadmins who you want to be your customers? > Upgrades are completely automatic in Userify Most enterprises who are paying sysadmins to manage their server environments do so at least in part because they want their sysadmins to, you know, manage their server environments, like not upgrading services during peak usage (cough, Windows 10, cough). I'm not saying I won't still try out Userify... I'm saying that, when one of my chief complaints about Atlassian was a lack of packaging support, you came in to champion a product that not only doesn't provide packaging support, but reminds me why packaging support is necessary. If Userify meets our needs, we'll end up needing to package it internally, which means it has to go on our priority list somewhere, and probably not near the top. Sorry if this sounds harsh... just trying to keep it real.
    - jamiesonbecker 9y ago
      Hi Solatic, no problem and appreciate your direct approach :) Pull requests are gratefully accepted: https://github.com/userify/userify-server-tools https://github.com/userify/userify-server-tools Why don't you discuss with one of our solutions architects (or me) by email instead? Most enterprises definitely do package for their unique environment, and we certainly will assist. My email is jamieson.becker@.

solatic 9y ago

For what it's worth, I'd love to try and push Userify at my workplace, but without a trial version to install on-prem, I have nothing to try and persuade people of the value of Userify. Such a trial version should be relatively easy to push out the door - just disable Active Directory / LDAP integration in the trial version. Also, telling on-prem customers to run curl -# https://usrfy.io/upgrade.sh https://usrfy.io/upgrade.sh enterprise |sudo -sE to manually upgrade.... for a security product... completely DOA.

jamiesonbecker 9y ago
Awesome, thanks! We definitely offer trial versions to install on-prem with a built-in permanent 10-server license (via a one-liner), and we provide 30 (and sometimes 60) day free trials for however many servers you need for anyone who asks. Converting to production is just a matter of pasting a new key. We could probably make this a bit more clear on our website though (it's buried in our docs section[1]) That is a good point and that doc page is really incomplete. Upgrades are completely automatic in Userify, and without diving too deep into the `curl https | sh` debate :), security conscious are always well advised to do the regular curl > file.sh anyway, even with CA cert checks. Just a good idea. 1. https://userify.com/docs/enterprise/installation/ https://userify.com/docs/enterprise/installation/
- solatic 9y ago
  > without diving too deep into the `curl https | sh` debate :) So now that it's clear to me that it is possible to do an on-prem install, I decided to look at your curl->sh install script. You guys are basically justifying the fears of our security folks. After grabbing sudo from the user, without asking permission, you pkill NTPD (!), add pool.ntp.org (never mind that we may run our own NTP servers, specifically to remove Internet-based dependencies to lower risk...) and start NTPD again, invoke an install-pip script from a server you don't control (https://bootstrap.pypa.io/get-pip.py https://bootstrap.pypa.io/get-pip.py) without attempting to see if maybe there's a local package of pip available, and then install the EPEL repository. Which is, you know, a perfectly fine repository, but there's a reason why the software included in it isn't included with the official Red Hat repositories and so adding the EPEL repository without asking permission to do so can wreak serious havoc on servers with auto-update scripts installed with the intent to only grab security fixes for installed software. Why can't you guys just open-source some real packaging and respect the sysadmins who you want to be your customers? > Upgrades are completely automatic in Userify Most enterprises who are paying sysadmins to manage their server environments do so at least in part because they want their sysadmins to, you know, manage their server environments, like not upgrading services during peak usage (cough, Windows 10, cough). I'm not saying I won't still try out Userify... I'm saying that, when one of my chief complaints about Atlassian was a lack of packaging support, you came in to champion a product that not only doesn't provide packaging support, but reminds me why packaging support is necessary. If Userify meets our needs, we'll end up needing to package it internally, which means it has to go on our priority list somewhere, and probably not near the top. Sorry if this sounds harsh... just trying to keep it real.
  - jamiesonbecker 9y ago
    Hi Solatic, no problem and appreciate your direct approach :) Pull requests are gratefully accepted: https://github.com/userify/userify-server-tools https://github.com/userify/userify-server-tools Why don't you discuss with one of our solutions architects (or me) by email instead? Most enterprises definitely do package for their unique environment, and we certainly will assist. My email is jamieson.becker@.