code logs -> 2017 -> Tue, 14 Feb 2017< code.20170213.log - code.20170215.log >
--- Log opened Tue Feb 14 00:00:24 2017
00:15 LadyOfLight` [catalyst@Nightstar-bt5k4h.81.in-addr.arpa] has quit [[NS] Quit: Leaving]
00:52 * McMartin grumbles at Apple APIs
00:52
<&McMartin>
This function name is 55 characters long
01:32 Derakon[AFK] is now known as Derakon
04:52 himi [sjjf@Nightstar-v37cpe.internode.on.net] has joined #code
04:52 mode/#code [+o himi] by ChanServ
05:11 Derakon is now known as Derakon[AFK]
05:59 LadyOfLight` [catalyst@Nightstar-2e5m7m.dab.02.net] has joined #code
06:03 LadyOfLight [catalyst@Nightstar-ehrgro.dab.02.net] has quit [Ping timeout: 121 seconds]
06:05 LadyOfLight` is now known as LadyOfLight
06:37 AverageJoe [evil1@Nightstar-lc3.hbj.189.210.IP] has joined #code
07:01 Alek [Alek@Nightstar-cltq0r.il.comcast.net] has quit [Ping timeout: 121 seconds]
07:04 Alek [Alek@Nightstar-cltq0r.il.comcast.net] has joined #code
07:04 mode/#code [+o Alek] by ChanServ
07:10 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has quit [Ping timeout: 121 seconds]
07:29 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has joined #code
07:29 mode/#code [+ao ToxicFrog ToxicFrog] by ChanServ
07:59 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has quit [Ping timeout: 121 seconds]
08:01 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has joined #code
08:01 mode/#code [+ao ToxicFrog ToxicFrog] by ChanServ
08:12 sleepyminstrel is now known as celmin|sleep
08:14 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has quit [Ping timeout: 121 seconds]
08:16 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has joined #code
08:16 mode/#code [+ao ToxicFrog ToxicFrog] by ChanServ
08:21 ion [Owner@Nightstar-6grqph.vs.shawcable.net] has quit [Ping timeout: 121 seconds]
08:27 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has quit [Ping timeout: 121 seconds]
08:32 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has joined #code
08:32 mode/#code [+ao ToxicFrog ToxicFrog] by ChanServ
08:34 ion [Owner@Nightstar-6grqph.vs.shawcable.net] has joined #code
08:34 mode/#code [+o ion] by ChanServ
08:44 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has quit [Ping timeout: 121 seconds]
08:45 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has joined #code
08:45 mode/#code [+ao ToxicFrog ToxicFrog] by ChanServ
09:17 LadyOfLight [catalyst@Nightstar-2e5m7m.dab.02.net] has quit [[NS] Quit: Bye]
09:26 Kindamoody is now known as Kindamoody|afk
09:48 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Ping timeout: 121 seconds]
10:55 AverageJoe [evil1@Nightstar-lc3.hbj.189.210.IP] has quit [Ping timeout: 121 seconds]
11:26 LadyOfLight [catalyst@Nightstar-2e5m7m.dab.02.net] has joined #code
12:29 LadyOfLight` [catalyst@Nightstar-1n7o3m.dab.02.net] has joined #code
12:33 LadyOfLight [catalyst@Nightstar-2e5m7m.dab.02.net] has quit [Ping timeout: 121 seconds]
12:56 LadyOfLight` is now known as LadyOfLight
13:21 AverageJoe [evil1@Nightstar-lc3.hbj.189.210.IP] has joined #code
13:56 gnolam_ [lenin@Nightstar-t1tbf0.cust.bahnhof.se] has joined #code
14:00 gnolam [lenin@Nightstar-t1tbf0.cust.bahnhof.se] has quit [Ping timeout: 121 seconds]
14:16 AverageJoe [evil1@Nightstar-lc3.hbj.189.210.IP] has quit [[NS] Quit: Leaving]
15:09 gnolam_ is now known as gnolam
15:09 mode/#code [+o gnolam] by ChanServ
16:05 celmin|sleep is now known as celticminstrel
16:19 * LadyOfLight parses xml in c++, attempts not to fall asleep
16:28 ErikMesoy [Erik@Nightstar-hq72t5.customer.cdi.no] has quit [[NS] Quit: Leaving.]
16:29 ErikMesoy [Erik@Nightstar-hq72t5.customer.cdi.no] has joined #code
16:29 mode/#code [+o ErikMesoy] by ChanServ
16:32
<@abudhabi>
Ugh. Python's mysql stuff is so limited.
16:33
<@abudhabi>
(And broken/unsupported.)
17:13 * abudhabi curses encoding to Hell.
17:39 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
17:39 mode/#code [+qo Vornicus Vornicus] by ChanServ
18:02 LadyOfLight [catalyst@Nightstar-1n7o3m.dab.02.net] has quit [The TLS connection was non-properly terminated.]
18:02 LadyOfLight [catalyst@Nightstar-1n7o3m.dab.02.net] has joined #code
18:06 LadyOfLight [catalyst@Nightstar-1n7o3m.dab.02.net] has quit [The TLS connection was non-properly terminated.]
18:06 LadyOfLight [catalyst@Nightstar-1n7o3m.dab.02.net] has joined #code
18:13 LadyOfLight` [catalyst@Nightstar-bt5k4h.81.in-addr.arpa] has joined #code
18:59 LadyOfLight`` [catalyst@Nightstar-inhlg0.dab.02.net] has joined #code
19:02 LadyOfLight [catalyst@Nightstar-1n7o3m.dab.02.net] has quit [Ping timeout: 121 seconds]
19:06 LadyOfLight` is now known as LadyOfLight
19:33 Kindamoody|afk is now known as Kindamoody
19:56 LadyOfLight`` [catalyst@Nightstar-inhlg0.dab.02.net] has quit [[NS] Quit: Bye]
20:01
<&McMartin>
Well, this is terrifying
20:01
<&McMartin>
http://fermatslibrary.com/s/when-csi-meets-public-wifi-inferring-your-mobile-pho ne-password-via-wifi-signals
20:20
<@celticminstrel>
It sure sounds like it would be terrifying, but it's so dense... I'm not sure I really want to read all of that... >_>
20:26
<&McMartin>
"The motion of your hands entering your Wi-Fi password produces interference that can be used as a side-channel attack on your password"
20:26
<&McMartin>
Is the high bit
20:38
<&ToxicFrog>
Just wifi passwords? From the abstract it sounds like this lets you infer any hand movements as long as the phone is connected to wifi
20:38
<&ToxicFrog>
So the main use is, e.g, figuring out your unlock code or google account password or the like.
20:38
<@celticminstrel>
Is this Android or iPhone or both?
20:41
<@ErikMesoy>
Another step towards the future where everything leaks everything to sufficient signal analysis. >_>
20:42
<@Tamber>
We're already in that future.
20:42
<@Tamber>
But the magic key words there are "sufficient ${X}"
20:44
<@ErikMesoy>
Someday: "the screen brightness modifier to electricity consumption can be used as a side-channel attack to to read text being entered from the power cable".
20:44
<&McMartin>
... pretty sure that power draw was one of the first remote side channels
20:44
<&McMartin>
You'd monitor during a decryption operation and determine their private key
20:45
<@ErikMesoy>
McMartin: Pretty sure power draw is not yet a sufficiently detailed side channel to read individual letters appearing on display, though.
20:46
<&McMartin>
Yeah, no, but, well
20:46
<@Tamber>
It just requires sufficient signal analysis.
20:46
<&McMartin>
Are laptops TEMPEST shielded?
20:51
<@ErikMesoy>
A decade or two later: The power company's logs are sufficiently detailed for frame-by-frame reconstruction of everything you had on your screen.
20:51
<@Tamber>
"...shit."
20:52
<@Tamber>
Cue rotary converter in the power feed~
20:53
<@Tamber>
(Two months later, cue "Logs sufficiently detailed to pick up data, via harmonics coupled through the rotary converter.")
20:54
<@ErikMesoy>
Cue "buy three copies of PC, plug into splitter in same outlet, put hyperactive children on other two".
20:55
<@Namegduf>
This stuff tends to assume everything else is held perfectly still while the analysis is done and the model created. A model could be made in the presence of noise but I imagine it'd only be able to faintly hint at what large spaces are more likely than others in the absence of lots of repeats or lots of modeling of other things.
20:57
<@ErikMesoy>
Repeats like monitor refresh rate? (New hotness: etch-a-sketch style monitors drawing only as needed.)
20:58
<@Namegduf>
There'd be lots of possible monitor states with the same power draw.
20:58
<@Namegduf>
I would absolutely believe they could do that analysis- if they could hold everything else on the screen constant and known while they trained their models.
20:59
<@Namegduf>
In real situations, you'd be maybe able to say some parts of the space of passwords were more likely than others, given distributions over the state of the rest of the screen.
20:59
<@Namegduf>
Would need more data.
21:00
<@Namegduf>
Not that that can't be done, but I think that's the big barrier to making any of these side channel things practical.
21:21 LadyOfLight [catalyst@Nightstar-bt5k4h.81.in-addr.arpa] has quit [[NS] Quit: Leaving]
21:57
<~Vornicus>
Yeah, I know my dad worked in places where for instance there was noise generators so keyboard couldn't be heard.
21:58
<~Vornicus>
I've used software with tempest prevention built in. Dunno how good it is against modern signal analysis but it did things like use #aaa and #555
22:02 LadyOfLight [catalyst@Nightstar-bt5k4h.81.in-addr.arpa] has joined #code
22:28
<&[R]>
What's #aaa and #555?
22:29
<~Vornicus>
colors
22:29
<@ErikMesoy>
Color codes for light grey and dark grey, I believe.
22:29
<~Vornicus>
they have bit patterns 1010 and 0101 respectively
22:42 LadyOfLight [catalyst@Nightstar-bt5k4h.81.in-addr.arpa] has quit [[NS] Quit: Leaving]
22:58
<&McMartin>
CGA colors 7 and 8
23:14
<@gnolam>
I'm mostly wondering what uses 12-bit color.
23:17
<~Vornicus>
gnolam: css allows specification of 12-bit color in situations where that would be sufficient: #abc is #aabbcc is rgb(170, 187, 204)
--- Log closed Wed Feb 15 00:00:25 2017
code logs -> 2017 -> Tue, 14 Feb 2017< code.20170213.log - code.20170215.log >

[ Latest log file ]