--- Log for 20.05.116 Server: orwell.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 7 days and 11 hours ago 00.13.59 Quit ZincAlloy (Quit: Leaving.) 00.20.48 *** Saving seen data "./dancer.seen" 00.33.24 Quit ender` (Quit: The propeller is just a big fan in front of the plane used to keep the pilot cool. When it stops, you can actually watch the pilot start sweating.) 00.58.51 Join Strife89 [0] (~quassel@adsl-98-67-60-245.mcn.bellsouth.net) 01.19.31 Quit girafe (Read error: Connection reset by peer) 01.48.48 Quit PurlingNayuki (Quit: PurlingNayuki) 01.50.07 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 02.09.31 Quit TheSeven (Disconnected by services) 02.09.43 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 02.20.49 *** Saving seen data "./dancer.seen" 02.32.56 Quit pamaury (Ping timeout: 276 seconds) 02.44.50 Quit smoke_fumus (Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/) 04.08.53 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 04.12.08 Quit JdGordon (Ping timeout: 260 seconds) 04.13.52 Join JdGordon [0] (~jonno@124-149-159-182.dyn.iinet.net.au) 04.13.52 Quit JdGordon (Changing host) 04.13.52 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 04.15.03 Quit JdGordon_ (Ping timeout: 260 seconds) 04.20.53 *** Saving seen data "./dancer.seen" 04.43.30 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 04.46.03 Quit JdGordon (Ping timeout: 244 seconds) 05.47.35 Quit michaelni (Read error: Connection reset by peer) 06.04.08 Join michaelni [0] (~michael@chello213047041020.graz.surfer.at) 06.20.54 *** Saving seen data "./dancer.seen" 07.07.12 Quit PurlingNayuki (Quit: PurlingNayuki) 08.13.15 Quit krabador (Remote host closed the connection) 08.19.30 Quit nlogex (Ping timeout: 250 seconds) 08.20.58 *** Saving seen data "./dancer.seen" 08.24.22 Join ender` [0] (krneki@foo.eternallybored.org) 08.27.51 Quit Tristitia (Ping timeout: 276 seconds) 08.28.00 Join Mir__ [0] (~Mir@173.51.247.246) 08.28.29 Quit Mir_ (Ping timeout: 276 seconds) 08.31.09 Join Tristitia [0] (~tristitia@static-ip-69-64-50-196.inaddr.ip-pool.com) 09.02.09 Quit naleo (Read error: Connection reset by peer) 09.05.56 Nick Mir__ is now known as Mir (~Mir@173.51.247.246) 10.00.46 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 10.08.59 Quit dfkt (Disconnected by services) 10.09.08 Join dfkt_ [0] (~dfkt@unaffiliated/dfkt) 10.19.58 Join idonob [0] (~Owner@S010610c37b922980.vs.shawcable.net) 10.20.11 Join edhelas [0] (~edhelas@2001:1c02:1903:d800:b822:7aeb:f09e:24be) 10.21.01 *** Saving seen data "./dancer.seen" 10.51.16 Quit idonob (Read error: Connection reset by peer) 10.53.28 Join idonob [0] (~Owner@S010610c37b922980.vs.shawcable.net) 11.01.33 Quit PurlingNayuki (Read error: Connection reset by peer) 11.01.45 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 11.10.34 Quit PurlingNayuki (Remote host closed the connection) 11.13.36 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 11.13.36 Join petur [0] (~petur@rockbox/developer/petur) 11.30.45 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 11.44.35 Join xorly [0] (~xorly@193.85.203.185) 12.07.23 Join ZincAlloy [0] (~Adium@2a02:8108:8bc0:1664:5c1f:de28:bd00:70c) 12.10.31 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 12.21.02 *** Saving seen data "./dancer.seen" 12.27.41 Quit pamaury (Ping timeout: 276 seconds) 12.51.42 Quit xorly (Ping timeout: 244 seconds) 13.26.08 # talk to me right now 13.29.22 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 13.41.09 Join krabador [0] (~krabador@unaffiliated/krabador) 14.02.06 Join pamaury_ [0] (~pamaury@rockbox/developer/pamaury) 14.05.17 Quit pamaury (Ping timeout: 250 seconds) 14.21.04 *** Saving seen data "./dancer.seen" 14.54.45 Join petro_ [0] (b28cf4e3@gateway/web/freenode/ip.178.140.244.227) 15.03.49 Quit edhelas (Ping timeout: 260 seconds) 15.06.51 Join edhelas [0] (~edhelas@2001:1c02:1903:d800:5fe:a9a1:db7f:560) 15.07.35 Quit wodz (Ping timeout: 276 seconds) 15.12.17 Join Boltermor [0] (~Boltermor@subscr-46-148-168-250.dhcp-docsis.net.tomkow.pl) 15.17.37 # ok 15.17.57 # cool 15.18.02 # does that mean i have a friend now? 15.18.59 Join xorly [0] (~xorly@193.85.203.185) 15.27.13 Quit xorly (Ping timeout: 244 seconds) 15.35.42 # [sorry for my English] Hi, somehow I'm listening to music and the music stops. I look at the screen and there is some error. Reboot and... When running at me rockbox hangs on the splash screen, there still is shows bootloader 4.0. to turn off - the button power hold. Firmware sandisk also hangs on the splash screen. I can't connect to a computer. I read http://www.rockbox.org/wiki/SansaAMS - did't help. 15.35.51 # [Sansa Clip Zip, rk 440ff95-140513 or c3c2c91-150425, bootloader 01.01.20] 15.36.27 # petro_: as a first step, I'd recommend checking the filesystem for corruption 15.38.20 # gevaerts, I can't connect to a computer!!! in no way 15.38.38 # hmm 15.38.52 # right, I misread, sorry 15.39.10 # * gevaerts isn't sure 15.39.28 # I think I'll leave this to those who actually know a bit about the AMS sansas 15.41.35 # gevaerts, I have read various topics, but nothing helped 15.42.56 # I do not know what to do next 15.48.32 Join Moarc [0] (~chujko@a105.net128.okay.pl) 16.21.07 *** Saving seen data "./dancer.seen" 16.35.52 Quit krabador (Quit: Take The Time) 16.55.01 Join xorly [0] (~xorly@193.85.203.185) 17.01.02 Quit xorly (Ping timeout: 240 seconds) 17.08.23 Quit petro_ (Ping timeout: 250 seconds) 17.13.00 Join petro_ [0] (b28cf4e3@gateway/web/freenode/ip.178.140.244.227) 17.17.18 Quit petro_ (Client Quit) 17.18.27 Join petro_ [0] (b28cf4e3@gateway/web/freenode/ip.178.140.244.227) 17.19.15 Quit petro_ (Client Quit) 17.28.57 Join desowin [0] (~desowin@37-33-125-44.bb.dnainternet.fi) 17.36.11 Quit krnlyng (Ping timeout: 260 seconds) 17.37.20 Join xorly [0] (~xorly@193.85.203.185) 17.48.49 Join krnlyng [0] (~liar@178.114.108.103.wireless.dyn.drei.com) 17.57.42 Quit xorly (Ping timeout: 252 seconds) 18.03.36 # I am considering getting a used Creative ZEN X-Fi 2, after I literally bricked my h320. How unstable is the port? What I read on doesn’t seem like entire show-stoppers, and I might even get my hands dirty on e.g. the LCD sleep or something. 18.08.57 Quit PurlingNayuki (Quit: PurlingNayuki) 18.15.13 # Horrorcat: first you should know there are basically two versions of it 18.15.52 # it is a NAND based 18.16.00 # (I am looking at an ebay offer right now) 18.16.03 # one with NAND internal storage and one with SD. If you have the NAND one, you won't be able to use the internal storage. If you have the SD one, then you will not either but that support can easily be added (I was just too lazy to do it) 18.16.07 # (checked the model number on the photo of the back) 18.16.18 # what are the barriers for the NAND? 18.17.06 # It's really high, we would have to reimplement the OF FTL, I tried to reverse engineer it, it's huge and complicated so I just gave up because I think it's not worth it as you can simply use an sd card 18.17.16 # what does FTL stand for? 18.17.37 # flash translation layer, it's the way to make a NAND appear as a hard drive basically 18.17.42 # eww 18.18.36 # what are the byte size limits for the SD? 18.18.49 # Otherwise the device works although last time I tried it crashed from time to time for unknown reasons. Also radio is not working (I have some patches for it but there are quirks left) 18.19.27 # there are 64GB sd cards on the market (even 128GB but that's a lot more expensive) 18.19.37 # so microSDHC works? 18.19.45 # yeah it's a microSD port anyway 18.19.49 # pamaury_: I got Sansa Connect bootloader to shift a lot of stack by two bytes (including LR value), unfortunately such resulting LR is outside any memory region and futher shifting does not seem to work due to length being negative 18.20.12 # desowin: is that based on the security report you mentioned ? 18.20.21 # yes, this is exactly that 18.20.31 # also, they do not check PKCS padding in signature check 18.20.48 # so if you could forge last 20 bytes of signature it would be broken 18.20.58 # Horrorcat: so to sum up, I would say the port basically works but because only few people tried it, you will face a few bugs that need to be squash. Also you need to know the touchscreen handling is...suboptimal to say the least 18.21.08 *** Saving seen data "./dancer.seen" 18.21.12 # http://crypto.stackexchange.com/questions/35240/what-is-the-probability-of-attacking-sha1-used-in-rsa-signature-with-small-expon 18.21.22 Quit edhelas (Remote host closed the connection) 18.21.34 Join nlogex [0] (~filip@dhcp-108-168-15-53.cable.user.start.ca) 18.21.47 # this is the case in more cryptographic sense 18.22.29 # pamaury_: what are the differences to the X-Fi3, with respect to the port stability/quirks? 18.22.48 # (except for what is obvious in the progress matrix; and there seems to be SD internal storage on the X-Fi3) 18.23.52 # Horrorcat: last time I tried it was much more stable (very little crashes). The radio is the same so also not working (but again I have some patches). The only thing that I don't like with the Xi3 are the buttons, those are weird touch buttons but if you like those go for it. 18.24.01 # internal storage is supported yes 18.24.08 # and it has a microSD slot 18.24.22 # pamaury_: as long as there’s a hardware lock switch I’m fine with any kind of button I guess. 18.24.42 # yeah it has a hardware lock (I think the Xi 2 does not which is really annoying) 18.24.46 # okay 18.24.49 # that’s a decider for me 18.24.51 # thanks for the tips 18.24.54 # going for the X-Fi 3 then. 18.25.37 # ok, if you encounter any problem just poke me. In particular I think the button code could be better, there is a lot of potential tweaking for those touch buttons 18.26.20 # desowin: how do you manage to shift the stack ? Is there a bug somewhere in the check ? 18.27.24 Nick pamaury_ is now known as pamaury (~pamaury@rockbox/developer/pamaury) 18.27.51 # forging SHA-1 sounds difficult no ? 18.28.41 # pamaury: will do, thanks! 18.29.21 # pamaury_: the length of MPI containing encrypted RSA data in RFC4880 packet is not being checked. It is then shifted byte-by-byte into bignum structure (fixed length; first data buffer, then int32_t len, then int32_t negative_flag). When MPI length is > sizeof(data buffer) it shifts len, effectively multiplying it by 256 and adding the MSB of MPI data 18.30.15 # when next shift occurs, length data is shifted by 1 byte, and also length gets multiplied. After two such shifts, length turns negative and it no longer works 18.32.43 Join rela_ [0] (~x@p5B246FF7.dip0.t-ipconnect.de) 18.33.07 # to complicate it even more it does something like while (buf[len] == 0) { len-- } and stores such len 18.33.38 # so the exact length variable value depens on data that was already on the stack (and well beyond) 18.34.23 Quit rela (Ping timeout: 260 seconds) 18.34.44 # pamaury: around 2^(-80) chances due to this flaw 18.35.09 # but maybe there is some faster method (not yet published by anyone) 18.36.45 # pamaury: it's forging RSA signature. I generate various SHA1 (by modyfing last bytes of image) and then tried to forge signature but it always required RSA modulo reductions as e=41 in this case 18.37.08 # such forgery is a piece of cake with e=3 18.37.19 # but we cannot change it 18.39.10 # so either we find some way to generate SHA1 collisions with known signatures or find a way to create image with SHA1 that can be successfully forged avoiding RSA modulo reduction 18.40.30 # or "just" factor RSA 2048-bit modulus and calculate euler totient ;-) 18.40.55 # then it's easy to sign anything 18.42.29 Join krabador [0] (~krabador@unaffiliated/krabador) 19.21.15 Join naleo [0] (~naleo@unaffiliated/naleo) 19.22.13 # is some expert on the iriver h3xx here? 19.23.27 # I dropped it on the floor two days ago, now it doesn’t manage to boot. the display turns on, but stays white, no bootloader to be seen. 19.24.51 # it's a pretty old device, I am not sure if we have any active dev on them anymore. Is it using a hard drive ? 19.25.24 # it was, until I replaced the harddrive with an SSD because it died the tick of death 19.25.40 # (I actually maintain a patchset to make the SSD work better with rockbox) 19.26.12 Join paulk-collins [0] (~paulk@gagarine.paulk.fr) 19.26.42 # from what I can tell the bootloader isn’t on the SSD though. mainly because I formatted it several times, but also because I can see it print out a few messages before failingw ith result -1 if the SSD is not connected 19.26.50 # the obvious would be that the fall someone damaged the ssd or some connector to it but that's just a wild guess. Have you tried to remove it and put it back ? 19.27.00 # ah 19.27.29 # now it just stays white 19.28.36 # indeed the bootloader is probbaly on the flash 19.29.15 # the keybinding for booting the OF isn’t doing anything either 19.29.41 # plugging it to an external power source while turned off would normally show an OF screen which indicates the charge status (because rockbox could never handle the battery charging in that state) 19.29.49 # now, just the white screen 19.30.13 # I thought it might have wrecked the screen somehow, but it doesn’t show up in lsblk either when connected via USB 19.33.19 # hum, I don't know but it looks bad 19.33.35 # that’s why I am considering a Zen X-Fi ;) 19.34.36 Join lebellium [0] (~chatzilla@89-93-179-187.hfc.dyn.abo.bbox.fr) 19.59.33 Quit rela_ (Quit: Leaving) 19.59.52 Join rela [0] (~x@pdpc/supporter/active/rela) 20.08.40 Quit pamaury (Remote host closed the connection) 20.21.11 *** Saving seen data "./dancer.seen" 20.39.32 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 21.06.58 Join girafe [0] (~girafe@LFbn-1-8020-64.w90-112.abo.wanadoo.fr) 21.26.38 Quit puckipedia (Read error: Connection reset by peer) 21.26.49 Join puckipedia [0] (~puck@irc.puckipedia.com) 21.39.47 Quit Boltermor (Ping timeout: 260 seconds) 21.45.12 Join xorly [0] (~xorly@ip-89-176-117-132.net.upcbroadband.cz) 22.21.14 *** Saving seen data "./dancer.seen" 22.22.08 Quit petur (Quit: Leaving) 22.25.43 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 22.42.31 Quit paulk-collins (Quit: Leaving) 22.54.19 Quit xorly (Ping timeout: 246 seconds) 22.59.49 Quit naleo (Quit: Leaving)