<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Very gooood. Nicknames and a standard log format. I would like to
put Shannon's pipe on a cronjob that updates the gnuplot in a
directory served via minotaur and published on the wiki.<br>
<br>
<br>
-bfb<br>
<br>
On 06/22/2013 03:27 AM, Shannon Lee wrote:
<blockquote
cite="mid:CAGjxhtmFTWfT3tmW3gVanvGJ0KX-W6+BiWxonrwos6_CnnkbPg@mail.gmail.com"
type="cite">
<div dir="ltr">A flatfile of anonymized log fields would go better
with my cut | sort | uniq -c | gnuplot toolchain.
<div><br>
</div>
<div style="">--S</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, Jun 21, 2013 at 1:19 PM, Leif
Ryge <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:leif@synthesize.us" target="_blank">leif@synthesize.us</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Fri, Jun 21, 2013 at 11:58:01AM -0700,
Shannon Lee wrote:<br>
> No, if you generate a one-time pad of random hashes,
such that...<br>
><br>
> 1 -> foo<br>
> 2 -> bargain basement<br>
> 3 -> mickey mouse<br>
> 4 -> jet plane<br>
><br>
> ...et cetera, then we maintain frequency counts and
timing while<br>
> anonymizing specific codes, and you can't brute force
it because there's no<br>
> hash function. You can even throw away the one-time
pad, because the<br>
> timing data makes it easy to map "mickey mouse" back
to specific entries if<br>
> you have the original dataset.<br>
><br>
> I think Curtis' suggestion actually has the same
properties.<br>
><br>
> --S<br>
<br>
</div>
I was talking about making pseudonymous (not anonymous!)
door code logs<br>
public a few months ago, and started on a project to do so.
I'm sorry I<br>
haven't finished it yet, and glad to see others interested
in doing this<br>
now!<br>
<br>
(Previosuly I heard a few concerns which I think I
addressed, but mostly<br>
a lot of meh.)<br>
<br>
My plan was/is to replace the flat file of codes + comments
(which<br>
frequently have email addresses which obviously should not
be made<br>
public) with a json file that has a 3rd field called
"nickname" that<br>
users can optionally choose, knowing that it will be
publicly logged.<br>
The nicknames can be randomly chosen initially.<br>
<br>
I began implementing that here:<br>
<a moz-do-not-send="true"
href="https://github.com/noisebridge/noisebridge-baron/compare/master...json"
target="_blank">https://github.com/noisebridge/noisebridge-baron/compare/master...json</a><br>
<br>
The converter script works, but has boring names ("pseudonym
751dfb0"),<br>
and I have not tested the changes to baron.py yet.<br>
<br>
I was thinking of trying to generate pronounceable gibberish
names, but<br>
haven't done that part yet.<br>
<br>
I am not going to have time to work on this today or
tomorrow but this<br>
thread inspiried me to push the little bit of code I wrote
so far in<br>
case someone might find it useful.<br>
<br>
If nobody else publishes something by Sunday, I'll probably
work on this<br>
then.<br>
<span class="HOEnZb"><font color="#888888"><br>
~leif<br>
<br>
</font></span></blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
Shannon Lee<br>
(503) 539-3700<br>
<br>
"Any sufficiently analyzed magic is indistinguishable from
science."
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Noisebridge-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a>
<a class="moz-txt-link-freetext" href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a>
</pre>
</blockquote>
<br>
</body>
</html>