| 00:00.16 | *** join/#maemo arossdotme-planb (~zxy@host-84-13-235-151.opaltelecom.net) |
| 00:01.09 | DocScrutinizer05 | or a HTTP forward (301 Moved Permanently) |
| 00:03.19 | DocScrutinizer05 | dos1: could we create a subdomain downloads.maemo.neo900.org? and for now point it to muarf? |
| 00:03.52 | *** join/#maemo darkschneider (~gab@93-32-51-166.ip32.fastwebnet.it) |
| 00:04.43 | DocScrutinizer05 | by either an A, CNAME, or even a webpage with a 301 - whatever works best for HAM |
| 00:06.18 | kerio | DocScrutinizer05: i think our apt doesn't follow redirects, idk about HAM though |
| 00:06.33 | DocScrutinizer05 | hmm, HAM uses apt |
| 00:06.44 | kerio | yeah but it's its own implementation, or something |
| 00:06.51 | DocScrutinizer05 | k |
| 00:07.03 | dos1 | DocScrutinizer05: we could, but for A/CNAME it most likely needs webserver config support on muarf side |
| 00:07.12 | dos1 | (vhost) |
| 00:07.16 | DocScrutinizer05 | :nod: |
| 00:07.31 | kerio | it's all in apt-worker |
| 00:07.33 | DocScrutinizer05 | that's what I meant by "we have no control over muarf" |
| 00:08.28 | DocScrutinizer05 | dos1: could we test if muarf has a catch-all (*) vhost? |
| 00:08.33 | dos1 | I have downloads.maemo.nokia.com pointed via /etc/hosts to my local PC configured to accept this vhost |
| 00:08.46 | dos1 | sure, just give me a link to muarf |
| 00:08.57 | DocScrutinizer05 | ~repo |
| 00:08.58 | infobot | repos is probably "deb http://maemo.muarf.org/apt-mirror/mirror/downloads.maemo.nokia.com/fremantle/ssu/apps/ ./ ;; deb http://maemo.muarf.org/apt-mirror/mirror/downloads.maemo.nokia.com/fremantle/ssu/mr0/ ./", or see http://wiki.maemo.org/Repository#List_of_Maemo_repositories |
| 00:10.50 | *** join/#maemo Arch-KT (Arch-TK@fsf/member/Arch-TK) |
| 00:11.05 | dos1 | nope, default vhosts points to something that returns HTTP/1.1 401 Authorization Required |
| 00:11.14 | dos1 | s/vhosts/vhost/ |
| 00:11.23 | *** join/#maemo lool- (~lool@debian/developer/lool) |
| 00:11.34 | DocScrutinizer05 | grr |
| 00:12.06 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 00:12.13 | *** join/#maemo louis_ (~louisdk@static-5-103-130-65.seas-nve.net) |
| 00:12.32 | DocScrutinizer05 | we need a mirror that allows council to point to it via a DNS record the community has under direct control |
| 00:13.13 | DocScrutinizer05 | so if anybody decides to take down the mirror, the DNS could get updated to point to another one |
| 00:14.18 | DocScrutinizer05 | or would the domain owner be responsible for content under a IP he doesn't own? |
| 00:15.09 | dos1 | I think that might depend on jurisdiction |
| 00:15.18 | DocScrutinizer05 | when neo900 points A to muarf, if somebody approaches me I only can take down the DNS record since I got no clue where and who is muarf |
| 00:15.50 | DocScrutinizer05 | I'd prefer a CNAME or 301 though |
| 00:16.23 | DocScrutinizer05 | CNAME should be resolver level, 301 alas is HTTP level |
| 00:17.22 | dos1 | A and CNAME are here virtually the same cases, the only thing that changes is that we wouldn't have to update our domain is muarf A record changes |
| 00:17.59 | DocScrutinizer05 | :nod: |
| 00:18.22 | DocScrutinizer05 | CNAME however documents that we're not necessarily owner of the domain |
| 00:18.38 | *** join/#maemo ab_ (~ab@vda.li) |
| 00:18.38 | *** join/#maemo ab_ (~ab@pdpc/supporter/professional/ab) |
| 00:19.30 | DocScrutinizer05 | and since we're not related to council, we may point to a domain we shouldn't point to if we were council or HiFo |
| 00:19.33 | dos1 | well, instead of pointing to IP, you point to another domain - and you don't own that domain just the same way you don't own that IP |
| 00:20.01 | DocScrutinizer05 | yes, *I* know that ;-) |
| 00:20.27 | dos1 | not trying to explain technicalities to you :D I just don't see anything "documented" there regading the ownership |
| 00:20.40 | DocScrutinizer05 | the amount of ownership info differs between IP and domain though |
| 00:21.01 | *** join/#maemo Mek (~quassel@kde/mkruisselbrink) |
| 00:21.19 | DocScrutinizer05 | CNAME muarf.org; whois muarf.org |
| 00:21.35 | dos1 | ah, "look, whois says it's not mine" :) |
| 00:21.38 | DocScrutinizer05 | A <IP-of-muarf.org>; ??? IP |
| 00:22.03 | DocScrutinizer05 | yes, exactly |
| 00:23.25 | DocScrutinizer05 | warfare: would you consider using a "downloads.maemo.maemo.org CNAME muarf.org" a thing we might dare to do? |
| 00:26.24 | DocScrutinizer05 | prolly using a 'foreign domain' like downloads.maemo.neo900.org is less conflict potential for the maemo 'authorities' |
| 00:29.50 | DocScrutinizer05 | actually it's jussi who 'owns' maemo.org |
| 00:30.15 | DocScrutinizer05 | according to whois |
| 00:30.41 | DocScrutinizer05 | of course HiFo/whovernow-eV is the legal owner |
| 00:37.21 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 00:56.27 | *** join/#maemo vectis3 (~user@79-64-234-154.host.pobb.as13285.net) |
| 00:56.54 | M-bobsummerwill | Hello everyone! I'm a bit late to the party, I know but ... |
| 00:56.55 | M-bobsummerwill | https://twitter.com/doublethink_co/status/680056050880389120?s=09 |
| 01:02.04 | *** join/#maemo louis_ (~louisdk@static-5-103-130-65.seas-nve.net) |
| 01:04.00 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 01:16.34 | DocScrutinizer05 | humm, what is ethereum? |
| 01:18.08 | DocScrutinizer05 | the N+1'th container implementation? |
| 01:25.18 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 01:36.56 | *** join/#maemo vectis3 (~user@79-64-234-154.host.pobb.as13285.net) |
| 01:50.38 | *** join/#maemo hashcore (~hashcore@unaffiliated/hashcore) |
| 01:51.18 | Luke-Jr | DocScrutinizer05: a group of guys learning consensus systems; (possibly legally) funded by idiots who think it will become the next Bitcoin |
| 01:51.49 | DocScrutinizer05 | duh, realy? |
| 01:52.39 | DocScrutinizer05 | https://www.ethereum.org/ didn't give that away |
| 01:53.33 | DocScrutinizer05 | oh yeah, keywords "contracts" and "blockchain" |
| 01:53.53 | *** join/#maemo realitygaps (~realityga@2a01:4a0:3::5096:aeb) |
| 01:53.53 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 01:56.06 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 01:56.48 | Luke-Jr | there may be ethical problems with their public-facing promotional materials (but I don't have time to go through them and state for certain) |
| 01:58.24 | DocScrutinizer05 | indeed that website doesn't tell too much about what this stuff _really_ is and does. I mean... "Ethereum is how the Internet was supposed to work." really now? |
| 01:58.55 | Luke-Jr | they take too much in the footsteps of many scam "altcoins" before them |
| 02:00.04 | Luke-Jr | basically trying to keep the scamcoin 'profits' but do it legit |
| 02:00.14 | DocScrutinizer05 | >>Ether is the internal 'fuel' of Ethereum. Programs running on Ethereum need to pay the network for the resources they consume.<< |
| 02:00.53 | DocScrutinizer05 | all sounds *very* cloudy and weird |
| 02:02.06 | Luke-Jr | it's basically stupid, but hopefully they'll learn something in the process of doing it |
| 02:02.07 | DocScrutinizer05 | why the heck would I "run a program on Ethereum"? |
| 02:02.33 | Luke-Jr | (no reasons come to mind) |
| 02:04.08 | DocScrutinizer05 | if this is the future then please I want to die before it becomes prevalent |
| 02:04.54 | Luke-Jr | it isn't. :P |
| 02:05.24 | Luke-Jr | Bitcoin has scaling problems already; with Ethereum's nonsense, those become 100000000 times worse |
| 02:05.32 | Luke-Jr | and Bitcoin's solutions no longer really work |
| 02:06.10 | Luke-Jr | essentially every program run "on Ethereum" really means every single computer in the Ethereum network is independently and redundantly executing it |
| 02:06.32 | DocScrutinizer05 | ouch |
| 02:07.17 | Luke-Jr | the same is more or less true of Bitcoin, but Bitcoin is specifically a single *simple* purpose (currency/finance), and there is scalability work to cut-through overlapping transfers |
| 02:07.43 | DocScrutinizer05 | doubleplusOUCH |
| 02:07.53 | Luke-Jr | (that is, if A pays B, B pays C, and C pays A, only the differences get settled on the public/shared ledger) |
| 02:08.04 | Luke-Jr | (more complex routing also possible of course) |
| 02:08.57 | DocScrutinizer05 | such a thing obviously can't scale |
| 02:10.58 | Luke-Jr | DocScrutinizer05: the routing network is implemented without the shared execution |
| 02:11.55 | DocScrutinizer05 | M-bobsummerwill: >>So I have *cracked* and bought a N900 on eBay to see for myself what is so special about it.<< welcome on board :-) and you'll notice the most special thing about N900 is that there's aömost nothing special with it. It's smply a very small linux computer, with a phone built in |
| 02:13.30 | DocScrutinizer05 | a slightly unusual desktop manager called hildon - though you *could* even run KDE or whatever you like, on it |
| 02:14.24 | DocScrutinizer05 | and that's the very unusual thing for a phone: it's a very usual linux PC |
| 02:19.11 | *** join/#maemo realitygaps (~realityga@2a01:4a0:3::5096:aeb) |
| 02:19.11 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 02:21.04 | DocScrutinizer05 | M-bobsummerwill: or simply watch this: https://www.youtube.com/watch?v=66RBfrBgL2E |
| 02:37.21 | DocScrutinizer05 | M-bobsummerwill: first thing you want to do on N900: ~flashing anew, then open browser and navigate to http://maemo.cloud-7.de/maemo5/et_al/HAM-catalogs/muarf.install |
| 02:37.33 | DocScrutinizer05 | ~flashing |
| 02:37.33 | infobot | maemo-flashing is, like, http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh |
| 02:38.31 | DocScrutinizer05 | then: |
| 02:38.34 | DocScrutinizer05 | ~cssu |
| 02:38.34 | infobot | hmm... cssu is http://wiki.maemo.org/Community_SSU, or (Community Seamless Software Update) |
| 02:47.18 | *** join/#maemo Humpelstilzchen (erik@f054096065.adsl.alicedsl.de) |
| 02:47.30 | *** join/#maemo eMHa__ (~mh@p579DB9BE.dip0.t-ipconnect.de) |
| 03:12.28 | *** join/#maemo krnlyng (~liar@178.114.84.229.wireless.dyn.drei.com) |
| 03:43.58 | *** join/#maemo ruskie (ruskie@sourcemage/mage/ruskie) |
| 03:58.30 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 04:10.59 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 04:39.16 | *** join/#maemo Roth (~quassel@2601:18c:c700:c4d3:2451:22c1:871a:e75b) |
| 04:54.50 | *** join/#maemo Venusaur (~wdwrwf@wikipedia/Antonio-Lopez) |
| 05:27.36 | *** join/#maemo Arch-TK (Arch-TK@fsf/member/Arch-TK) |
| 05:57.13 | *** join/#maemo Gadgetoid (~Gadgetoid@customers.shef1.resi.ask4.co.uk) |
| 06:09.08 | *** join/#maemo Arch-TK (Arch-TK@fsf/member/Arch-TK) |
| 06:32.20 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 06:34.29 | jonwil | hi |
| 07:33.44 | *** join/#maemo robink_ (~quassel@unaffilated/robink) |
| 07:50.37 | *** join/#maemo coderus (~coderus@static.88-198-208-108.clients.your-server.de) |
| 07:50.43 | coderus | plz save me |
| 07:50.53 | coderus | Sorry, it seems that you are using an IP address or a proxy that is listed in the forum anti spam blacklist. |
| 07:50.56 | coderus | Feel free to contact our staff on irc freenode #maemo channel. |
| 07:51.05 | coderus | 188.165.30.151 |
| 07:51.12 | KotCzarny | ~unbanip |
| 07:51.12 | infobot | i guess unbanip is please contact techstaff <at> maemo <dot> org with your request, or see ~techstaff |
| 07:53.16 | coderus | okay emailed, thx! |
| 07:53.18 | *** part/#maemo coderus (~coderus@static.88-198-208-108.clients.your-server.de) |
| 08:03.59 | *** join/#maemo Arch-TK (Arch-TK@fsf/member/Arch-TK) |
| 08:15.39 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 08:24.15 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 08:24.19 | *** join/#maemo krnlyng (~liar@77.117.103.28.wireless.dyn.drei.com) |
| 08:24.45 | KotCzarny | pali, why do you want to rely on .n.c/m$ anyway? |
| 08:25.15 | KotCzarny | imo there should be cssu release as a flashable firmware |
| 08:25.26 | KotCzarny | call it 1.4-cssu1 or something |
| 08:25.30 | *** join/#maemo vahe (~funtoo@130.193.124.135) |
| 08:25.45 | KotCzarny | or just 1.4 |
| 08:25.45 | Pali | KotCzarny: we cannot redistribute nokia bins via r.m.o |
| 08:25.56 | Pali | only unofficial |
| 08:26.03 | KotCzarny | can't you do it unofficially? |
| 08:26.11 | Pali | how? |
| 08:26.25 | Pali | I want to have one "official" location |
| 08:26.29 | Pali | for all maemo stuff |
| 08:26.35 | Pali | and it is r.m.o domain |
| 08:26.45 | KotCzarny | make the image, put on the internet, google will direct people easily |
| 08:26.46 | Pali | it is "trusted" by all n900 users |
| 08:26.54 | KotCzarny | as most just want 'latest' |
| 08:26.55 | vahe | hi all :) |
| 08:27.58 | Pali | KotCzarny: ask merlin if he can host such firmware on site where is cssu-devel |
| 08:28.27 | Pali | and once we will have location where to host, I could prepare "firmware" file |
| 08:28.49 | KotCzarny | hmm, cssu-thumb might be nice candidate because 'its incompatible with regular stuff' |
| 08:29.09 | Pali | in cssu-devel is prepared new kernel |
| 08:29.14 | KotCzarny | and 'its untested/unstable' |
| 08:29.18 | Pali | with thumb support |
| 08:29.25 | KotCzarny | pali, i know, but if anyone asks why ;) |
| 08:29.29 | Pali | and after testing I would suggest to mark it as stable |
| 08:29.52 | KotCzarny | vahe: hi you |
| 08:30.05 | Pali | because kernel contains also fixes |
| 09:08.38 | *** join/#maemo Arch-TK (Arch-TK@fsf/member/Arch-TK) |
| 09:11.53 | *** join/#maemo Ras_Older (blank@iddqd.fi) |
| 09:15.29 | jonwil | wonders what the minimum set of files required to get a N900 to boot is and how many of those remain closed source' |
| 09:15.54 | jonwil | probably more than I thought (e.g. ICD is necessary) |
| 09:16.05 | KotCzarny | boot is one thing, boot maemo is another |
| 09:16.07 | kerio | to boot what? |
| 09:16.08 | kerio | yea |
| 09:16.14 | KotCzarny | for minimal set see rescueos |
| 09:16.27 | kerio | NOLO is closed i think |
| 09:16.38 | jonwil | yeah it is closed unfortunately :( |
| 09:17.43 | kerio | so |
| 09:17.56 | kerio | that's it really |
| 09:18.11 | kerio | and we can't run uboot directly because nolo does some hardware initialization that we're not aware of |
| 09:21.23 | jonwil | well if we can clone MCE and camera-ui and the various other packages, I am sure we could figure out the important bits of what nolo is doing. If I knew how to get nolo into IDA etc I would take a look myself. |
| 09:22.37 | KotCzarny | nolo is arm binary without any particular format, executed directly by cpu i think |
| 09:23.07 | kerio | well |
| 09:23.19 | kerio | ROMBL probably does stuff |
| 09:23.19 | jonwil | yeah but you need to know where in memory it sits and what's code and what's data and etc which isn't easy |
| 09:23.48 | KotCzarny | if you can get uboot into ida, then nolo is probably few first kbytes from the nand |
| 09:24.23 | KotCzarny | and i guess you will need to know asm well enough |
| 09:25.05 | jonwil | HexRays will help a bit with some of the work if you can get everything lined up properly |
| 09:27.02 | KotCzarny | i wonder if qemu would be able to boot from exact nand dump |
| 09:27.46 | jonwil | probably not since you dont have rombl |
| 09:27.49 | jonwil | and whatever rombl does |
| 09:28.08 | KotCzarny | http://wiki.maemo.org/N900_Hardware_Hacking/serial_dump |
| 09:29.06 | KotCzarny | Über-cool backlight fade-in took 9 ms |
| 09:29.08 | KotCzarny | hehe |
| 09:30.19 | Pali | KotCzarny: qemu implement only GP device (general purpose), not HS (high secure) |
| 09:30.47 | Pali | so qemu ROM cannot parse special header in x-loader where are certificates and RSA keys |
| 09:30.49 | KotCzarny | pali, did someone actually tried installing generic boot loader? |
| 09:31.12 | Pali | KotCzarny: nokia got us x-loader & nolo for GP devices |
| 09:31.18 | Pali | and this is used in qemu! |
| 09:31.40 | kerio | Pali: pls implement nolo in uboot :3 |
| 09:31.53 | Pali | kerio: do it yourself :-) |
| 09:32.07 | kerio | nu :c |
| 09:36.57 | KotCzarny | jonwil: also here: http://wiki.maemo.org/Firmware_hacking |
| 09:39.13 | bencoh | DocScrutinizer05: if you actually do it, please use a CNAME to maemo.muarf.org or whatever *.maemo.muarf.org subdomain, not just "muarf.org" :) |
| 09:40.54 | kerio | the muarf.org home page lists a SHA1 sshfp for a DSS key |
| 09:41.10 | kerio | do two wrongs make a right? |
| 09:41.14 | kerio | or is it just a double wrong |
| 09:41.20 | bencoh | hmmm? |
| 09:41.39 | bencoh | ah you mean sha1 is broken and dss should no longer be used? :D |
| 09:41.41 | kerio | it's also got a CAcert https certificate :\ |
| 09:41.42 | KotCzarny | muarf.org uses an invalid security certificate. |
| 09:41.45 | KotCzarny | The certificate is not trusted because it was signed using a signature algorithm that was disabled because that algorithm is not secure. |
| 09:41.51 | bencoh | I haven't updated it for a long time |
| 09:41.54 | kerio | oh god, a sha1 cert |
| 09:42.23 | kerio | bencoh: letsencrypt? :3 |
| 09:42.31 | bencoh | kerio: no fscking way |
| 09:42.35 | kerio | 3: |
| 09:42.40 | bencoh | not for now at least |
| 09:42.44 | kerio | y not |
| 09:43.03 | bencoh | their "automagic" stuff is .... awful |
| 09:43.12 | kerio | so don't use that client |
| 09:43.16 | kerio | there's plenty of other ACME clients |
| 09:43.35 | bencoh | yeah sure, like I want to let a cron update a file on my server so that they can fetch it - wtf is wrong with them? |
| 09:43.44 | *** join/#maemo xorly (~xorly@213.192.4.202) |
| 09:44.04 | bencoh | 1. I dont like the idea 2. it's http-centric |
| 09:44.11 | bencoh | 3. I dont like automagic stuff |
| 09:44.25 | bencoh | 4. I dont need my cert to change every 3 months |
| 09:47.07 | *** join/#maemo pozitrono (~nu@195-154-169-183.rev.poneytelecom.eu) |
| 09:47.07 | kerio | wut |
| 09:47.48 | KotCzarny | bencoh, still, you should update that cert to something more secure, otherwise there is no point in https/ssh |
| 09:48.24 | jonwil | is bored |
| 09:48.25 | kerio | i mean, dns verification is coming soon, afaik |
| 09:48.28 | jonwil | has run out of N900 stuff to do |
| 09:51.44 | bencoh | <PROTECTED> |
| 09:51.49 | bencoh | according to openssl (?) |
| 09:52.11 | Pali | using non-own CA is unsecure |
| 09:52.12 | kerio | and short-lived certs are a workaround for the unreliable revocation of certs in the TLS PKI |
| 09:52.49 | Pali | just own certificates could be secure by definition |
| 09:52.58 | kerio | secure according to what |
| 09:52.59 | bencoh | Pali: :) |
| 09:53.07 | bencoh | kerio: according to "who can I trust" |
| 09:53.13 | Pali | secure according from client to server connection |
| 09:53.19 | KotCzarny | trust no 1 |
| 09:53.43 | kerio | no authentication |
| 09:53.53 | Pali | if I'm connecting from my mobile to server XYZ, then of course verisign or other CA has nothing to do with connection |
| 09:54.22 | Pali | it is peer-to-peer connection |
| 09:55.02 | kerio | yes, but there's no reasonable way to get your server to be trusted by a majority of clients without using a PKI |
| 10:00.53 | jonwil | Lets see what www.ssllabs.com has to say about maemo.muarf.org :P |
| 10:04.38 | jonwil | it points to a bunch of dangerously weak cyper suites and gives it a fail |
| 10:05.57 | Wizzup | jonwil: and now you have to wonder what maemo actually supports, with an aging openssl |
| 10:06.16 | kerio | *aging NSS |
| 10:06.18 | kerio | but yea |
| 10:06.38 | jonwil | depends whether you are talking SSL for the browser (which is NSS) or SSL for other things like apt-transport-https (which probably uses openssl) |
| 10:07.04 | Wizzup | or wget,curl,ssh :) |
| 10:07.14 | Wizzup | (the latter is not so relevant for http) |
| 10:07.33 | kerio | anyway, openssl 0.9.8 supports a vaguely decent cipher in DHE-RSA-AES256 |
| 10:07.52 | kerio | (or aes128 i guess) |
| 10:08.12 | jonwil | SSH is in extras so its age is less of a factor (its not installed by default and someone could update it to something modern without breaking things) |
| 10:08.24 | kerio | i updated mine to something modern :3 |
| 10:08.48 | kerio | i like me some ed25519 |
| 10:09.10 | *** join/#maemo Tekk_ (~user@cpe-174-106-203-236.ec.res.rr.com) |
| 10:09.10 | jonwil | yeah apt-transport-https does use openssl |
| 10:09.29 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 10:09.35 | kerio | we really ought to start using openssl 1.0.2 for extras |
| 10:10.02 | jonwil | we should ship latest openssl in community-ssu and recompile everything that uses it that is FOSS (or has been cloned) against that version too |
| 10:10.29 | kerio | let's move to libressl instead :> |
| 10:11.46 | jonwil | even better :) |
| 10:12.02 | kerio | i have to run openssl for my tls terminator :< |
| 10:12.28 | kerio | libressl doesn't have SSL_CTX_add_server_custom_ext |
| 10:12.49 | FIQ | file a bug report |
| 10:12.56 | kerio | it's already filed |
| 10:13.19 | FIQ | make a pull request |
| 10:13.34 | Wizzup | kerio: would be good to push out open/libressl and then a recent ssh |
| 10:13.59 | Wizzup | jonwil: +1000 |
| 10:16.27 | bencoh | 12:10 < kerio> let's move to libressl instead :> |
| 10:16.36 | bencoh | and rewrite everything? yeah, sure, good luck :p |
| 10:16.55 | kerio | it's very api-compatible |
| 10:17.05 | jonwil | I am going to go through my on-disk copy of the stock N900 root filesystem, identify everything that links to openssl and make a post about it |
| 10:17.05 | KotCzarny | how very is very? |
| 10:17.11 | jonwil | documenting all the binaries that link to openssl |
| 10:17.19 | jonwil | whether they are open or closed |
| 10:17.21 | jonwil | what package they are in |
| 10:17.23 | kerio | KotCzarny: you could be missing some include or something like that |
| 10:17.35 | jonwil | and if they are closed, what openssl functions they call |
| 10:17.46 | KotCzarny | kerio: is there any distro that uses libressl by default? |
| 10:17.50 | kerio | openbsd |
| 10:18.01 | KotCzarny | and for linux world? |
| 10:18.07 | kerio | linux sucks |
| 10:18.10 | FIQ | yeah but no sane people use openbsd ;) |
| 10:18.39 | KotCzarny | having linux distro patches would ease eventual fixing |
| 10:18.39 | kerio | os x's openssh is statically linked against libressl |
| 10:18.49 | kerio | KotCzarny: oh there's a ton of those actually |
| 10:18.53 | Wizzup | bencoh: libressl works quite well |
| 10:19.02 | kerio | openbsd ports and the like |
| 10:19.03 | Wizzup | bencoh: gentoo has it for most major packages too |
| 10:19.20 | kerio | freebsd ports, too! |
| 10:19.35 | Wizzup | KotCzarny: perhaps alpinelinux uses it, otherwise perhaps voidlinux |
| 10:19.43 | Wizzup | KotCzarny: and for gentoo you can just set USE="libressl" |
| 10:19.52 | *** join/#maemo rm_work (rm_work@Maemo/community/cssu/rm-you) |
| 10:22.21 | jonwil | We dont need to replace every single binary that calls openssl in order to improve security (for example its unlikely to matter so much if something like the ActiveSync/Exchange support is still using weak old OpenSSL 0.9.8 |
| 10:22.59 | FIQ | it does for people who actually use that |
| 10:23.09 | Wizzup | that and you can have both openssl 0.9.8 and libressl installed |
| 10:23.27 | Wizzup | (or openssl 0.9.8 and openssl 1.0.2) |
| 10:26.11 | jonwil | It also depends on exactly which calls in openssl each closed-source binary is making |
| 10:26.40 | jonwil | If its only calling functions to do, say, SHA1 hashing and isn't using any of the actual SSL logic, it probably isn't a security problem. |
| 10:35.32 | Wizzup | It would be great if it could all be switched over to a new libre/openssl though |
| 10:35.50 | Wizzup | If then mainline kernel is managed somehow, you'd have one even more epic system :) |
| 10:37.59 | KotCzarny | then all we would need is thinning/removing apps |
| 10:38.16 | KotCzarny | having 128M of ram free would make it usable |
| 10:38.36 | freemangordon | jonwil: what were those 2 functions that were waiting to be REed in devicelock? |
| 10:38.57 | freemangordon | and could I have your IDA DB, to not reinvent the wheel |
| 10:39.33 | jonwil | its libcodelockui that needs work done |
| 10:39.54 | freemangordon | ok, whatever it is, just hand me the DB :) |
| 10:40.42 | jonwil | I believe I gave you my latest IDB before |
| 10:40.53 | jonwil | but yeah let me get it anyway |
| 10:41.22 | jonwil | the missing ones should be marked with todo in the code IIRC |
| 10:41.49 | jonwil | https://drive.google.com/file/d/0B9idqO9KygGsdXltRVBEYWtUQmM/view?usp=sharing |
| 10:41.51 | jonwil | latest db |
| 10:42.14 | freemangordon | ok, thanks |
| 10:43.44 | xes | coderus seems gone ..next time time i hope he would provide real ip while asking for a check of the ban.. |
| 10:43.49 | freemangordon | jonwil: wht is the "todo mark", 'z' at the beginning of the name? |
| 10:44.13 | jonwil | cant remember off the top of my head |
| 10:44.24 | freemangordon | ok, will check against the source code |
| 10:45.24 | *** join/#maemo futpib (~futpib@176.212.185.96) |
| 10:46.53 | KotCzarny | xes, most of those people are from shared ips with reported spammers anyway |
| 10:47.27 | KotCzarny | xes, maybe you should add info about it too, and probably link to google in form: http://google.com/?q=$ip |
| 10:53.37 | xes | KotCzarny: yes, i know. I want give support explaining and checking. ..But that ip isn't banned and never asked for a TMO page |
| 10:54.06 | KotCzarny | xes, i think you can do /whowas coderus and use that one |
| 10:54.14 | KotCzarny | or just reply to his mail |
| 10:57.33 | xes | in fact, coderus is logged in TMO now... |
| 11:03.03 | KotCzarny | so, either a spammer or clueless user |
| 11:03.11 | ceene | jonwil: maybe a priority regarding ssl is QT itself |
| 11:03.18 | KotCzarny | - coderus is ~coderus@static.88-198-208-108.clients.your-server.de (backdoor) |
| 11:03.35 | jonwil | QT is open source so its easy to fix |
| 11:03.36 | KotCzarny | nice 'realname' |
| 11:03.45 | ceene | i know for a fact that by default it tries to use unsecure algos |
| 11:04.02 | *** join/#maemo KotCzarny (ariel@31.135.195.239) |
| 11:04.11 | jonwil | I am concerned about the closed source bits so we know what might be worthwhile targets for cloning |
| 11:04.24 | ceene | on yappari i had to forbid it from using ssl3 beause the servers were rejecting that kind of connection |
| 11:05.09 | ceene | i guess that gtk/qt will make the majority of ssl users |
| 11:05.42 | ceene | but certain closed sources could use openssl by themselves, that's true |
| 11:07.42 | KotCzarny | wow, maemo.sexy domain is free to register |
| 11:07.58 | ceene | lol |
| 11:07.58 | KotCzarny | is.my.maemo.sexy ;) |
| 11:08.53 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 11:12.21 | *** join/#maemo louis_ (~louisdk@static-5-103-130-65.seas-nve.net) |
| 11:47.45 | jonwil | http://talk.maemo.org/showthread.php?p=1492735#post1492735 |
| 11:50.04 | jonwil | So there are a total of 9 binaries that are closed source and call openssl functions |
| 11:50.43 | KotCzarny | how did you make that list? ldd? |
| 11:51.04 | jonwil | no |
| 11:51.23 | jonwil | I have a local copy of a stock untouched (e.g. no optification) root filesystem on my disk |
| 11:51.32 | jonwil | I searched that for everything that linked to libssl and libcrypto |
| 11:51.47 | *** join/#maemo Halftux (~Halftux@i577B67AF.versanet.de) |
| 11:51.55 | KotCzarny | but how did you actually test if package links to libssl |
| 11:53.24 | jonwil | Its easy enough to tell by searching for the right strings (i.e. libssl.so and libcrypto.so) |
| 11:54.00 | jonwil | So then I matched each of those binaries (the ones referencing libsso and libcrypto in their strings) to a package |
| 11:54.08 | jonwil | and then for the closed source ones I dumped a list of symbols |
| 11:54.13 | jonwil | list of imported symbols |
| 11:54.25 | jonwil | and compared it to the list of symbols exported from libssl/libcrypto |
| 11:54.25 | KotCzarny | uhum |
| 11:54.50 | jonwil | trust me when I say that the info in the forum thread is accurate and complete |
| 11:54.51 | Wizzup | Use ldd? |
| 11:55.04 | Wizzup | Ah |
| 11:55.06 | Wizzup | Sorry. Didn't read up. |
| 11:55.29 | kerio | jonwil: is that only for the default rootfs, though? |
| 11:55.36 | jonwil | yes only for the stock rootfs |
| 11:55.48 | jonwil | I dont see anywhere else where there are closed source binaries that need examination |
| 11:56.34 | kerio | idk, the nokia repo |
| 12:01.42 | Pali | jonwil: can you look at http://talk.maemo.org/showpost.php?p=1491455&postcount=476 ? |
| 12:02.43 | jonwil | I tried to find where nokia debugging messages come from but was unable to properly reverse engineer the relavent bits (my clone does the same job as stock but it does it in a different way) |
| 12:03.08 | Pali | just add them into your clone |
| 12:03.30 | Pali | run binary and copy strings (if you do not know from where comes from) |
| 12:03.36 | Pali | this should be easy |
| 12:05.57 | *** join/#maemo geaaru (~geaaru@95.237.228.205) |
| 12:06.46 | *** join/#maemo rm_work (~rm_work@Maemo/community/cssu/rm-you) |
| 12:09.22 | Halftux | Pali you still need this available-notifications file? |
| 12:16.37 | jonwil | ok, so I checked the list of packages that http://mirrors.muarf.org/maemo/apt-mirror/mirror/downloads.maemo.nokia.com/fremantle/ssu/mr0/ (nokia repo) says it provides against the list of packages installed on the root filesystem image I have |
| 12:17.01 | jonwil | Then for the ones on the repo but not the root FS I checked if they were in the SDK repo as source |
| 12:17.21 | jonwil | and for the few that aren't FOSS, they aren't using OpenSSL (I checked) |
| 12:17.25 | Pali | Halftux: of course :-) |
| 12:18.04 | jonwil | so http://talk.maemo.org/showthread.php?p=1492735#post1492735 contains the complete list of all the closed-source things talking to openssl unless there is a repo somewhere I dont know about |
| 12:19.48 | jonwil | and we now have enough information (hopefully) to evaluate each of those closed binaries and figure out what the security risks might be going forward if those binaries continue to talk to openssl 0.9.8 |
| 12:22.22 | jonwil | hmmm, I never knew modest used microb-engine... |
| 12:22.52 | KotCzarny | almost everything in maemo uses microb engine |
| 12:23.01 | KotCzarny | at least if there is html involved in app |
| 12:23.07 | jonwil | yeah :) |
| 12:25.48 | Halftux | Pali: I had a look at my phone which had ota updates from Nokia. But the file was not there. Then the yellow update notification pops up and a file available-notifications.tmp was created. I think when the blinking stops the file disappears. After ignoring the updates a seen-updates file was created. Don't know if the temp file is of any help sadly I was to slow to copy it. |
| 12:28.13 | jonwil | The good news is that everything talking to NSS seems to be FOSS |
| 12:28.38 | jonwil | microb-engine and bits of modest being the main ones |
| 12:29.03 | jonwil | so it should be possible to replace NSS with something newer (and make any necessary changes in microb-engine etc) easily enough |
| 12:29.54 | Wizzup | I guess it's very hard to port microb engine to use newer firefox engines |
| 12:30.01 | jonwil | yes it is |
| 12:30.27 | jonwil | for a bunch of reasons including Flash |
| 12:31.01 | jonwil | but updating NSS and the security sensitive stuff should be possible without breaking things |
| 12:31.29 | bencoh | modest depends on NSS? |
| 12:31.36 | xes | Flash? Who is so mad to use it? |
| 12:31.39 | jonwil | yes it does |
| 12:31.42 | bencoh | oh and, seriously, flash... |
| 12:32.32 | bencoh | I'm sure most of us would be happy to trade a flash-enabled browser with a real "fast" html5-compatible browser |
| 12:32.42 | Pali | Halftux: .tmp file is created and HAM try to download new version to it from nokia server (which is down) |
| 12:33.39 | Wizzup | jonwil: I think gnash does better flash than the maemo flash :) |
| 12:35.50 | jonwil | Fennec probably has just as many security issues as microb but since its not an official part of the system (not even sure where it comes from) its not within the scope of CSSU |
| 12:35.58 | Halftux | Pali: ok I see |
| 12:36.01 | jonwil | and therefore CSSU people dont need to care about fixing it |
| 12:37.43 | jonwil | main thing is, we have target list for closed source binaries that may present security risk if not moved to newer openssl |
| 12:39.42 | Wizzup | :) |
| 12:44.02 | bencoh | hmm, looks like curl on maemo doesnt make any use of tlsv1 (?) |
| 12:44.45 | bencoh | error SSL routines:SSL23_GET_SERVER_HELLO ... |
| 13:04.37 | *** join/#maemo Fulltux (~Halftux@i577B46A2.versanet.de) |
| 13:06.03 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 13:11.36 | jonwil | would be good to see security improvements for Maemo |
| 13:12.10 | jonwil | but its a matter of finding people who understand the libraries and code involved (openssl, libcurl, microb, nss etc) |
| 13:12.36 | KotCzarny | in case of libressl it could be as simple as recompiling |
| 13:12.50 | jonwil | for the things that are FOSS yes |
| 13:12.53 | KotCzarny | (and source available) |
| 13:13.10 | jonwil | but for the closed source things we need to figure out which ones are using openssl in a way that matters for security |
| 13:13.49 | jonwil | also we need to deal with how certain things use openssl (e.g. lubcurl and libqt4-network) to make sure they use it in a way that is secure |
| 13:14.08 | jonwil | i.e. selecting the right algorithms and stuff and not claiming to support the old insecure stuff |
| 13:14.50 | *** join/#maemo vahe (~funtoo@130.193.124.135) |
| 13:17.09 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 13:17.47 | bencoh | is libcurl part of the stock system? |
| 13:18.00 | jonwil | yes it is |
| 13:18.43 | bencoh | ah. |
| 13:19.50 | jonwil | its used by (among other things) apt-transport-https |
| 13:19.57 | jonwil | and nokia maps |
| 13:20.08 | jonwil | and flash |
| 13:20.29 | jonwil | and activysync daemon |
| 13:20.35 | jonwil | activesync |
| 13:21.08 | bencoh | hmm |
| 13:21.40 | jonwil | hmm what? |
| 13:22.06 | bencoh | then we need to either patch it to use the tlsv1 function or try to pull a recent version from upstream |
| 13:22.21 | bencoh | first option is probably the easiest one |
| 13:22.33 | *** join/#maemo Vajb (~Vajb@85-76-85-86-nat.elisa-mobile.fi) |
| 13:23.39 | jonwil | yeah once we have newer openssl/libressl we need to fix up libcurl so that it makes the right calls to openssl to do all the correct security stuff (and none of the stuff we dont want like sslv3) |
| 13:27.15 | bencoh | we dont even need to upgrade for that |
| 13:27.29 | bencoh | (ssl*_ |
| 13:40.30 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 13:51.13 | merlin1991 | iirc curl in cssu is "newer" and should behave better |
| 13:51.36 | jonwil | we do, we dont just want TLS1.0 we want whatever the latest TLS standard is |
| 13:51.39 | jonwil | TLSv2 or whatever it is |
| 13:51.56 | bencoh | merlin1991: in -testing maybe |
| 13:52.03 | bencoh | (-testing/-devel) |
| 13:52.04 | merlin1991 | bencoh: yep |
| 13:52.08 | merlin1991 | (testing) |
| 13:52.14 | merlin1991 | iirc luf did that |
| 13:52.28 | bencoh | luf? |
| 13:54.16 | merlin1991 | hm stable also has curl 7.26 |
| 13:58.41 | bencoh | yeah, that's what I have here as well |
| 13:59.41 | *** join/#maemo hashcore (~hashcore@unaffiliated/hashcore) |
| 14:12.45 | *** join/#maemo FlameReaper-PC (~FR@tin-206-250.tm.net.my) |
| 14:15.51 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 14:31.15 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 14:50.47 | ceene | qt4 doesn't support tlsv1.2 i think |
| 14:50.56 | ceene | or at least it needs openssl 1.0.1 |
| 14:51.01 | ceene | so... |
| 14:51.11 | ceene | sometime in the future we may be not even able to access https sites? |
| 14:53.34 | jonwil | depends what browser you are using |
| 14:53.38 | jonwil | microb needs nss updated |
| 14:54.00 | ceene | i was trying to get at why getmewheels wasn't working |
| 14:54.05 | jonwil | fennec is likely using its own copy of NSS (although by all accounts there are builds of Fennec for the N900 that are a fair bit newer than microb) |
| 14:54.07 | ceene | and it's because car2go site uses tlsv1.2 |
| 14:54.19 | ceene | getmewheels an interface to an http based api |
| 14:54.28 | ceene | so... this application is now useless |
| 14:55.20 | jonwil | its not useless, it just needs someone to bring newer OpenSSL to Maemo then someone to fix QT to use the new OpenSSL and pick the best/most secure/etc settings |
| 14:55.44 | ceene | i don't think it's going to be very easy, isn't it? |
| 14:56.14 | jonwil | it probably wont be as hard as it looks... |
| 14:57.18 | Sicelo | sorry to go back to 'old' news ... i don't understand the significance of the file Pali was working on for HAM. we've been getting updates without it. what is it important for? |
| 14:57.26 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 14:58.18 | Pali | Sicelo: update for stock n900 devices |
| 14:58.48 | Pali | not apt update, just pop-up note with URL link |
| 15:01.01 | *** join/#maemo louis_ (~louisdk@0155800528.0.fullrate.dk) |
| 15:02.24 | jonwil | ok, zzz time |
| 15:02.27 | jonwil | cya later :) |
| 15:02.28 | KotCzarny | sicelo: it was to notify users that dont know about t.m.o or w.m.o or cssu that there is something they can install |
| 15:03.45 | KotCzarny | pali, but if the sources for ham are available, maybe its just as simple as pushing updated ham into extras? |
| 15:04.26 | Pali | KotCzarny: no, HAM does not allow updates for NokiaSSU packages which are not from NokiaSSU repo |
| 15:04.34 | Pali | it has special pinning in HAM for it |
| 15:04.42 | KotCzarny | uhum |
| 15:04.45 | Pali | reason why we need to patch everything in CSSU |
| 15:04.58 | Pali | CSSU installer adds new repo with higher priority |
| 15:05.13 | Pali | and so this repo can update packages also from NokiaSSU repo |
| 15:05.36 | Pali | it is security framework, something like in harmattan, but fully open and configurable |
| 15:05.42 | KotCzarny | btw. if m$ ever decides to revive nssu repos and push rogue things there to install bugs, will they succeed? |
| 15:18.51 | Sicelo | why would they do that? |
| 15:19.14 | Sicelo | thanks for explanation by the way :) |
| 15:19.24 | KotCzarny | sicelo, because evil people often do evil things |
| 15:19.57 | *** join/#maemo guest123 (2e3ba145@gateway/web/freenode/ip.46.59.161.69) |
| 15:20.23 | guest123 | there also is http://maemo-repos.com/apt-mirror/ |
| 15:20.26 | guest123 | http://talk.maemo.org/showthread.php?t=95870 |
| 15:20.33 | *** part/#maemo guest123 (2e3ba145@gateway/web/freenode/ip.46.59.161.69) |
| 15:20.45 | KotCzarny | wtf was that? |
| 15:21.17 | sixwheeledbeast | Singapore calling... |
| 15:36.43 | *** join/#maemo vahe (~funtoo@130.193.124.135) |
| 15:57.20 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 16:02.04 | *** join/#maemo krnlyng (~liar@77.117.79.42.wireless.dyn.drei.com) |
| 16:03.57 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 16:04.51 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 16:06.08 | M-bobsummerwill | DocScrutinizer05 and infobot: Thanks! Will do that when my N900 arrives. |
| 16:07.42 | KotCzarny | infobot is a bot |
| 16:07.52 | KotCzarny | infobot: botsnack |
| 16:07.52 | infobot | aw, gee, KotCzarny |
| 16:08.00 | Wizzup | aw, gee, KotCzarny |
| 16:08.04 | M-bobsummerwill | Doesn't mean I can't say thanks :-) |
| 16:08.08 | KotCzarny | wizzup: rollover |
| 16:08.18 | Wizzup | \o/ |
| 16:08.19 | KotCzarny | bob: sure, why not |
| 16:08.38 | M-bobsummerwill | :-P |
| 16:11.03 | *** join/#maemo FReaper-PC (~FR@110.159.98.219) |
| 16:12.02 | *** join/#maemo heroux (sandroco@gateway/shell/insomnia247/x-uxudofztfoqpcujf) |
| 16:16.22 | M-bobsummerwill | Luke-jr: It sounds like you've already made up your mind about Ethereum, but for everybody else's benefit, let me reply. |
| 16:16.23 | M-bobsummerwill | In summary, Bitcoin introduced two new innovations at the same time: |
| 16:16.24 | M-bobsummerwill | Block-chain. Decentralized open ledger, consensus mechanism. |
| 16:16.25 | M-bobsummerwill | Crypto-currency built on top of that block-chain. |
| 16:16.25 | M-bobsummerwill | Great stuff. However, the "VM" for the Bitcoin block-chain was designed only for that single purpose. You can transfer crypto-currency excellently, but using it as a consensus mechanism for other purposes is hard. You see a bunch of other "Bitcoin 2.0" projects coming into existence which are piggy-backing on the Bitcoin block-chain for things like land registry, digital assets, insurance, etc. The problem they |
| 16:16.26 | M-bobsummerwill | all have is that the Bitcoin block-chain really wasn't designed for that. |
| 16:16.50 | M-bobsummerwill | Ethereum block-chain is Turing-complete, so you can build anything on it. |
| 16:17.34 | M-bobsummerwill | Now of course, it's not at all intended as a replacement for local CPUs. That would be insane. It's probably trillions of times slower. Obviously. |
| 16:18.05 | M-bobsummerwill | It's just intended for consensus |
| 16:18.15 | M-bobsummerwill | Accounts. Who owns A, B, C. |
| 16:19.24 | M-bobsummerwill | And then the "new stuff" over Bitcoin is that you can build (simple) behaviours on top. AKA - "smart contracts", which are self-executing. Like our friend "infobot" |
| 16:19.40 | M-bobsummerwill | ie. If Condition A then pay money to account B. |
| 16:19.42 | M-bobsummerwill | Escrow |
| 16:19.44 | M-bobsummerwill | Insurance |
| 16:19.47 | M-bobsummerwill | Shares |
| 16:19.58 | M-bobsummerwill | Voting mechanisms |
| 16:20.00 | M-bobsummerwill | blah blah blah |
| 16:20.48 | M-bobsummerwill | But all just on the Ethereum block-chain using the basic functionality of the system, rather than wedged into the Bitcoin block-chain with a crow-bar and external systems. |
| 16:20.56 | M-bobsummerwill | That's about it. |
| 16:20.58 | M-bobsummerwill | http://devcon.ethereum.org |
| 16:21.12 | M-bobsummerwill | Not a shitcoin. It' |
| 16:21.18 | M-bobsummerwill | It's a technology |
| 16:21.41 | M-bobsummerwill | You have a real absence of the speculators in Ethereum. It's all technologists. |
| 16:38.10 | *** join/#maemo Vajb (~Vajb@85-76-39-113-nat.elisa-mobile.fi) |
| 16:49.36 | *** join/#maemo louisdk (~louisdk@80-62-117-93-mobile.dk.customer.tdc.net) |
| 17:02.28 | *** join/#maemo realitygaps (~realityga@2a01:4a0:3::5096:aeb) |
| 17:02.28 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 17:16.36 | Luke-Jr | M-bobsummerwill: lol |
| 17:17.14 | Luke-Jr | M-bobsummerwill: maybe if any of the people working on Ethereum ever did Bitcoin development, they would have realised Bitcoin already does basically everything useful that Ethereum aims to do |
| 17:25.16 | *** join/#maemo realitygaps (~realityga@2a01:4a0:3::5096:aeb) |
| 17:25.16 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 17:40.40 | *** join/#maemo sq-one (~sq-one@HSI-KBW-5-56-236-246.hsi17.kabel-badenwuerttemberg.de) |
| 17:44.25 | *** join/#maemo Vajb (~Vajb@85.76.4.43) |
| 17:45.35 | *** join/#maemo eMHa (~mh@p579DB9BE.dip0.t-ipconnect.de) |
| 18:04.00 | *** join/#maemo sparetire_ (~sparetire@unaffiliated/sparetire) |
| 18:05.04 | *** join/#maemo LjL^ (~ljl@unaffiliated/ljl) |
| 18:11.10 | M-bobsummerwill | Luke-jr: I don't know quite why you are being so aggressive and religious here. Vitalik Buterin, the creator of Ethereum, co-founded Bitcoin magazine in 2011, and is no crypto-dummy. It must be delightful for you to have such utterly certainly in your own opinions that you can discard the efforts of thousands of people to advance the state of technology. Also, delightful that there is "one true way". |
| 18:18.25 | Wizzup | -> private messages? |
| 18:19.44 | M-bobsummerwill | Or "let's agree to disagree", I think. |
| 18:20.25 | M-bobsummerwill | Anyway ... I'll get going with my N900 development as-and-when. Best wishes, everyone! |
| 18:24.17 | *** join/#maemo Vajb (~Vajb@85.76.138.73) |
| 18:39.22 | xes | what is this? Advertising channel? |
| 18:40.17 | APic | What does it look like? |
| 18:41.12 | KotCzarny | looks like proud software dev overdefending his work |
| 18:41.28 | xes | an advertising monologue? |
| 18:41.36 | KotCzarny | + backlock reading |
| 18:41.40 | KotCzarny | *backlog |
| 18:49.03 | *** join/#maemo eMHa (~mh@p579DB9BE.dip0.t-ipconnect.de) |
| 18:56.31 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 19:04.20 | *** join/#maemo trumee (~trumee@c-50-175-121-86.hsd1.tx.comcast.net) |
| 19:24.56 | useretail | hey everyone, i had power kernel and decided to return back to stock, so i launched Nokia kernel from menu and restored stock kernel (got successful message) after that removed power kernel settings package. but after reboot device went to reboot loop: nokia logo screen with usb icon appears on pale screen. after that black screen lights up and after few seconds reboots. any suggestions? |
| 19:26.40 | *** join/#maemo thuttu77 (~thuttu77@82-181-33-81.bb.dnainternet.fi) |
| 19:29.28 | freemangordon | useretail: it might be that kernel could not find its modules, try to flash kernel-power again, by using the flasher |
| 19:33.23 | useretail | freemangordon: ok, so what do i need to flash exactly? looks like i had that problem some time ago. i have uImage-2.6.28.10-power52 and zImage-2.6.28.10-power52 images |
| 19:37.17 | freemangordon | useretail: maybe first try to use zImage, and tell the flasher to only boot that kernel |
| 19:37.25 | freemangordon | then you can flash wuth uImage |
| 19:37.31 | freemangordon | *with |
| 19:46.21 | KotCzarny | or just try to use flasher to BOOT without flashing |
| 19:46.31 | KotCzarny | right. |
| 19:46.51 | useretail | KotCzarny: how? i can't get it stop rebooting |
| 19:47.16 | freemangordon | KotCzarny: please help him, as I don;t have time now |
| 19:47.32 | *** join/#maemo eMHa (~mh@p579DB9BE.dip0.t-ipconnect.de) |
| 19:51.39 | KotCzarny | useretail, grab the kernel power image package on pc, unpack it |
| 19:52.12 | useretail | KotCzarny: yeah, i have done that already |
| 19:52.46 | KotCzarny | flasher-3.5 -k kernelimgfile -l |
| 19:54.23 | KotCzarny | there is also -b param to set default cmdline for kernel |
| 19:55.04 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 19:55.54 | KotCzarny | By using the "-l" option, we do not flash the kernel or initrd image. |
| 19:56.06 | KotCzarny | It only loads the kernel into RAM. No modification on the NAND or bootloader happens. |
| 19:56.30 | KotCzarny | 0xFFFF also can load kernel |
| 19:56.42 | KotCzarny | 0xFFFF -m kernelfile -l |
| 19:57.19 | KotCzarny | i assume you know how and when to connect n900 |
| 19:57.45 | KotCzarny | if not, run flasher/0xffff command first, then connect (powered off) n900 via usb cable to computer |
| 20:05.14 | useretail | ok, flashed the kernel. but it still doesn't boot and more importantly doesnt charge from wall charger |
| 20:08.22 | KotCzarny | did you use -l ? |
| 20:08.47 | KotCzarny | -l mean to 'load/boot only' not actual flashing |
| 20:09.09 | useretail | well i actually flashed: flasher-3.5 -k zImage-2.6.28.10-power52 --flash-only=kernel -f -R |
| 20:09.16 | KotCzarny | eh |
| 20:09.32 | KotCzarny | anyway, you can still try to boot |
| 20:09.49 | KotCzarny | as n900 is unkillable by flasher-3.5 |
| 20:10.30 | useretail | ok, how to extract and flash default stock nokia kernel only? |
| 20:10.40 | KotCzarny | but are you sure power52 was your kernel? |
| 20:10.46 | KotCzarny | i think most recent is 54 |
| 20:10.50 | useretail | yeah, absolutely |
| 20:11.10 | freemangordon | useretail: use rootfs image and tell the flasher to flash kernel only |
| 20:11.42 | KotCzarny | fmg, but if he is missing modules as you suspected it wont help at all |
| 20:12.00 | KotCzarny | useretail, you can also boot rescueos |
| 20:12.18 | KotCzarny | and check which modules dirs you have under /lib/modules/ |
| 20:12.26 | freemangordon | KotCzarny: but there should be at least *some* modules |
| 20:12.26 | KotCzarny | also, it can charge the battery |
| 20:12.42 | freemangordon | yeah, rescueos might help |
| 20:13.03 | KotCzarny | but beware, if you discharge battery too much, you wont be able to boot anything |
| 20:13.29 | KotCzarny | (unless you have second device in which you can recharge it) |
| 20:17.52 | useretail | ok, booted rescueos. how to run charger script? |
| 20:18.11 | freemangordon | ~rescueos |
| 20:18.12 | infobot | somebody said rescueos was http://n900.quitesimple.org/rescueOS/ |
| 20:18.35 | freemangordon | useretail: https://n900.quitesimple.org/rescueOS/rescueOS-1.2/documentation.txt |
| 20:18.48 | freemangordon | "/rescueOS/charge21.bash" |
| 20:21.20 | freemangordon | useretail: mount maemo rootfs and check what is in /lib/modules |
| 20:22.33 | freemangordon | then either flash the correct kernel (if there is anything in /lib/modules) or copy the needed debs to the device, chroot to maemo and install them |
| 20:23.38 | *** join/#maemo eijk (~eijk@x55b2ca7a.dyn.telefonica.de) |
| 20:31.51 | *** join/#maemo FlameReaper-PC (~FR@115.132.88.188) |
| 20:34.32 | useretail | there are: 2.6.28-omap1 2.6.28.10-bfs10 2.6.28.10-power53 current |
| 20:34.48 | useretail | how to detect which ones are in current? |
| 20:35.20 | useretail | ok figured out |
| 20:40.00 | freemangordon | useretail: are there any files in 2.6.28-omap1? |
| 20:42.31 | useretail | freemangordon: one moment. i rebooted to see if flashing power53 will boot device |
| 20:43.34 | freemangordon | ok |
| 20:47.05 | useretail | yeah, it worked. |
| 20:47.12 | KotCzarny | yeah. 52 for sure? |
| 20:47.20 | useretail | no, 53 |
| 20:47.28 | KotCzarny | > but are you sure power52 was your kernel? |
| 20:47.30 | KotCzarny | <useretail> yeah, absolutely |
| 20:47.33 | useretail | lol |
| 20:47.40 | useretail | i was wrong |
| 20:48.08 | useretail | i guess |
| 20:48.21 | KotCzarny | now update to 54 and be happy |
| 20:48.38 | KotCzarny | or go cssu |
| 20:51.09 | freemangordon | :) |
| 20:51.17 | useretail | while upgrading i ran out of free space on rootfs, so i cancelled kernel upgrade. after that was struggling to remove some stuff to freeup some space, than decided to remove power kernel and go back to stock, than that |
| 20:51.35 | KotCzarny | :) |
| 20:51.40 | useretail | geez |
| 20:51.57 | KotCzarny | if you are cautious you can move some things from / to /opt and symlinking back |
| 20:52.16 | useretail | enough experiments for today |
| 20:52.35 | useretail | i need to work tomorrow |
| 20:53.17 | useretail | thanks for the help guys |
| 20:53.27 | useretail | cya around |
| 20:53.39 | useretail | off to bed |
| 21:05.28 | DocScrutinizer05 | hhhh, ubi0:rootfs 228M 184M 40M 83% / |
| 21:05.38 | DocScrutinizer05 | hmmm even |
| 21:40.01 | *** join/#maemo darkschneider (~gab@93-32-51-166.ip32.fastwebnet.it) |
| 22:22.53 | timeless | hello world |
| 22:24.23 | *** join/#maemo Tekk_` (~user@cpe-174-106-203-236.ec.res.rr.com) |
| 22:29.33 | *** join/#maemo Maxdamantus[R] (~max@122.56.196.63) |
| 22:31.14 | *** join/#maemo Kilroo (~Kilroo@98.27.26.236) |
| 22:57.34 | *** join/#maemo andril (~andril@c-66-229-28-40.hsd1.fl.comcast.net) |
| 23:00.37 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 23:01.58 | jonwil | pali: ping |
| 23:05.04 | *** join/#maemo Tekk_ (~user@cpe-174-106-203-236.ec.res.rr.com) |
| 23:05.22 | *** part/#maemo Tekk_ (~user@cpe-174-106-203-236.ec.res.rr.com) |
| 23:06.25 | *** join/#maemo pozitron (nu@gateway/vpn/mullvad/x-cpifcoipysmptype) |
| 23:06.48 | *** join/#maemo g3kk3r (~torrkull@far.torrkulla.net) |
| 23:12.33 | *** join/#maemo Maxdamantus[R] (~max@122.56.196.63) |