| 00:16.09 | *** join/#qi-hardware mth (kemxgxre@88.159.34.112) |
| 00:36.12 | *** join/#qi-hardware uwe_ (~uwe_@dslb-084-056-052-068.084.056.pools.vodafone-ip.de) |
| 00:55.55 | *** join/#qi-hardware xiangfu (~xiangfu@58.101.248.8) |
| 01:04.14 | *** join/#qi-hardware archang (~archang@111.198.29.54) |
| 01:21.36 | *** join/#qi-hardware fengling (~fengling@2002:6fc6:1d35:0:2c29:5865:f323:c85) |
| 01:32.22 | *** join/#qi-hardware dandon (~dandon@185.16.53.202) |
| 01:44.11 | *** join/#qi-hardware archang (~archang@111.198.29.53) |
| 02:02.37 | *** join/#qi-hardware dandon (~dandon@185.16.53.202) |
| 02:46.16 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 02:56.56 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 03:17.04 | *** join/#qi-hardware dandon (~dandon@185.16.53.202) |
| 03:37.32 | *** join/#qi-hardware archang (~archang@111.198.29.54) |
| 05:00.00 | *** join/#qi-hardware fengling (~fengling@2002:6fc6:1d35:0:1145:ba94:4b3c:7933) |
| 07:01.12 | *** join/#qi-hardware rjeffries (~rjeffries@pool-108-40-199-126.snloca.fios.verizon.net) |
| 08:03.33 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 08:30.58 | *** join/#qi-hardware fengling (~fengling@2002:6fc6:1d35:0:94f:877a:8275:98ad) |
| 09:03.21 | *** join/#qi-hardware sb0 (~lekernel@194-144-39-174.du.xdsl.is) |
| 09:22.02 | *** join/#qi-hardware Ornotermes (~ornoterme@78-69-244-120-no180.tbcn.telia.com) |
| 10:15.47 | *** join/#qi-hardware icanicant (~icanicant@195.88.236.129) |
| 10:42.26 | *** join/#qi-hardware nicksydney (~quassel@18.097.dsl.syd.iprimus.net.au) |
| 11:07.53 | *** join/#qi-hardware Ornotermes (~ornoterme@78-69-244-120-no180.tbcn.telia.com) |
| 11:21.13 | *** join/#qi-hardware Nik05 (~Nik05@unaffiliated/nik05) |
| 11:36.13 | *** join/#qi-hardware sb0 (~lekernel@194-144-39-174.du.xdsl.is) |
| 13:31.04 | *** join/#qi-hardware rjeffries (~rjeffries@pool-108-40-199-126.snloca.fios.verizon.net) |
| 16:30.22 | *** join/#qi-hardware paul_boddie (~paul_bodd@cm-84.215.150.4.getinternet.no) |
| 17:52.00 | *** join/#qi-hardware viric (~viric@unaffiliated/viric) |
| 19:00.19 | *** join/#qi-hardware Ornotermes (~ornoterme@78-69-244-120-no180.tbcn.telia.com) |
| 20:23.38 | paul_boddie | I was asking on the #ci20 channel about jz4740 interrupts yesterday, but does anyone here know much about them? |
| 20:36.35 | paul_boddie | After looking at various manuals, I now have no idea what I should be defining in the CP0 status register. |
| 20:56.01 | *** join/#qi-hardware FDCX_ (~fdcx@ceata/consiliu/FDCX) |
| 21:24.28 | larsc | probably nothing |
| 21:43.40 | DocScrutinizer05 | wpwrak: new anelok stuff in git? :-) I just thought about how to implement some sort of pattern recognition so the gadget could more or less 'guess' the needed password from dunno moving it across the URL or the website or whatever |
| 21:45.42 | DocScrutinizer05 | dunno if a hacked mouse sensor "camera" would do |
| 21:47.27 | DocScrutinizer05 | hmmmm, or screen EMI ;-) |
| 21:48.22 | DocScrutinizer05 | but then, this prolly differs *massively* from one monitor model to next. even when both are LCD same size same technology |
| 21:49.32 | DocScrutinizer05 | if only each browser had an option to show the current URL as QR |
| 21:50.49 | DocScrutinizer05 | maybe your own server could overlay such QR to any referrer site you come with to it |
| 21:53.46 | DocScrutinizer05 | "F6 wpwrak.de <enter>" -> http://somewhere.com/password -> http://wpwrak.de shows QR code for "http://somewhere.com/password" -> (anelok reads QR) -> (hit enter to return to) http://somewhere.com/password |
| 21:54.47 | DocScrutinizer05 | anelok provides password for http://somewhere.com/password |
| 21:56.32 | DocScrutinizer05 | s/wpwrak.de/anel.ok/ |
| 21:57.37 | DocScrutinizer05 | ponders claiming a patent ;-) |
| 22:07.01 | DocScrutinizer05 | wpwrak: with this concept ypou don't even need QR and camera of sorts, a simple animated gif and a photdiode suffices :-D |
| 22:09.04 | DocScrutinizer05 | when you make complete screen blink black&wite, you can sense this from as far as 50cm, or more |
| 22:10.32 | DocScrutinizer05 | morse the fingerprint of md5sum of referrer URL. Should suffice to make anelok identify which of your stored passwords is needed |
| 22:12.27 | DocScrutinizer05 | some 10 to 15 baud are possible for sure by such morse monitor gif |
| 22:14.14 | DocScrutinizer05 | so, 2.5s for 4 chars plus checksum |
| 22:16.44 | DocScrutinizer05 | the anel.ok site could get used by all anelok users, it doesn't hold any special info or complicated infra that needs auth or protection |
| 22:18.40 | DocScrutinizer05 | it simply converts referrer URL to a 4char fingerprint plus checksum (1char) and converts and displays that to a flickering black and white animated gif. On <enter> it returns to referrer site |
| 22:19.49 | DocScrutinizer05 | the privacy issues are moderate |
| 22:25.10 | wpwrak | (new stuff) yeah, trying to finally test whether RF can actually send and receive |
| 22:25.21 | DocScrutinizer05 | ooh, and for auth input, did you consider "tresor code" input method? like: left:$many, right:5, left:7, right:2, left:5, hit-OK |
| 22:26.00 | DocScrutinizer05 | err, you don't have that nice scrollwheel anymore, do you? |
| 22:27.08 | wpwrak | (QR) well, one way is to have some browser plugin that either auto-detects when a password is wanted or that receives some special signals. QR would be fancier, though :) alas, also on the hw side |
| 22:27.27 | DocScrutinizer05 | read on! ;-) |
| 22:28.10 | wpwrak | (tresor code) abandoned that approach in 2013. where have you been ? ;-) |
| 22:28.13 | DocScrutinizer05 | you know you can even abuse normal LED as photdiode? |
| 22:28.50 | DocScrutinizer05 | (where have you been?) on youtube, watching a video of xiangfu |
| 22:29.16 | wpwrak | aaah ! ;-) |
| 22:29.43 | DocScrutinizer05 | it was top hit on google |
| 22:29.53 | wpwrak | link ? |
| 22:30.03 | DocScrutinizer05 | google:anelok |
| 22:30.22 | DocScrutinizer05 | git was 2nd |
| 22:30.24 | wpwrak | aah :) |
| 22:30.33 | wpwrak | wow. that's old :) |
| 22:30.48 | DocScrutinizer05 | yeah, but names like anelok are awesome |
| 22:31.04 | wpwrak | indeed. very google-friendly ;-) |
| 22:31.22 | wpwrak | take this, amazon "echo" :) |
| 22:32.59 | wpwrak | i actually had a photo sensor input in the design for a while. but nobody did anything with the idea, so i kicked it out again. space is critical, no room for might have beens :) |
| 22:37.02 | DocScrutinizer05 | you got a LED, right? |
| 22:37.50 | DocScrutinizer05 | btw a photsensor is fine to save energy by dimming backlight |
| 22:38.00 | DocScrutinizer05 | if you got any ;-) |
| 22:39.01 | DocScrutinizer05 | hey, you have a transparent case (of sorts) - so adding a photo-(LE)D shouldn't be any big issue |
| 22:39.20 | DocScrutinizer05 | those red SMD LEDs are really tiny |
| 22:39.53 | DocScrutinizer05 | and work amazingly well as photodiode |
| 22:41.49 | *** join/#qi-hardware jwhitmore (~jwhitmore@host81-148-227-42.range81-148.btcentralplus.com) |
| 22:42.49 | DocScrutinizer05 | http://wstaw.org/m/2015/06/24/plasma-desktopuk1947.png LED3 iirc https://github.com/r0ket/r0ket/blob/master/hardware/r0ket/r0ket.sch.png |
| 22:45.09 | DocScrutinizer05 | if the case was completely transparent, a simple tiny LED mounted directly on PCB and connected to a A/D GPIO should suffice to receive the morse-gif |
| 22:45.54 | DocScrutinizer05 | if you want to paint it black, you might need a window for the LED |
| 22:50.07 | DocScrutinizer05 | usecase: on PC hit F6, enter "anel.ok", activate anelok receive mode and hold device direction screen, hit PC <enter>, wait until anelok received valid fingerprint code (display flashes with code received), hit PC <enter> again to return to $arbitrary_page, on anelok authenticate for password playback, plug in anelok to PC USB where it registers as kbd and "types" the (username and) password |
| 22:51.49 | DocScrutinizer05 | unplug |
| 22:52.18 | DocScrutinizer05 | sounds good? |
| 22:53.37 | DocScrutinizer05 | lemme rephrase to eliminate some fuzzy wording |
| 22:54.54 | DocScrutinizer05 | usecase: on PC in browser $arbitrary_page hit F6, enter "anel.ok", activate anelok receive mode and hold device direction screen, hit PC <enter>, wait until anelok received valid fingerprint code (anelok display flashes with fingerprint code received), hit PC <enter> again to return to $arbitrary_page, on anelok authenticate for password playback, plug in anelok to PC USB where it enumerates as kbd and "types" the (username and) |
| 22:54.56 | DocScrutinizer05 | password |
| 22:56.01 | DocScrutinizer05 | (wait until...) shouldn't take longer than 3 s usually |
| 23:00.42 | DocScrutinizer05 | for the "morse" encoding you probbaly could re-use ordinary barcode decoder and instead of width of black and white stipes in barcode you use black and bright periods of duration proportional to bar's width |
| 23:01.05 | DocScrutinizer05 | in the animated gif |
| 23:05.20 | *** join/#qi-hardware jwhitmore (~jwhitmore@host81-148-227-42.range81-148.btcentralplus.com) |
| 23:06.22 | DocScrutinizer05 | oooh, and probably ANELOK should rather display both the fingerprint code and the associated name (aka website URL or whatever) on receiving a valid code |
| 23:09.25 | DocScrutinizer05 | err the display is OLED, right? not LCD with backlight |
| 23:10.41 | DocScrutinizer05 | just pondered exploiting the LCD backlight LEDs as photosensor. That won't fly with OLED |
| 23:11.43 | DocScrutinizer05 | could you share a http link to recent anelok schematics please? |
| 23:32.03 | *** join/#qi-hardware wildlander (~wild@unaffiliated/wildlander) |
| 23:53.33 | wpwrak | current design (CR2032): http://downloads.qi-hardware.com/people/werner/anelok/tmp/anelok-20150107.pdf |
| 23:53.47 | wpwrak | note that this will change a fair bit |
| 23:54.04 | wpwrak | lemme make a WIP snapshot ... |
| 23:55.16 | wpwrak | http://downloads.qi-hardware.com/people/werner/anelok/tmp/anelok-20150623-wip.pdf |
| 23:55.51 | wpwrak | key changes: AAA battery, 2nd MCU |
