IRC log for #maemo on 20170912

00:46.45*** join/#maemo Kabouik_ (~kabouik@2a01:e35:2fd3:5030:e142:c406:c878:1d89)
01:15.05*** join/#maemo yosafbridge (~yosafbrid@68.ip-149-56-14.net)
01:22.16*** join/#maemo frals (~frals@c83-251-145-18.bredband.comhem.se)
01:22.16*** join/#maemo frals (~frals@Maemo/community/contributor/frals)
01:56.54*** join/#maemo DocScrutinizer06 (~saturn@openmoko/engineers/joerg)
01:59.01*** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
02:24.08*** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr)
03:16.41*** join/#maemo mva_ (znc@gentoo/contributor/mva)
04:02.32*** join/#maemo LauRoman (~LauRoman@5-14-5-68.residential.rdsnet.ro)
04:51.11*** join/#maemo Kilroo (~Kilroo@cpe-71-71-97-50.triad.res.rr.com)
05:46.11*** join/#maemo xy2_ (~xy2_@94.239.177.175)
05:51.12*** join/#maemo Milhouse (~Milhouse@kodi/staff/milhouse)
05:53.41*** join/#maemo spiiroin (~spiiroin@2001:998:2a:dead:28be:1d23:de4:62ff)
06:18.36*** join/#maemo xorly (~xorly@ip-86-49-24-93.net.upcbroadband.cz)
06:26.15*** join/#maemo Milhouse (~Milhouse@kodi/staff/milhouse)
06:35.32*** join/#maemo dmth|intevation (~dmth|inte@2001:470:747a:2a:6af7:28ff:fe64:1ded)
06:40.47*** join/#maemo rhn_mk1 (~rhn@pD4B9E37F.dip0.t-ipconnect.de)
06:40.48*** join/#maemo rhn_mk1 (~rhn@unaffiliated/rhn)
06:45.10*** join/#maemo FalconSpy_ (falconspy@ip72-208-197-193.ph.ph.cox.net)
06:56.29*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
07:07.31*** join/#maemo HTTP_____GK1wmSU (~DEEP-BOOK@103.27.125.238)
07:10.13*** part/#maemo HTTP_____GK1wmSU (~DEEP-BOOK@103.27.125.238)
07:24.04*** join/#maemo HTTP_____GK1wmSU (~DEEP-BOOK@103.27.125.238)
07:26.15*** part/#maemo HTTP_____GK1wmSU (~DEEP-BOOK@103.27.125.238)
07:32.27*** join/#maemo freemangordon_ (~ivo@195.242.126.12)
07:38.01*** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it)
07:51.25*** join/#maemo FalconSpy (falconspy@unaffiliated/falconspy)
08:34.41*** join/#maemo eMHa (~mh@2a02:788:113:142:d6be:d9ff:fe2b:f21b)
08:40.40*** join/#maemo wnd (~wnd@katei.fi)
08:43.20freemangordon_merlin1991: ping
08:51.47*** join/#maemo xray256 (~xray256@host86-162-113-135.range86-162.btcentralplus.com)
08:56.04DocScrutinizer05moin
09:28.46*** join/#maemo Kabouik_ (~kabouik@lns-bzn-37-82-253-53-3.adsl.proxad.net)
10:15.23*** join/#maemo spiiroin (~spiiroin@37-33-95-250.bb.dnainternet.fi)
10:54.15*** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au)
10:55.11jonwilhi
11:05.30*** join/#maemo cyteen (~cyteen@cyteen42.plus.com)
11:13.45*** join/#maemo err0r3o3 (~err0r3o3@88-117-124-16.adsl.highway.telekom.at)
11:16.48*** join/#maemo freemangordon_ (~ivo@195.128.225.2)
11:19.58*** join/#maemo wnd (~wnd@katei.fi)
11:32.08*** join/#maemo ketar (~herekun@164.132.132.199)
11:33.38DocScrutinizer05freemangordon: ping
11:36.23DocScrutinizer05>>To use AES on N900 you need to flash special boot loader.<<
11:44.40freemangordon_DocScrutinizer05: pong
11:44.54DocScrutinizer05you know this crypto NOLO?
11:45.13*** join/#maemo err0r3o3 (~err0r3o3@88-117-124-16.adsl.highway.telekom.at)
11:45.17freemangordon_yes
11:45.21DocScrutinizer05good :-)
11:45.39DocScrutinizer05should CSSU... ?
11:45.41freemangordon_it enables AES IP in the L2 firewall, iirc
11:45.46DocScrutinizer05yep
11:46.09DocScrutinizer05http://susepaste.org/25062175
11:46.32freemangordon_re cssu - there is not much use of that AES, it is slower than doing it on MPU
11:47.10DocScrutinizer05duh!
11:47.51freemangordon_it makes sense if we do some mobile payments or such, which we don't :)
11:48.15DocScrutinizer05but it's a coproc, right? so it could run concurrently to "normal" tasks, e.g. for disk encryption
11:48.44freemangordon_iirc somebody tried it, and there is no gain, on the contrary
11:48.52DocScrutinizer05dang
11:48.52freemangordon_yes, it is coproc
11:49.40freemangordon_but you do supervisor call, iirc, with all the nasty contexts switches etc
11:49.50DocScrutinizer05I see
11:50.16freemangordon_there should be a thread on TMO with the results
11:50.36DocScrutinizer05does the NOLO itself reveal something, at least. EG when comparing it to default xloader/nolo?
11:52.14DocScrutinizer05I mean, maybe we got a second signature, cracking would be more than twice as fast with two than with just one signature - in theory ;-D
11:52.57DocScrutinizer05and maybe this is BS I pulled right outa my read
11:53.07DocScrutinizer05rear even
11:53.12freemangordon_you mean 2^127 years instead of 2^128? :p
11:53.24DocScrutinizer05yes, this sort of thing ;-P
11:54.40DocScrutinizer05I'm still totally unclear about signatires of xloader in GP SoC
11:55.17DocScrutinizer05does GP also have a L2 FW?
11:56.10DocScrutinizer05I'd assume they build the very same chip, incl all IP, and just change the xloader and signature
11:56.23DocScrutinizer05resp L2 config
11:56.36DocScrutinizer05a mere guess
11:57.13freemangordon_iirc, yes, there is L2 firewall on gp devices
11:58.20DocScrutinizer05and the L2 config is completely done in xloader, or would GP and HS have different ROMBL (apart from obviously different signatures/keys)?
11:58.41*** join/#maemo xray256 (~xray256@host86-142-134-157.range86-142.btcentralplus.com)
11:59.43DocScrutinizer05iirc the omapedia about bootloader said you need to sign xloader for GP too (they don't even cover HS devices there)
12:00.12DocScrutinizer05~listvalues omapedia
12:01.31freemangordon_sure GP xloader needs to be signed
12:01.43DocScrutinizer05~listvalues omappedia
12:01.53freemangordon_but it is not a problem as the keys are known
12:02.39freemangordon_though I don;t remember signing xloader for BB back then
12:03.01freemangordon_though it could be that I just forgot
12:03.11DocScrutinizer05http://omappedia.org/wiki/Bootloader_Project
12:04.54DocScrutinizer05>>Note: If you are using an HS (High Security) OMAP device, an extra step is required. First, build x-load.bin using the steps above. Then, download the MShield signing tool and use the commands below. Contact your TI representative to get access to this tool.<<  o.O
12:06.29DocScrutinizer05now who's at home in darknet? ;-) find that tool
12:06.57DocScrutinizer05though... prolly Nokia had their own keys
12:08.18DocScrutinizer05~#maemo boot is http://omappedia.org/wiki/Bootloader_Project
12:08.18infobotokay, DocScrutinizer05
12:16.30*** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr)
12:27.41bencohxloader is signed on n900?
12:36.20DocScrutinizer05I *think* yes
12:37.49DocScrutinizer05the question rather is if it *needs* to be signed, or if a HS device would behave exactly like a GP device when yiu use a GP (unsigend) xloader
12:40.03DocScrutinizer05this basically boils down to the question if GP and HS SoCs share same ROMBL (or if the ROMBL maybe has a check if there's a HS key or not and acts differently when there is)
12:51.55*** join/#maemo dafox (~dafox@2a02:a448:c25a:1:7061:3b2a:37df:ded3)
12:57.00*** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr)
12:58.07DocScrutinizer05>>It's also worth noting the TI did not technically disable TrustZone. Instead, the bootrom code transitions the processor into the Normal world prior to switching execution to U-boot. So it's actually using TrustZone to move to the Normal world, but then doesn't provide a mechanism for moving back to the Secure world<<  https://stackoverflow.com/questions/7955982/arm-trustzone-development
12:58.21*** join/#maemo err0r3o3 (~err0r3o3@88-117-124-16.adsl.highway.telekom.at)
13:01.57DocScrutinizer05>>Yes, things have changed considerable to the positive after 5 years :) << 2017-06-29
13:06.04DocScrutinizer05hmmm https://github.com/OP-TEE/optee_os
13:06.30DocScrutinizer05~trust
13:06.30infobotrumour has it, trust is safe, or http://www.youtube.com/watch?v=0cbS_lDJuJg
13:06.32DocScrutinizer05?
13:11.18DocScrutinizer05this whole trustzone stuff is as intangible as... No docs at all
13:13.24DocScrutinizer05and I still don't buy it that there's any benefit from it for end users that couldn't get achieved as well (and actually always been) by mere decent implementation of classical OS-based permission handling
13:15.49DocScrutinizer05as soon as you hand the signing tools to unwashed public, there's no visible benefit from trusted computing at all
13:21.59*** join/#maemo xy2_ (~xy2_@94.239.253.5)
13:25.15*** join/#maemo chfoo[m] (chfoomatri@gateway/shell/matrix.org/x-wmdpvnhojaiibnxl)
13:42.05*** join/#maemo dmth|intevation (~dmth|inte@2001:470:747a:2a:6af7:28ff:fe64:1ded)
13:54.33DocScrutinizer05a completely different topic: FSF RYF
13:54.48*** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr)
13:55.40DocScrutinizer05from dng@lists.dyne.org  "From:"Taiidan@gmx.com" <Taiidan@gmx.com> Re: [DNG] Purism Librem and disabling Intel ME: it can be done [ Re: TALOS 2 - The Libre Owner Controlled POWER9 Workstation/Server ]  2017-09-08 Fri 06:22"
13:56.26DocScrutinizer05>> Full documentation and HDL's will be available for all components besides the onboard broadcom nics which currently require a firmware blob as there are no open source non-intel gigabit NIC's - but the FSF says that this minor detail doesn't prevent it from receiving RYF certification as they are behind the POWER-IOMMU and as such are not capable of doing anything malicious.<<
13:57.40DocScrutinizer05I wonder how they can do this for that hardware, but then consider Neo900 doing basically same as sufficient reason to deny RYF
13:58.19*** join/#maemo err0r3o3 (~err0r3o3@88-117-124-16.adsl.highway.telekom.at)
13:59.42DocScrutinizer05we also have no open source WLAN/BT solution available and whatever that IOMMU it's not better than a mere SDIO hw interface
14:01.02DocScrutinizer05and I don't think I want to even start about our modem sandbox solution that's definitely way beyond anything IOMMU
14:01.29DocScrutinizer05anybody FSF around to comment?
14:16.13*** join/#maemo err0r3o3 (~err0r3o3@88-117-124-16.adsl.highway.telekom.at)
15:31.05*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
15:43.13Pali~deb2dsc
15:43.13infobothmm... deb2dsc is on http://pastebin.com/ZPuYnZPr
15:43.23Palifreemangordon ↑↑↑
15:44.26Wizzupjesus. only on pastebin? :D
15:45.30freemangordonPali: thanks
15:46.09bencoh:D
15:47.02*** join/#maemo ntinos (~quassel@snf-766783.vm.okeanos.grnet.gr)
15:58.49freemangordonPali: (and the others) how it sounds "Oroshi" as a codename for that maemo-devuan frankenstein?
16:00.14WizzupOroshi?
16:00.21Wizzupwe had some codenames, but not project names
16:00.25Wizzupe.g. 'kawai'
16:00.43freemangordonWizzup: nokia used to name releases after winds
16:00.57Wizzupok. I am going to be afk for a bit.
16:01.03KotCzarnyis there a name for 'wind of change' ?
16:01.05Wizzupneed food
16:01.11freemangordonKotCzarny: no idea
16:01.28KotCzarnyor wind of hope
16:02.21freemangordonKotCzarny: I found ^^^ at wikipedia, feel free to suggest another one if you need symbolics. I coose it because it sounds pretty much ok and simple
16:02.25freemangordon*choose
16:03.12freemangordonKotCzarny: https://en.wikipedia.org/wiki/List_of_local_winds
16:04.43freemangordonKona and Leste sound ok as well
16:04.53KotCzarnyyeah, it should come after 'h'
16:05.00freemangordonmhm
16:05.22KotCzarnyChinook, Diablo, Fremantle, Harmattan
16:05.29freemangordonMeltemi ;)
16:05.34KotCzarnyBora before chinook
16:05.35freemangordonnad Bora
16:05.55KotCzarnyLoo ? ;)
16:05.58freemangordonhmm, maybe Kona is better
16:06.15KotCzarnyKhamsin isnt bad either
16:06.25freemangordonno, Loo doesn;t sound tasty :D
16:06.50KotCzarnyanyway, all winds starting with K on that page sound cool
16:07.09freemangordonI like Kona more, it is shorter but still sounds good
16:07.57freemangordonok, if no objections in the next couple of hours, then it will be Lona :)
16:08.00freemangordon*Kona
16:08.10KotCzarnyhttp://mentalfloss.com/article/56382/21-wonderful-words-wind
16:08.13KotCzarnymore names
16:08.26KotCzarnywilly-willy ?
16:08.51freemangordonhehe
16:31.30drathirLuna mmm....
16:31.59drathirKira
16:34.42drathirignore that... ^^
16:43.55*** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix)
16:53.03sixwheeledbeastis getting deja-vu
16:53.12sixwheeledbeasthttp://mg.pov.lt/maemo-irclog/%23maemo.2017-02-03.log.html
16:54.05sixwheeledbeastI recall liking "Ostria" A warm southerly wind on the Bulgarian coast :)
17:04.20*** join/#maemo err0r3o3_ (~err0r3o3@88-117-124-16.adsl.highway.telekom.at)
17:05.59*** join/#maemo phlixi (~phlixi@ppp-46-244-140-185.dynamic.mnet-online.de)
17:13.58*** join/#maemo eMHa (~mh@p200300738E28D100267703FFFE6CC360.dip0.t-ipconnect.de)
17:25.09*** join/#maemo heroux (~heroux@gateway/shell/insomnia247/x-xjiddtbiajkkkbdv)
17:53.08*** join/#maemo err0r3o3_ (~err0r3o3@194-166-171-87.adsl.highway.telekom.at)
17:57.49DocScrutinizer05https://www.armis.com/blueborne
18:11.14*** join/#maemo xy2_ (~xy2_@94.239.177.175)
18:12.53freemangordonsixwheeledbeast: ah, I remember I told you there is no such word in Bulgarian, back then :)
18:13.48DocScrutinizer05freemangordon: ^^^
18:14.03DocScrutinizer05please rate severety for maemo
18:14.14freemangordonDocScrutinizer05: I'm reading through it
18:14.19DocScrutinizer05ta
18:14.52DocScrutinizer05stack overflow in bluetooth.ko?
18:20.02DocScrutinizer05they pitched it well for maximum publicity with minimum help for experts to actually investigate
18:20.24DocScrutinizer05at least a few random CVE are mentioned
18:21.55freemangordonDocScrutinizer05: All Linux devices from version 3.3-rc1 (released in October 2011) are  affected by the remote code execution vulnerability (CVE-2017-1000251).
18:22.03freemangordonso this does not affect n900
18:22.12freemangordonthe other one affects us, I guess
18:22.13DocScrutinizer05:-) at least
18:22.37freemangordonAll Linux devices running BlueZ are affected by the information leak vulnerability (CVE-2017-1000250).
18:23.00DocScrutinizer05please share URLs to genuine CVE database
18:23.24DocScrutinizer05I have a hard time finding it right now
18:23.31*** join/#maemo FalconSpy_ (~falconspy@ip72-208-197-193.ph.ph.cox.net)
18:24.15freemangordonI don't have urls for those, I read what is on Armis Labs page
18:24.22DocScrutinizer05ooh
18:24.36freemangordongoogling leadds to some fedora and redhat pages
18:24.40DocScrutinizer05I fvrown at the latter one
18:24.41freemangordon*leads
18:24.55DocScrutinizer05there are multiple massively different Bluez implementations
18:25.00freemangordonhttps://bugzilla.redhat.com/show_bug.cgi?id=1490911
18:25.47freemangordonwhere is bluez upstream?
18:25.53DocScrutinizer05nfc
18:26.04DocScrutinizer05next to PA?
18:26.16*** join/#maemo phlixi (~phlixi@ppp-46-244-140-185.dynamic.mnet-online.de)
18:26.42freemangordonhttps://git.kernel.org/pub/scm/bluetooth/bluez.git
18:32.38sixwheeledbeasthttps://nvd.nist.gov/vuln/detail/CVE-2017-1000250
18:34.16*** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr)
18:35.34DocScrutinizer05sixwheeledbeast: ta
18:36.12sixwheeledbeastnp
18:36.48DocScrutinizer05https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9445  I guess was the one I looked for
18:37.48DocScrutinizer05err, or nearby, anyway MITRE
18:38.48DocScrutinizer05https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000250
18:58.05*** join/#maemo Kabouik_ (~kabouik@2a01:e35:2fd3:5030:e142:c406:c878:1d89)
18:58.30DocScrutinizer05cf  https://bugzilla.redhat.com/show_bug.cgi?id=1490911
18:58.36DocScrutinizer05iips sorry
19:33.02*** join/#maemo LauRoman (~LauRoman@5-14-5-68.residential.rdsnet.ro)
20:01.16*** join/#maemo florian (~fuchs@x4db5bdc0.dyn.telefonica.de)
20:27.10*** join/#maemo jkepler (~Thunderbi@gateway/vpn/privateinternetaccess/jkepler)
20:49.45*** join/#maemo xorly (~xorly@ip-86-49-24-93.net.upcbroadband.cz)
20:56.02*** join/#maemo rhn_mk1 (~rhn@unaffiliated/rhn)
21:22.46*** join/#maemo rhn (~rhn@pD4B9E2C5.dip0.t-ipconnect.de)
21:22.46*** join/#maemo rhn (~rhn@unaffiliated/rhn)
21:25.15*** join/#maemo thuttu77 (~thuttu77@82-181-37-124.bb.dnainternet.fi)
21:43.41*** join/#maemo Milhouse (~Milhouse@kodi/staff/milhouse)
23:28.54*** join/#maemo pagurus (~user@i59F7CB75.versanet.de)
23:29.05*** join/#maemo herekun (~herekun@164.132.132.199)
23:29.33*** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr)
23:44.56*** join/#maemo nslu2-log (~nslu2-log@milla.nas-admin.org)
23:48.58*** join/#maemo peetah_ (~peetah@cha92-9-82-236-202-86.fbx.proxad.net)
23:49.16*** join/#maemo ArGGu^^ (~ArGGu^^@dsl-trebng12-b04895-48.dhcp.inet.fi)
23:49.37*** join/#maemo dos1 (~dos1@dosowisko.net)
23:49.42*** join/#maemo dos1 (~dos1@neo900/coreteam/dos)
23:53.50*** join/#maemo Mek (~quassel@kde/mkruisselbrink)
23:54.12*** join/#maemo chainsawbike (~chainsawb@unaffiliated/chainsawbike)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.