<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Terry Jones - Fluidinfo - Latest Comments</title><link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#forumcomments-1a803aa8" type="application/json"/><link>http://terrycojonesfluidinfo.disqus.com/</link><description></description><atom:link href="http://terrycojonesfluidinfo.disqus.com/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 23 May 2013 10:47:54 -0000</lastBuildDate><item><title>Re: Ten days in hospital</title><link>http://blogs.fluidinfo.com/terry/2013/05/23/ten-days-in-hospital/#comment-905861346</link><description>&lt;p&gt;OMG! Riveting reading. Not unlike NYT Diagnosis column, only those don't worry me. Good time for a virtual hug.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bambi</dc:creator><pubDate>Thu, 23 May 2013 10:47:54 -0000</pubDate></item><item><title>Re: Graceful shutdown of a Twisted service with outstanding deferreds</title><link>http://blogs.fluidinfo.com/terry/2011/06/10/graceful-shutdown-of-a-twisted-service-with-outstanding-deferreds/#comment-863854039</link><description>&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;useful class, thanks.&lt;/p&gt;

&lt;p&gt;I'm using deferreds returned from maybeDeferred() and observed that when calling add(), an error was raised in _fired() because the deferred hadn't been added to the pool yet. I fixed this by swapping the two lines in add() so that if _fired() is called when executing addBoth() it will find and be able to remove the deferred,&lt;/p&gt;

&lt;p&gt;best regards&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John Popplewell</dc:creator><pubDate>Sun, 14 Apr 2013 22:38:32 -0000</pubDate></item><item><title>Re: Alternate browsing realities</title><link>http://blogs.fluidinfo.com/terry/2012/12/04/alternate-browsing-realities/#comment-857107387</link><description>&lt;p&gt;I'd like a tab closer running in the background. If I haven't visited a tab in N minutes, close the tab, or maybe put it in a searchable queue. Give me the option to make certain tabs sticky so they don't autoclose.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Emily Dickinson</dc:creator><pubDate>Tue, 09 Apr 2013 01:26:42 -0000</pubDate></item><item><title>Re: Daylight robbery: Barclays skims €170 off a 5K EUR -&gt; GBP transfer</title><link>http://blogs.fluidinfo.com/terry/2013/02/05/daylight-robbery-barclays-skims-e170-off-a-5k-eur-gbp-transfer/#comment-833471128</link><description>&lt;p&gt;Terry, I have used Transferwise for similar transactions and I love them. 100% transparent and cheap.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Juan Alvarez</dc:creator><pubDate>Mon, 18 Mar 2013 07:25:41 -0000</pubDate></item><item><title>Re: Daylight robbery: Barclays skims €170 off a 5K EUR -&gt; GBP transfer</title><link>http://blogs.fluidinfo.com/terry/2013/02/05/daylight-robbery-barclays-skims-e170-off-a-5k-eur-gbp-transfer/#comment-790473930</link><description>&lt;p&gt;Another advertisement for bitcoin :) &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel</dc:creator><pubDate>Wed, 06 Feb 2013 06:52:47 -0000</pubDate></item><item><title>Re: Daylight robbery: Barclays skims €170 off a 5K EUR -&gt; GBP transfer</title><link>http://blogs.fluidinfo.com/terry/2013/02/05/daylight-robbery-barclays-skims-e170-off-a-5k-eur-gbp-transfer/#comment-789443101</link><description>&lt;p&gt;Yet another daylight robbery with bank as perp, also related to wire transfers and intermediary banks: Bank of America advertises that, for "Platinum Privileges clients," "no fee for incoming wires [which are, for ordinary folk] ($12 domestic/$16 international)." So why is $27 missing from each of my incoming wires?&lt;/p&gt;

&lt;p&gt;"The fee that was assessed and deducted from the incoming wire is a bank-negotiated wire fee from the International bank that’s sending the wire, the intermediary bank and us," BofA responded. &lt;/p&gt;

&lt;p&gt;Uh, isn't that a "fee for incoming wires"? Fraud and false advertising! The mere mention of which got me a six-month reprieve from "intermediary bank wire fees," after which I will check the bank's current claims and quit Bank of America in a blizzard of public comments.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bambi vincent</dc:creator><pubDate>Tue, 05 Feb 2013 12:16:45 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-789182247</link><description>&lt;p&gt;Thanks Richard, I'll go look.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">terrycojones</dc:creator><pubDate>Tue, 05 Feb 2013 08:24:40 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-789181671</link><description>&lt;p&gt;Thanks Brandon, I'll have a look.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">terrycojones</dc:creator><pubDate>Tue, 05 Feb 2013 08:24:08 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-789181376</link><description>&lt;p&gt;Hi David.  That's a good question :-)   I guess the only answer is that you'd need to choose a different service name for that site (because, as you say, changing your master password would be bad).  But that further highlights the need for some kind of management of the service names you've used for sites. I don't like that at all, as I guess is clear - that's why I say this is a good (hard) question.&lt;/p&gt;

&lt;p&gt;Another thing which I find very impractical about this approach is that once you start using a version of this code, it's very hard to upgrade to another version. Again, you'd want metadata stored elsewhere to keep some idea of state.&lt;/p&gt;

&lt;p&gt;Thanks for commenting!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">terrycojones</dc:creator><pubDate>Tue, 05 Feb 2013 08:23:52 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-789167326</link><description>&lt;p&gt;What if your password expires on one site? How do you change one password without changing the "secret" and therefore changing all passwords?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Avraamides</dc:creator><pubDate>Tue, 05 Feb 2013 08:09:46 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-789016913</link><description>&lt;p&gt;Good point. Unfortunately, that means you now have to save the salt between invocations, if I'm not mistaken. You'll also need the same salt value on every computer you want to generate passwords on (instead of only the same algorithm), and when you lose it, you lose access to all your passwords. I wonder if there's a better way?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">trendels</dc:creator><pubDate>Tue, 05 Feb 2013 03:19:21 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-788173248</link><description>&lt;p&gt;Note that &lt;a href="http://passwordmaker.org/" rel="nofollow"&gt;http://passwordmaker.org/&lt;/a&gt; implements this idea with several competing implementations for many different platforms, and with more secure cryptographic options than the simple hash(secret + message) that you do here. PasswordMaker Pro, the Chrome extension, is the particular implementation of its standard that I recommend that people use.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brandon Rhodes</dc:creator><pubDate>Mon, 04 Feb 2013 09:36:29 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-787720907</link><description>&lt;p&gt;Thanks Christian. I'd not heard of key stretching. I'll go look...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">terrycojones</dc:creator><pubDate>Sun, 03 Feb 2013 21:01:23 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-787669915</link><description>&lt;p&gt;Never ever do something like hashfunc(secret + message)! This is insecure and open to several attack vectors like length extension attacks. At least you want to use a &lt;/p&gt;

&lt;p&gt;message authentication code algorithm like HMAC. If you want to reach a minimum level of security, than add a salt from a proper CPRNG and use a key stretching or key derivation algorithm like PBKDF2. The master passwords has most likely not enough entropy. A key stretching algorithms compensates it a bit.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Christian Heimes</dc:creator><pubDate>Sun, 03 Feb 2013 19:56:18 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-787608208</link><description>&lt;p&gt;Yeah, that would be a lot safer.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Moore</dc:creator><pubDate>Sun, 03 Feb 2013 17:24:59 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-787597964</link><description>&lt;p&gt;Hi Richard. Thanks. I originally wrote the code using hmac but then thought I didn't need to worry about length extensions. I guess you're right to be concerned though, and also I later thought that I might want to use service names like "gmail" and "gmail-work" or whatever.  So, I should probably revert :-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">terrycojones</dc:creator><pubDate>Sun, 03 Feb 2013 17:08:43 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-787561448</link><description>&lt;p&gt;Looking at the 'how it works' page for this tool it looks like this is broken too.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Moore</dc:creator><pubDate>Sun, 03 Feb 2013 16:26:39 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-787559366</link><description>&lt;p&gt;You might also consider running `pip install oplop` and/or visiting &lt;a href="https://oplop.appspot.com/" rel="nofollow"&gt;https://oplop.appspot.com/&lt;/a&gt;.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pekka Klärck</dc:creator><pubDate>Sun, 03 Feb 2013 16:22:22 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-787542393</link><description>&lt;p&gt;With your scheme if you ever sign into a local service say for the sake of example 'www' then you will be generating a password that can be used to workout all passwords for sites that start with www. The hash output can be used as input for a length extensions attack (due to the way these hashes work). The risk is mitigated to an extent by the fact that the password is a truncated form of the hash as you only take the first 32 bytes of the digest, but that means that the remaining search space for a brute force attack is tiny. If you want to look into doing something like this, take a look at things like HMAC which are designed to prevent this kind of extension attack.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Moore</dc:creator><pubDate>Sun, 03 Feb 2013 15:49:17 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-787522443</link><description>&lt;p&gt;Hi Petter.  Yes, that's the same thing, pretty much, thanks for the pointer!  I'm going to edit the text above to point people to SGP.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">terrycojones</dc:creator><pubDate>Sun, 03 Feb 2013 15:15:24 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-787508297</link><description>&lt;p&gt;Have you looked into SuperGenPass? [&lt;a href="http://supergenpass.com/" rel="nofollow"&gt;http://supergenpass.com/&lt;/a&gt;]&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Petter Häggholm</dc:creator><pubDate>Sun, 03 Feb 2013 14:49:05 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-787503808</link><description>&lt;p&gt;Terrry. There are some existing services. I use &lt;a href="https://oplop.appspot.com/" rel="nofollow"&gt;https://oplop.appspot.com/&lt;/a&gt; but there's also  &lt;a href="https://www.pwdhash.com/" rel="nofollow"&gt;https://www.pwdhash.com/&lt;/a&gt; which has a nice  Firefox extension.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Wall</dc:creator><pubDate>Sun, 03 Feb 2013 14:42:20 -0000</pubDate></item><item><title>Re: Secure per-site passwords with no encrypted blob</title><link>http://blogs.fluidinfo.com/terry/2013/02/03/secure-per-site-passwords-with-no-encrypted-blob/#comment-787501683</link><description>&lt;p&gt;Great idea!  Have to think about the problem solution. At least i'll do it for myself .&lt;br&gt;Thanks :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tigors</dc:creator><pubDate>Sun, 03 Feb 2013 14:38:20 -0000</pubDate></item><item><title>Re: 10,000 things: Andrew Hensel lives (on Twitter)</title><link>http://blogs.fluidinfo.com/terry/2009/01/05/10000-things-andrew-hensel-lives-on-twitter/#comment-762587605</link><description>&lt;p&gt;Sounds great, I've eaten at G in several cities, but never in London :-)  I'm terry@jon.es  Thanks!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">terrycojones</dc:creator><pubDate>Thu, 10 Jan 2013 11:33:43 -0000</pubDate></item><item><title>Re: 10,000 things: Andrew Hensel lives (on Twitter)</title><link>http://blogs.fluidinfo.com/terry/2009/01/05/10000-things-andrew-hensel-lives-on-twitter/#comment-762583326</link><description>&lt;p&gt;Ha! Just in time for the floods! If you fancy it, come and have lunch chez Google if you're in London. I'm samdutton@gmail.com.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">samdutton</dc:creator><pubDate>Thu, 10 Jan 2013 11:29:57 -0000</pubDate></item></channel></rss>