News for hackers. Stuff that matters.

dustinrcollins

Re:Infosec's Jerk Problem (2013) on Friday April 29, 2016 @03:23PM (#11598116)
Tribalism is really hurting the progress that security folks could be making. Development and operations are starting to collaborate and make huge gains in productivity. Rebranding security as a component of quality can help.

Coming into meetings with other teams with a list of (often unfounded) assumptions does not help anyone. I wrote about this a bit last year: https://blog.conjur.net/devops-and-security-the-five-monkeys

Re:Vault – A tool for managing secrets on Tuesday April 28, 2015 @06:33PM (#9455495)
The policies look like they'd be a bear to manage since they are path- and not role-based. In order to implement least privilege with multiple actors you'd have to be really careful with your paths.

Example: 2 apps. App 1 needs secrets A B and D. App 2 need secrets A B and C.

So we need to set up our paths in a way that App 1 can get A and B and C, but not D. App 2 needs C but not D. Now when you want to modify secret access from your apps you have to rethink how your paths are set up.

When you're instead assigning permissions to roles this is a lot easier. An example: http://blog.conjur.net/what-is-a-devops-secrets-server

Re:Vault – A tool for managing secrets on Tuesday April 28, 2015 @06:21PM (#9455450)
Re:Security of Infrastructure Secrets on Saturday March 28, 2015 @12:28AM (#9280512)
We have been audited by a 3rd party and incorporated all of their suggestions in the latest 4.4 release.

http://blog.conjur.net/conjur-4-4-released

One of their stipulations for the audit was that we don't use it for promotional purposes so I guess a NDA is required to discuss details.

The tech we use for encryption of secrets is definitely open source here: https://github.com/conjurinc/slosilo

Conjur isn't built on in-house cryptographic software - it uses trusted open-source tools - OpenSSL, PAM and so on.

Most of our work is open-source https://github.com/conjurinc https://github.com/conjur-cookbooks

Re:Security of Infrastructure Secrets on Saturday March 28, 2015 @12:18AM (#9280497)
When using Hosted Chef you can't generate a private key and upload it. You create a user, their system generates your key pair and displays the private key one-time-only for you to store somewhere. A user in Chef can only have one keypair at a time. This is just a limitation of their system we have to work with.

It's important to note that the 'user' here in Hosted Chef is not a person, it is an identity in the Chef server that is allowed to upload cookbooks. Its scope is limited to only that.

Rotating the deploy user's key when using HostedChef is a 1 step process, using knife and Conjur together

``` knife user reregister "conjurbot" | conjur variable values add hostedchef/conjurbot/private_key ```

The stdout of `knife user reregister` is the private key so you can update the variable in Conjur without even seeing the value. You could run this in a cron job if you wanted. Your CI system responsible for uploading cookbooks will pull the new private key next time it runs.

Again, not ideal that Hosted Chef only allows you one keypair per user but we can minimize the threat by rotating the key frequently.

Re:KeyBox: A better way to SSH on Monday November 24, 2014 @12:21AM (#8651157)
conjur is a more robust solution for SSH management and avoids the single point of failure. Treating services and code as first-class citizens is not something LDAP excels at.

http://www.conjur.net

Re:Fix OS X Yosemite on Thursday October 23, 2014 @10:37AM (#8498319)
You could also just disable spotlight:

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist

and use [Alfred](http://www.alfredapp.com/).

2.7, mostly. Check here though; if the libs you use are green consider using 3.

https://python3wos.appspot.com/

Vagrant, Chef, AWS CloudFormation. Writing your infrastructure as code saves you a ton of time and headaches.

Older »