| 01:33.49 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 03:08.25 | *** join/#maemo florian__ (~florian_k@Maemo/community/contributor/florian) |
| 04:43.45 | *** join/#maemo APic (apic@apic.name) |
| 05:15.42 | *** join/#maemo Oksana (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 06:15.33 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 06:36.39 | *** join/#maemo Vajb (~Vajb@85-76-72-191-nat.elisa-mobile.fi) |
| 07:27.21 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 07:37.56 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 08:28.17 | *** join/#maemo mva_ (znc@gentoo/contributor/mva) |
| 08:54.38 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 09:06.39 | *** join/#maemo err0r3o3_ (~err0r3o3@178-191-18-63.adsl.highway.telekom.at) |
| 09:21.52 | *** join/#maemo guerby_ (~guerby@ip165.tetaneutral.net) |
| 09:26.35 | *** join/#maemo auenfx8 (~David@120.154.78.136) |
| 09:28.45 | *** join/#maemo auenf (~David@120.154.78.136) |
| 09:36.00 | *** join/#maemo guerby (~guerby@april/board/guerby) |
| 10:04.21 | *** join/#maemo xorly (~xorly@ip-86-49-24-93.net.upcbroadband.cz) |
| 10:39.02 | *** join/#maemo nslu2-log_ (~nslu2-log@milla.nas-admin.org) |
| 10:40.12 | *** join/#maemo hurrian_ (~textual@112.210.151.206) |
| 11:30.53 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 11:36.57 | *** join/#maemo louisdk (~louisdk@5.103.138.205) |
| 12:41.38 | *** join/#maemo xray256 (~xray256@host86-153-172-0.range86-153.btcentralplus.com) |
| 12:49.28 | *** join/#maemo xy2_ (~xy2_@94.239.253.5) |
| 12:51.21 | *** join/#maemo xy2_ (~xy2_@94.239.253.5) |
| 13:30.52 | *** join/#maemo florian__ (~florian_k@Maemo/community/contributor/florian) |
| 14:08.35 | *** join/#maemo florian__ (~florian_k@Maemo/community/contributor/florian) |
| 15:10.21 | *** join/#maemo florian__ (~florian_k@Maemo/community/contributor/florian) |
| 15:37.59 | *** join/#maemo juiceme (~juice@Maemo/community/council/juiceme) |
| 16:28.46 | sicelo | DocScrutinizer05: ping |
| 16:28.55 | DocScrutinizer05 | hm? |
| 16:29.29 | DocScrutinizer05 | oooh, sunday |
| 16:29.30 | sicelo | hi |
| 16:29.40 | sicelo | indeed |
| 16:30.03 | DocScrutinizer05 | seems there was some "important" thing? |
| 16:30.51 | sicelo | <PROTECTED> |
| 16:31.25 | sicelo | you're able to join? |
| 16:31.33 | DocScrutinizer05 | sure |
| 16:32.04 | sicelo | thank you very much :) |
| 16:33.30 | DocScrutinizer05 | np |
| 16:48.04 | DocScrutinizer05 | Oksana: ping |
| 16:48.29 | DocScrutinizer05 | Oksana: MC eV GA meeting in #maemo.meeting |
| 17:57.13 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 18:04.39 | *** join/#maemo Kabouik (~kabouik@239.72.95.88.customer.cdi.no) |
| 18:05.09 | *** join/#maemo xy3_ (~xy2_@94.239.177.175) |
| 18:12.02 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 18:39.56 | *** join/#maemo pagurus (~user@i59F775A3.versanet.de) |
| 18:54.52 | blap | ever see the isis flag? |
| 18:55.19 | KotCzarny | yeah, few folks doing the sheeps |
| 18:57.08 | blap | very interesting |
| 18:57.21 | blap | they like to show the truth in their symbols |
| 19:37.09 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 19:37.45 | DocScrutinizer05 | huh? |
| 19:41.12 | blap | people who make scrawly images often want them to refer to ideologies or groups DocScrutinizer05 |
| 19:41.21 | blap | so it sometimes is useful to study what symbols they choose |
| 19:43.01 | DocScrutinizer05 | I'd expect isis to not use *any* pictures at all, since.. a misconception about pictures from their understanding of Quran |
| 19:44.27 | DocScrutinizer05 | and iirc that flag is mere Arabian writing, with a lot of deco |
| 19:47.14 | DocScrutinizer05 | like this, sort of ;-) https://www.ixquick.com/do/search?q=isis+flag&nj=0&cat=pics |
| 19:50.49 | DocScrutinizer05 | prolly too much ink in that one: https://qph.ec.quoracdn.net/main-qimg-4b819495fcfdd9d2c754d832d973b695-c |
| 19:52.30 | DocScrutinizer05 | ((<NeKit> is Nokia N900 set up differently then?)) yes, N900 and Neo900 have a properly separated modem |
| 19:52.55 | NeKit | Droid 4 likely too then, since it's OMAP4 |
| 19:53.07 | DocScrutinizer05 | is it? |
| 19:53.41 | NeKit | http://elektranox.org/2017/02/0013-droid-4-modem/ |
| 19:53.59 | DocScrutinizer05 | weird, I checked a few days ago what I *thought* was driod4 and gsmarena said sth like "snapdragon 617" |
| 19:54.43 | KotCzarny | http://www.gsmarena.com/motorola_droid_4_xt894-4418.php |
| 19:54.46 | DocScrutinizer05 | must have been another device I checked, then |
| 19:54.49 | KotCzarny | says omap 4430 |
| 19:55.11 | KotCzarny | maybe there are more than 1 device under droid4 name |
| 19:55.13 | DocScrutinizer05 | aaah http://www.gsmarena.com/motorola_moto_g4-8103.php |
| 19:55.37 | DocScrutinizer05 | nah, I mixed names |
| 19:56.33 | KotCzarny | launch january 2012 |
| 19:56.34 | KotCzarny | lol |
| 19:58.57 | DocScrutinizer05 | it's pathetic how gsmarena not even _mentions_ the modem chipset |
| 19:59.39 | DocScrutinizer05 | also symptomatic of the general ignorance regarding the topic |
| 19:59.49 | KotCzarny | yup |
| 20:00.11 | KotCzarny | regular joe only knows core quantityt and screen size |
| 20:00.22 | KotCzarny | sometimes even cpu clock and ram size |
| 20:00.35 | KotCzarny | but that's considered hacker's knowledge |
| 20:01.42 | DocScrutinizer05 | they should be more interested in e.g. if their WLAN is a broadcom chipset and thus vulnerable |
| 20:02.11 | sicelo | what does 'vulnerable' mean .. :-) |
| 20:02.18 | sicelo | that's the quesiton 'joe' will ask |
| 20:02.31 | DocScrutinizer05 | https://googleprojectzero.blogspot.de/2017/04/over-air-exploiting-broadcoms-wi-fi_11.html |
| 20:02.32 | KotCzarny | it means 'you take it in the ass without the soap' |
| 20:04.34 | DocScrutinizer05 | awesome how diagram in ^^^ shows a separate "baseband processor" which is _not_ what it regularly looks like today |
| 20:05.47 | blap | <PROTECTED> |
| 20:14.56 | DocScrutinizer05 | one core statement >>Well⦠Until several months prior to this research (mid 2016), the firmware made no effort to filter these frames. Any frame received as part of the data RX-path, regardless of its ethertype, was simply forwarded blindly to the host. As a result, attackers were able to remotely send frames containing the special 0x886C ethertype, which were then processed by the driver as if they were event frames created by the |
| 20:14.57 | DocScrutinizer05 | firmware itself!<< |
| 20:25.00 | DocScrutinizer05 | sicelo: in short it means: an atacker can *completely* take over control over your device, via WLAN |
| 20:25.14 | KotCzarny | remotely. |
| 20:26.34 | DocScrutinizer05 | and I mean *completely*, even to or beyond what user could do after rooting their device |
| 20:27.12 | sicelo | yes. i mean ... average joes don't seem to owrry themselves with all that. all they want is an iphone :-) |
| 20:27.18 | sicelo | *worry |
| 20:27.56 | DocScrutinizer05 | well, they also want apple's encryption and no-unlock policies |
| 20:28.30 | DocScrutinizer05 | prolly not only against FBI but also the random hacker attacker |
| 20:29.18 | DocScrutinizer05 | on the bright side, rooting all those smartphones with broadcom WLAN is as simple as hardly ever before, also for user |
| 20:29.24 | DocScrutinizer05 | ;-P |
| 20:35.13 | *** join/#maemo Kabouik_ (~kabouik@176.31.13.108) |
| 20:36.38 | *** join/#maemo __Chris (~Chris@p4FCA1E56.dip0.t-ipconnect.de) |
| 20:37.29 | DocScrutinizer05 | and for the rest... PCIe to the rescue X-P |
| 20:38.07 | DocScrutinizer05 | isn't it a *great* idea when the peripheral can do autonomous DMA? |
| 20:38.18 | DocScrutinizer05 | (j/k) |
| 20:54.54 | DocScrutinizer05 | >>Aha! The Wi-Fi chip managed to DMA into the physical address range containing the hostâs kernel, without any interference!<< LOL |
| 20:56.36 | DocScrutinizer05 | >>Not only does this kind of access not require a single vulnerability [[except control over the WiFi chip's firmware which is given by the original exploit]] , but it is also much more reliable to exploit<< |
| 20:57.35 | DocScrutinizer05 | Broadcom, the better bootloader/kexec for your android device ;-P |
| 21:00.03 | DocScrutinizer05 | up to further hw platform examination if it also works as wireless (android) firmware flasher right away, or if they somehow have an additional level of write protection for the firmware storage |
| 21:00.56 | NeKit | <s>can this be used to install Linux on BlackBerry keyboard devices?</s> |
| 21:02.19 | __Chris | DocScrutinizer05: See what questions you get now? :-) |
| 21:02.51 | *** join/#maemo Kabouik- (~kabouik@239.72.95.88.customer.cdi.no) |
| 21:02.57 | DocScrutinizer05 | LOL |
| 21:03.06 | __Chris | giggles. |
| 21:03.34 | DocScrutinizer05 | netkat: in theory for sure. Practically I have no idea |
| 21:04.06 | __Chris | Maybe we can ask about on the FB-page of broadcom.... If they have something like that. ^^ |
| 21:04.07 | DocScrutinizer05 | NeKit: damn |
| 21:04.26 | DocScrutinizer05 | my tab completion fails on n vs N here |
| 21:13.05 | DocScrutinizer05 | >> letâs repeat the same experiment on a Galaxy S7 Edge, which is based on Samsungâs Exynos 8890 SoC. [...] Once again we are able to DMA freely into the kernel (bypassing RKPâs protection along the way)! It seems that both Samsungâs Exynos 8890 SoC and Qualcommâs Snapdragon 810 either lack SMMUs or fail to utilise them<< |
| 21:14.05 | DocScrutinizer05 | (SMMU == IOMMU) |
| 21:21.02 | blap | ponders |
| 21:21.39 | blap | that's a horrible thing |
| 21:21.48 | blap | that's like economics departments teaching lies to students |
| 21:24.40 | DocScrutinizer05 | hm? |
| 21:26.50 | *** join/#maemo auenfx8 (~David@120.154.78.136) |
| 21:27.29 | *** join/#maemo auenf (~David@120.154.78.136) |
| 21:31.52 | blap | nobody saying anything about phones |
| 21:31.58 | blap | the terrible security |
| 21:32.19 | Wizzup | in 74 |
| 21:32.21 | Wizzup | oops. |
| 21:37.24 | __Chris | People only want to have some cloud, g00gle, bling-bling-flat-design for showing ads and some curvy displays it seems. |
| 21:38.13 | __Chris | OLEDs which get yellow and burned in in 2 years of usage too. |
| 21:38.49 | DocScrutinizer05 | well, you're aware that SMS_two-factor-auth is already deprecated? Now think about NFC payment |
| 21:41.12 | *** join/#maemo Kabouik_ (~kabouik@ks3100825.kimsufi.com) |
| 21:42.15 | DocScrutinizer05 | doesn't need any far fetched scenario like hacking the smartphone navi to lure digital retards and their cars into dark side streets to rob all they got |
| 21:42.57 | DocScrutinizer05 | anyway I am pretty sure we will see all of that and more |
| 21:46.52 | *** join/#maemo Kabouik- (~kabouik@239.72.95.88.customer.cdi.no) |
| 21:54.14 | blap | i have nothing to say in contradiction |
| 22:10.07 | DocScrutinizer05 | not trying to feature FUD, just I'm pretty sure that "People only want to have some cloud, g00gle, bling-bling-flat-design..." of those people will and already does change drastically, considering what we're heading at |
| 22:11.16 | DocScrutinizer05 | bling-bling-flat-design..." '+attitude' of |
| 22:14.21 | DocScrutinizer05 | soon old good style phones like N900 and even feature phones will be as useful and popular as torches, in a world where batteries for flashlights are expensive and explosive and hard to find |
| 22:17.15 | DocScrutinizer05 | and I think the market for a smartphone designed according to best practice regarding security and privacy like the Neo900 is better than ever |
| 22:19.59 | DocScrutinizer05 | I'm absolutely sure the electronics engineers who desined all that new rogue and vulnerable stuff are either well aware but ignorant of the design flaws / compromises they chosen for sake of lower costs, or they are incredibly incompetent |
| 22:23.34 | __Chris | DocScrutinizer05: It was meant more sarcastic. No worries. |