<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>bearlog - Latest Comments</title><link>http://bearlog.disqus.com/</link><description></description><atom:link href="https://bearlog.disqus.com/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 05 Aug 2013 16:40:01 -0000</lastBuildDate><item><title>Re: Nginx SSL Config for Forward Secrecy</title><link>http://code-bear.com/bearlog/2013/06/26/nginx-ssl-config-for-forward-secrecy/#comment-989567016</link><description>&lt;p&gt;Thanks for the update - I tweaked the cipher list with your change&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bear</dc:creator><pubDate>Mon, 05 Aug 2013 16:40:01 -0000</pubDate></item><item><title>Re: Nginx SSL Config for Forward Secrecy</title><link>http://code-bear.com/bearlog/2013/06/26/nginx-ssl-config-for-forward-secrecy/#comment-987637336</link><description>&lt;p&gt;I added the cipher :DHE-RSA-AES256-SHA before:RC4-SHA&lt;/p&gt;&lt;p&gt;This seems to satisfy Firefox21, etc.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">devin</dc:creator><pubDate>Sat, 03 Aug 2013 22:02:38 -0000</pubDate></item><item><title>Re: Nginx SSL Config for Forward Secrecy</title><link>http://code-bear.com/bearlog/2013/06/26/nginx-ssl-config-for-forward-secrecy/#comment-987610122</link><description>&lt;p&gt;I had PFS working on qualsys with nginx and your cipher list, but now it is failing Firefox21, etc. Anyone else having trouble?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">devin</dc:creator><pubDate>Sat, 03 Aug 2013 21:17:52 -0000</pubDate></item><item><title>Re: Deploy secrets and git &amp;#8211; why you should not combine them</title><link>http://code-bear.com/bearlog/2013/07/06/deploy-secrets-and-git-why-you-should-not-combine-them/#comment-954110806</link><description>&lt;p&gt;I didn't go into detail because it varies based on how you deploy.  With something like Fabric or Capistrano, I would build a local file from a template with the secret values loaded into memory from the secure store.&lt;/p&gt;&lt;p&gt;Puppet and Chef have similiar methods of retrieving named items or structures from an encrypted store.&lt;/p&gt;&lt;p&gt;Deploying a server is, well at least for how I do it ;), always a provision step followed by a configuration step.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bear</dc:creator><pubDate>Sat, 06 Jul 2013 22:50:52 -0000</pubDate></item><item><title>Re: Deploy secrets and git &amp;#8211; why you should not combine them</title><link>http://code-bear.com/bearlog/2013/07/06/deploy-secrets-and-git-why-you-should-not-combine-them/#comment-954079572</link><description>&lt;p&gt;Right, but I guess my point is, how do you deploy a deploy server? I'm assuming you have a deploy procedure for deploy servers, so how does that configuration information end up on the deploy servers?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paddy Foran</dc:creator><pubDate>Sat, 06 Jul 2013 21:49:26 -0000</pubDate></item><item><title>Re: Deploy secrets and git &amp;#8211; why you should not combine them</title><link>http://code-bear.com/bearlog/2013/07/06/deploy-secrets-and-git-why-you-should-not-combine-them/#comment-954008070</link><description>&lt;p&gt;Most shops have two groups of people who need to know the configuration and/or deploy secrets: Ops and QA/Devs and each need a different set of secrets and they should not have any knowledge about each other. For instance devs need something to use when working locally but that dev server should not be the same as what Ops deploys - hence their secrets are not shared.&lt;/p&gt;&lt;p&gt;In all of the environments i've worked or created, the secrets are always pushed from the deploy servers to the production servers as part of the configuration management step and are stored in their own environment.&lt;/p&gt;&lt;p&gt;I guess some could store the secrets in a private git server that is behind the firewall and all of that, but I would still consider that sub-par because of the social aspect as I mentioned.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bear</dc:creator><pubDate>Sat, 06 Jul 2013 19:13:33 -0000</pubDate></item><item><title>Re: Deploy secrets and git &amp;#8211; why you should not combine them</title><link>http://code-bear.com/bearlog/2013/07/06/deploy-secrets-and-git-why-you-should-not-combine-them/#comment-954001443</link><description>&lt;p&gt;So how would you suggest storing deploy secrets? Git has the nice benefit of being easy to share with the people who need access to these secrets and being easy to backup and make redundant to prevent against lost data. How can I get those properties in a more secure way?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paddy Foran</dc:creator><pubDate>Sat, 06 Jul 2013 19:06:32 -0000</pubDate></item><item><title>Re: Nginx SSL Config for Forward Secrecy</title><link>http://code-bear.com/bearlog/2013/06/26/nginx-ssl-config-for-forward-secrecy/#comment-953901843</link><description>&lt;p&gt;I should be find for IE10 for everything *except* the forward secrecy as IE10 doesn't support the ciphers required IIRC&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bear</dc:creator><pubDate>Sat, 06 Jul 2013 16:19:21 -0000</pubDate></item><item><title>Re: Nginx SSL Config for Forward Secrecy</title><link>http://code-bear.com/bearlog/2013/06/26/nginx-ssl-config-for-forward-secrecy/#comment-953140803</link><description>&lt;p&gt;I just tried this and it works for every browser except IE 10. Any workarounds?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Wayne</dc:creator><pubDate>Fri, 05 Jul 2013 16:00:06 -0000</pubDate></item><item><title>Re: Nginx SSL Config for Forward Secrecy</title><link>http://code-bear.com/bearlog/2013/06/26/nginx-ssl-config-for-forward-secrecy/#comment-948390412</link><description>&lt;p&gt;Yes, that is correct. I'm @Kiran Jonnalagadda   on Twitter and I've used your settings for my servers, which I've blogged about here: &lt;a href="https://blog.hasgeek.com/2013/https-everywhere-at-hasgeek" rel="nofollow noopener" target="_blank" title="https://blog.hasgeek.com/2013/https-everywhere-at-hasgeek"&gt;https://blog.hasgeek.com/20...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kiran Jonnalagadda</dc:creator><pubDate>Mon, 01 Jul 2013 17:37:27 -0000</pubDate></item><item><title>Re: Nginx SSL Config for Forward Secrecy</title><link>http://code-bear.com/bearlog/2013/06/26/nginx-ssl-config-for-forward-secrecy/#comment-948387098</link><description>&lt;p&gt;thanks - I updated the post again, can you double check that I put it in the proper spot?&lt;/p&gt;&lt;p&gt;what is your twitter handle - I want to give you credit for enhancing the config to make it even better!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bear</dc:creator><pubDate>Mon, 01 Jul 2013 17:33:39 -0000</pubDate></item><item><title>Re: Nginx SSL Config for Forward Secrecy</title><link>http://code-bear.com/bearlog/2013/06/26/nginx-ssl-config-for-forward-secrecy/#comment-948372691</link><description>&lt;p&gt;Thanks! I just tried your string with &lt;a href="http://ssllabs.com" rel="nofollow noopener" target="_blank" title="ssllabs.com"&gt;ssllabs.com&lt;/a&gt; and noticed that this does not enable Forward Secrecy with IE9 and IE10. They need an additional cipher: ECDHE-RSA-AES256-SHA (just before the last RC4-SHA). Adding that fixed it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kiran Jonnalagadda</dc:creator><pubDate>Mon, 01 Jul 2013 17:17:13 -0000</pubDate></item><item><title>Re: Nginx SSL Config for Forward Secrecy</title><link>http://code-bear.com/bearlog/2013/06/26/nginx-ssl-config-for-forward-secrecy/#comment-948354812</link><description>&lt;p&gt;ugh! great catch (the $ comes from the terminal I was cutting and pasting from)&lt;/p&gt;&lt;p&gt;I updated the post with the full cipher string.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bear</dc:creator><pubDate>Mon, 01 Jul 2013 17:06:20 -0000</pubDate></item><item><title>Re: Nginx SSL Config for Forward Secrecy</title><link>http://code-bear.com/bearlog/2013/06/26/nginx-ssl-config-for-forward-secrecy/#comment-948114378</link><description>&lt;p&gt;FWIW, I've used your config as a reference for my config. Here's my version: &lt;a href="https://blog.hasgeek.com/2013/https-everywhere-at-hasgeek" rel="nofollow noopener" target="_blank" title="https://blog.hasgeek.com/2013/https-everywhere-at-hasgeek"&gt;https://blog.hasgeek.com/20...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kiran Jonnalagadda</dc:creator><pubDate>Mon, 01 Jul 2013 13:38:20 -0000</pubDate></item><item><title>Re: Nginx SSL Config for Forward Secrecy</title><link>http://code-bear.com/bearlog/2013/06/26/nginx-ssl-config-for-forward-secrecy/#comment-946366190</link><description>&lt;p&gt;Mike, is the last line complete, or does it really end in a '$' and not a ';' ? I tried it on my server and lost TLS 1.0 and 1.1; only 1.2 worked. Then I appended 'RC4:HIGH:!aNULL:!MD5' to the list and support came back along with Forward Secrecy for all browsers except IE9 and IE10.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kiran Jonnalagadda</dc:creator><pubDate>Sat, 29 Jun 2013 12:35:28 -0000</pubDate></item><item><title>Re: XMPP features now missing from GTalk (aka Hangout Chat)</title><link>http://code-bear.com/bearlog/2013/05/19/xmpp-features-now-missing-from-gtalk-aka-hangout-chat/#comment-906530888</link><description>&lt;p&gt;I'm not a technical person, I'm just pissed that my gtalk contacts are not migrated to hangouts, that I'm being forced to use google+&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rae</dc:creator><pubDate>Fri, 24 May 2013 02:32:32 -0000</pubDate></item><item><title>Re: XMPP features now missing from GTalk (aka Hangout Chat)</title><link>http://code-bear.com/bearlog/2013/05/19/xmpp-features-now-missing-from-gtalk-aka-hangout-chat/#comment-903700141</link><description>&lt;p&gt;Google Apps users are in the same position, so Google screwed them over too. They can choose to either upgrade or wait to be forced to upgrade.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dmitri Smirnov</dc:creator><pubDate>Tue, 21 May 2013 04:05:22 -0000</pubDate></item><item><title>Re: I welcome Google as the new Borg</title><link>http://code-bear.com/bearlog/2013/05/19/i-welcome-google-as-the-new-borg/#comment-903095647</link><description>&lt;p&gt;Moving away from XMPP in general and federation in particular is BAD, BAD, BAD! Google you screwed up  big time!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harald Steindl</dc:creator><pubDate>Mon, 20 May 2013 12:55:39 -0000</pubDate></item><item><title>Re: XMPP features now missing from GTalk (aka Hangout Chat)</title><link>http://code-bear.com/bearlog/2013/05/19/xmpp-features-now-missing-from-gtalk-aka-hangout-chat/#comment-902882998</link><description>&lt;p&gt;How do you connect to Hangouts with XMPP? As I replied to the other post. I do not really see any changes. (I do not have Android and never use the chat function on G+.)&lt;br&gt;I don't think they can disable federation for their business users who pay for having a Jabber service with federation.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Julius Schwartzenberg</dc:creator><pubDate>Mon, 20 May 2013 09:25:13 -0000</pubDate></item><item><title>Re: XMPP features now missing from GTalk (aka Hangout Chat)</title><link>http://code-bear.com/bearlog/2013/05/19/xmpp-features-now-missing-from-gtalk-aka-hangout-chat/#comment-902832543</link><description>&lt;p&gt;The bridge is most likely something they threw together to allow old GTalk users to talk to new Hangouts.&lt;/p&gt;&lt;p&gt;After you switch to Hangouts (right now it's voluntary, but I'm pretty sure they will pull the plug soon enough), federation is gone and only remnant of XMPP is that you can still login to Hangouts via XMPP, but all your buddies from outside Google will be gone, statuses won't work and all you will be able to do - is send one2one messages. Pretty much the same you can do with Facebook Messenger. I'd say it's pretty much "we are too lazy to make a decent client for desktop for those, who doesn't use Chrome all the time, so you can have that). Also, my trust in google is gone and I won't be surprized if they drop that as well shortly.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dmitri Smirnov</dc:creator><pubDate>Mon, 20 May 2013 08:10:08 -0000</pubDate></item><item><title>Re: I welcome Google as the new Borg</title><link>http://code-bear.com/bearlog/2013/05/19/i-welcome-google-as-the-new-borg/#comment-902742221</link><description>&lt;p&gt;Your GMail account is still using the GTalk interface - sign into only Google+ or on your Android after updating and you will see that while you receive presence updates you will not be able to send or receive any chat messages.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bear</dc:creator><pubDate>Mon, 20 May 2013 05:12:10 -0000</pubDate></item><item><title>Re: XMPP features now missing from GTalk (aka Hangout Chat)</title><link>http://code-bear.com/bearlog/2013/05/19/xmpp-features-now-missing-from-gtalk-aka-hangout-chat/#comment-902741482</link><description>&lt;p&gt;Thanks for the response and helping me see more of the details from someone else's view.&lt;/p&gt;&lt;p&gt;Now I guess we get to explore what type of "bridge" they are building (and what materials it's made of - to extend their metaphor.)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bear</dc:creator><pubDate>Mon, 20 May 2013 05:10:16 -0000</pubDate></item><item><title>Re: I welcome Google as the new Borg</title><link>http://code-bear.com/bearlog/2013/05/19/i-welcome-google-as-the-new-borg/#comment-902738242</link><description>&lt;p&gt;I don't really get it. I can sign in with Psi to my Gmail account and everything works like it always did, including chat in Gmail, federation, etc. I don't see what they removed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Julius Schwartzenberg</dc:creator><pubDate>Mon, 20 May 2013 05:01:16 -0000</pubDate></item><item><title>Re: XMPP features now missing from GTalk (aka Hangout Chat)</title><link>http://code-bear.com/bearlog/2013/05/19/xmpp-features-now-missing-from-gtalk-aka-hangout-chat/#comment-902731211</link><description>&lt;p&gt;Nope, those correcting you are wrong. All that is said in that thread is that they won't pull the plug on old GTalk right away and will let you connect to new hangouts from your favourite XMPP client for the time being.&lt;br&gt;But federation is gone, since Google now wants to wall off it's users and build a proprietary IM network hoping to outphase all other IMs. It's like a nightmare, at least we still have email that is interoperable (hope they won't try to "fix" that as well).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dmitri Smirnov</dc:creator><pubDate>Mon, 20 May 2013 04:41:03 -0000</pubDate></item><item><title>Re: XMPP features now missing from GTalk (aka Hangout Chat)</title><link>http://code-bear.com/bearlog/2013/05/19/xmpp-features-now-missing-from-gtalk-aka-hangout-chat/#comment-902693713</link><description>&lt;p&gt;"Not federated support, but supports interop with XMPP clients. Meaning you can continue to use XMPP clients to log in to Google Talk and those messages will interop with folks on Hangouts.﻿"&lt;/p&gt;&lt;p&gt;Gracious lord!&lt;/p&gt;&lt;p&gt;P.S. I'm pissed off!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bartosz Małkowski</dc:creator><pubDate>Mon, 20 May 2013 02:56:01 -0000</pubDate></item></channel></rss>