IRC log for #maemo-ssu on 20130122

01:57.27*** join/#maemo-ssu X-Fade (~xfade@d5152FFD8.static.telenet.be)
03:27.41*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
03:39.08*** join/#maemo-ssu X-Fade (~xfade@d5152FFD8.static.telenet.be)
04:04.20*** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg)
04:43.39*** join/#maemo-ssu ShadowJK (jk@terminus.enivax.net)
05:14.44*** join/#maemo-ssu thedead1440 (~thedead14@216.244.71.133)
05:15.07*** join/#maemo-ssu jon_y (~enforcer@2002:af8e:231f::af8e:231f)
05:15.59DocScrutinizer05anybody already got my forwarded mail?
05:17.04DocScrutinizer05subject "N900 repo GPG key renewal issue"
05:17.50thedead1440DocScrutinizer05: i received your email
05:17.59DocScrutinizer05fine :-)
05:18.12DocScrutinizer05do you think we (community) can help?
05:18.27DocScrutinizer05in the end we'd help ourselves
05:19.39thedead1440i think the devs here can have a version of CSSU-Security which adds a Security repo on users N900s and that repo is only used in the event of any security updates. This can be communicated to Nokia's representative and would be a good opportunity to get some further sponsorship from Nokia; it would be a 1-for-1 kind of exchange ;)
05:20.15DocScrutinizer05also please keep in mind boards most recent call to mention to then everything HiFo needs to ask Nokia for handing control over to HiFo, to allow sustainable maintenance of maemo infra at large
05:21.47DocScrutinizer05thedead1440: brilliant approach (hehe, I think I know who contributed some aspects ;-D) - I suggest to exploit wiki to draft a concept in cooperation of you experts
05:23.01thedead1440DocScrutinizer05: you want me to put a "proposal to fix expired keys" page on wiki? I thought you didn't want the email on the ML so that it doesn't spread? Oh and yes your ideas ;)
05:23.21DocScrutinizer05it's kinda waste of time if all 20 I BCCed would draft their own version of "Repo 101" as an introduction to how repo security works, then append their own idea of options we/Nokia have
05:24.24thedead1440ok in that case I'll start off a wiki page and everyone can put in their suggestions; ultimately its the developers here who will have to decide
05:24.43DocScrutinizer05thedead1440: yep, I suggest a wiki page "Repositories: basics of operation, security, current issues, options for solutions"
05:25.30thedead1440https://wiki.maemo.org/Repositories is unused; maybe this can be the meta page with sub-sections
05:25.40DocScrutinizer05good idea
05:25.59DocScrutinizer05start with one long page, split into subpages when needed
05:27.40DocScrutinizer05thedead1440: please make that wiki.maemo.org/fremantle/Repositories though
05:27.46thedead1440ok
05:28.09DocScrutinizer05since e.g. for HARM the situation is quite different afaik
05:28.50DocScrutinizer05~seen freemangordon
05:28.53infobotfreemangordon <~freemango@130-204-50-168.2074221835.ddns.cablebg.net> was last seen on IRC in channel #maemo, 4h 59m 51s ago, saying: ':nod:'.
05:29.03DocScrutinizer05~seen pali
05:29.03infobotpali <~pali@Maemo/community/contributor/Pali> was last seen on IRC in channel #maemo, 1d 18h 33m 53s ago, saying: 'repository Flash?'.
05:30.18DocScrutinizer05anybody around with thorough expertise regarding repository management that I missed to send the mail to? Please holler
05:50.12thedead1440DocScrutinizer05: the issue and proposed solution 1 have been added to http://wiki.maemo.org/Fremantle/Repositories ; basics of operations I think someone with better knowledge of things adds
07:21.57*** join/#maemo-ssu freemangordon (~freemango@130.204.50.168)
07:25.27freemangordonDocScrutinizer05: I think it is Pali who can give the idea on what could be done re GPG key. IIRC he said that in theory that key validity could be extended
07:26.39DocScrutinizer05freemangordon: that would be best option, if the key validity is on server side and not encoded into key on device
07:27.09freemangordonyep
07:27.50freemangordonafaik so far we were in the same situation with repos on maemo.org, 1-2 years ago
07:27.59DocScrutinizer05freemangordon: first we need a concise but comprehensive explanation how stuff *works*, on that wiki page. Not even I have a clear idea of how gear works together
07:28.06freemangordonit was nokia to change something to fix it
07:28.17freemangordonme neither :D
07:28.56DocScrutinizer05hopes for pali and merlin1991 and woody to step up and contribute a "repo for dummies"
07:29.32DocScrutinizer05also X-Fade and javispedro, though I'm woefully missing the latter since months
07:29.42DocScrutinizer05actually missing both
07:30.09*** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au)
07:31.26DocScrutinizer05anyway please proactively further discussion and ping those who might have knowledge to contribute but possibly even didn't get BCCed on that mail
07:31.31*** join/#maemo-ssu sunkan (sunkan@alva.zappa.cx)
07:32.00freemangordonhmm, gregoa is our debian expert afaik, he might have some idea :)
07:32.15DocScrutinizer05we can demonstrate to Nokia we're worth it here ;-D
07:32.31freemangordonare we? :D:D:D
07:33.22jonwilreads logs to find out whats being discussed :)
07:33.24DocScrutinizer05so please keep the discussion floating
07:33.55freemangordonjonwil: Nokia needs our help to replace the expired apt key
07:34.06freemangordonDocScrutinizer05: correct?
07:34.15DocScrutinizer05kinda, aiui
07:37.27DocScrutinizer05freemangordon: will you fw the mail to whomever it may concern please?
07:37.37jonwilI intend to get back to looking at the N900 GPRS stuff soon btw (I was in the middle of reverse engineering csd-gprs when my computer failed suddenly, I only got it back from the repair guy yesterday and now I have to do a backup of important stuff before I move on)
07:38.01DocScrutinizer05freemangordon: not indiscriminately though
07:38.06DocScrutinizer05;-)
07:38.32freemangordonDocScrutinizer05: I can't think of anyone outside the guys here who can help
07:38.35DocScrutinizer05I'd like to stay PC here
07:38.56DocScrutinizer05sure, but I didn't have mail addr of all of "the guys here"
07:40.10freemangordonbug 11384
07:40.28freemangordonis she alive?
07:40.34DocScrutinizer05actually I had 9 addr
07:40.36keriothe validity of the key *is* stored on the device
07:40.41kerioand can't be changed
07:41.02freemangordonkerio: aiui repo acts as a keyserver
07:41.06kerioit's set in the first packet of the key, together with loads of things
07:41.11kerioit doesn't, surely
07:41.20keriowe can push more keys
07:41.36keriobut the current keys are stored in /var/lib/apt/trusted.gpg
07:41.51*** join/#maemo-ssu povbot_ (~supybot@office.pov.lt)
07:41.51*** mode/#maemo-ssu [+v povbot_] by ChanServ
07:42.02kerioand/or the files in /usr/share/HAM/keys
07:42.05DocScrutinizer05omfg
07:42.13DocScrutinizer05povbot spawns
07:42.43*** join/#maemo-ssu Mihanizat0r (~Miranda@83.149.37.226)
07:43.20kerioi asked a dude in #gnupg about modifying the expiration date without having the secret key
07:43.37keriohe said no, unless [condition]
07:43.48kerioand then we checked, and [condition] is false in our case
07:44.29keriojust get nokia to sign the Release file with a different key
07:44.34keriopossibly the maemo.org one
07:44.40DocScrutinizer05in 'our' case nokia is in posession of the secret key
07:44.41freemangordonkerio: you're missing that Nokia is willing to help ;)
07:45.01kerioor maemosw admin
07:45.03DocScrutinizer05no, *we* are willing to help Nokia
07:45.12kerioDocScrutinizer05: you'd still have to push the key somehow
07:45.13freemangordonDocScrutinizer05: either ways
07:45.20keriobut to push the key you need a working HAM
07:45.35kerioand that's just false, for devices that don't know about cssu
07:45.58keriothe MaemoSW Admin key doesn't expire
07:46.42freemangordonkerio: you suggest Nokia to push PR1.4?
07:46.54jonwilmore like 1.3.2 :)
07:47.16freemangordonI don;t think there is enough expertise left for that
07:47.19DocScrutinizer05none of that will fly, via SSU
07:48.21DocScrutinizer05please first get stuff sorted in *detail* how repo, key, HAM, apt works
07:48.43DocScrutinizer05place a concise but correct explanation of normal operation on wiki page
07:48.53DocScrutinizer05then analyze the problem we're facing
07:49.07DocScrutinizer05put that analysis there as well
07:49.34DocScrutinizer05based on that we can check what are our options
07:51.03DocScrutinizer05basically the analysis is as ashort as "on point 7 of above explanation of normal operation we run into error 'key expired'"
07:52.01DocScrutinizer05"since point 3 and point 8 we can't do anything about it on server/repo side" or similar
07:53.06keriois nokia willing to issue like *two* commands?
07:53.21keriothey just need to use a different key for the repo
07:53.25kerioa key that's already on the devices
07:53.50kerioaka one of those in apt-key list
07:54.02freemangordonkerio: you mean to resign the packages with i.e. maemo.org key?
07:54.04kerioserver-side change, nothing to do on the devices themselves
07:54.07keriofreemangordon: the packages aren't signed
07:54.24keriothe Release file is signed, and the Release has the md5sum of the Packages* files
07:54.33freemangordonok
07:54.36kerioand those have the md5sums of every deb, tarball and dsc
07:54.46freemangordonok,ok
07:55.09DocScrutinizer05freemangordon: you forwarded mail to kerio and gregoa?
07:55.10jonwilso all they need to do is to re-sign the Release file in their repos with a key that works?
07:55.16kerioyep
07:55.27freemangordonDocScrutinizer05: no, I don;t have their mails
07:55.30kerioit has to be a key that we (the n900s) already know of
07:55.49jonwilis there a key that's on the N900s that hasn't expired?
07:55.54keriojonwil: plenty :)
07:56.00jonwilok, great
07:56.19jonwilin that case it seems like the problem is simple assuming Nokia still has the private half of a suitable key
07:56.35freemangordonkerio: forwarded
07:56.49keriojonwil: yep
07:57.18keriomerlin1991: do you have the private key of 2E6D6F9A, "maemo.org community repositories (fremantle) <repositories@maemo.org>"?
07:57.24freemangordonkerio: doesn't key contains for which server it was issued for?
07:57.31keriofreemangordon: no, keys are just gpg keys
07:57.36freemangordonok
07:57.44keriooh right, there's maybe another issue
07:57.47kerioHAM has to be happy of the key
07:58.16kerioso it has to be one of the keys listed under nokia-system in ham/domains/variant-domains.xexp
07:58.34jonwilis there a key in that list that isn't expired?
07:58.49kerio"MaemoSW Admin <admin@maemo.research.nokia.com>"
07:59.06freemangordonyep
07:59.10keriocrap, that's the only one, hopefully nokia still has that one
07:59.11DocScrutinizer05ok guys ( thedead1440), I can't be the driving force behind this since my plate is filled with 'other stuff of minor importance ;-P', so are you able to sustain this discussion on your own?
08:01.32freemangordonkerio: what about maemo repos key?
08:01.40thedead1440DocScrutinizer05: me for? I'm reading the backscroll :D
08:01.55DocScrutinizer05thedead1440: you mentioned jonni
08:02.08keriofreemangordon: those aren't listed in the nokia-system/nokia-certified domain
08:02.11thedead1440DocScrutinizer05: ah ok I'll speak to him
08:02.13DocScrutinizer05please invite him and fw mail if you think so
08:02.21kerioit *shouldn't* matter, mind you, because you'll never upgrade to a package from those repositories anyway
08:02.30keriobut i'm not sure
08:03.24thedead1440ok DocScrutinizer05 I'll speak to him and ask him if he would like to come here and share his view
08:03.47kerioaiui, domain information in HAM prevents the upgrade to a package from a higher domain to a lower domain
08:03.59keriobut i'm not sure if that information is stored across uninstalls, probably yes
08:04.07DocScrutinizer05fine, I'm out of the loop since other pressing affairs like finding a new sponsor for my bagels
08:04.14thedead1440haha
08:04.21DocScrutinizer05oooh, and that negligible issue of maemo migration
08:05.00thedead1440negligible? i thought it was on auto-pilot :D
08:05.07DocScrutinizer05HAHAHAHA
08:05.36DocScrutinizer05only one on auto-pilot is Murphy, as usual
08:05.58thedead1440:D
08:06.11kerioah crap, maemosw isn't actually on devices
08:06.24keriowhy did i have it? :s
08:06.28keriowe might be actually screwed
08:06.35freemangordonkerio: what?
08:06.42DocScrutinizer05he even resort to giving me unbearable tooth-ache
08:06.49freemangordonyou mean it is listed, but not present?
08:06.51kerioi just deleted all the keys in apt and reimported the .gpg file from nokia
08:06.53kerioit's listed in HAM
08:07.07kerioor, rather, the fingerprint is stored in HAM
08:07.11thedead1440DocScrutinizer05: take some rest
08:07.14kerioso if we got the key on the device, it would work for HAM
08:07.32freemangordonbut we don;t have it?
08:07.39keriofreemangordon: sudo apt-key list
08:07.47freemangordonit is listed there
08:07.50kerio:o
08:08.01kerioDocScrutinizer05: we need your vanilla device for a tiny bit
08:08.05kerio`sudo apt-key list`
08:08.12DocScrutinizer05umm
08:08.23freemangordonpub   1024D/4510B055 2009-03-18
08:08.23freemangordonuid                  MaemoSW Admin <admin@maemo.research.nokia.com>
08:08.30DocScrutinizer05fsck, no rootsh on vanilla device
08:08.44kerioDocScrutinizer05: haven't you got ssh on it?
08:08.47jonwilI have a vanilla no-CSSU-anything device
08:08.50jonwilwith ssh on it
08:08.53DocScrutinizer05neither
08:09.02DocScrutinizer05which vanilla device has ssh?
08:09.05kerioDocScrutinizer05: why do you have it? :o
08:09.11keriook, then we need your slightly less vanilla device
08:09.16jonwilmy device has no changes to the phone
08:09.16freemangordonjonwil: try it, please
08:09.21keriojonwil: `sudo apt-key list`
08:09.43keriofreemangordon: i reckon it's one of those key i recvd from a keyserver manually, but i'm not sure
08:09.54kerioi deleted all the keys and readded variant-keys.gpg
08:10.09thedead1440apt-key list shows a number of keys expired at the same time as the key Nokia want to replace; so the issue here is more than 1 key?
08:10.14freemangordonkerio: I am sure i didn;t touch gpg keys here
08:10.20keriothedead1440: do you see a MaemoSW Admin key?
08:10.32freemangordonhe is on -thumb :)
08:10.39thedead1440kerio: pub   1024D/4510B055 2009-03-18
08:10.40thedead1440uid                  MaemoSW Admin <admin@maemo.research.nokia.com>
08:10.41thedead1440sub   2048g/F18168D7 2009-03-18
08:10.57jonwilhttp://pastebin.com/vpxedgjE
08:11.05jonwilThats the output of apt-key list in SSH
08:11.16freemangordonyep, the key is there
08:11.16kerioweird, a phantom key
08:11.19DocScrutinizer05http://paste.ubuntu.com/1557762 FWIW
08:11.22keriohow did it *get* there?
08:11.23freemangordonwhy phantom?
08:11.33freemangordonnokia put it there
08:11.38keriofreemangordon: but where?
08:11.47freemangordonNFC :D
08:11.53keriojust a personal curiosity, mind you
08:12.09thedead1440why do i have a MaemoSW key and Doc doesn't have it
08:12.16keriothedead1440: because you can't read
08:12.30keriook, so
08:12.32thedead1440ah scrolling error :D
08:12.41jonwilok, so does that list I pastebinned help?
08:12.45keriojonwil: yep
08:12.52jonwilok, so there is a key on that list we can use?
08:12.57jonwilAssuming Nokia has the private half?
08:13.04kerioit means that nokia MUST sign their Release file with that key
08:13.05kerioyep
08:13.30freemangordonkerio: but, but, if public key is not on the devices?
08:13.39keriofreemangordon: the public key is on the devices
08:13.53freemangordonok. it was you to ask "where" :P
08:14.25kerioi meant that it's not in the keychains that are shipped in /usr/share/hildon-application-manager/keys
08:14.37keriousually you ship a file somewhere and apt-key add it in postinst
08:14.38jonwilok, so we better hope Nokia has the private half of that key
08:15.12freemangordonyep
08:15.54DocScrutinizer05could we sneak in arbitrary keys from postinst with root perm?
08:16.02kerioDocScrutinizer05: most definetely
08:16.16keriobut you also need to make HAM happy, for it to work properly
08:16.27kerioor enable redpill mode and disable the domain verification
08:16.35DocScrutinizer05meh
08:16.43freemangordonkerio: no redpill on pr1.3
08:16.45freemangordonafaik
08:16.48keriofreemangordon: lies
08:16.56kerioyou just have to edit ~/.osso/something
08:16.57DocScrutinizer05DOES redpill mode WORK on stock pr1.2+ HAM?
08:17.31jonwilSo basically we are going to ask Nokia to re-sign all the Release files with the MaemoSW Admin key (if they have it) and then everything will magically start working again?
08:17.40DocScrutinizer05afaik it got completely nuked in PR1.2
08:17.44keriojonwil: yep!
08:17.56kerioDocScrutinizer05: i only ever used PR1.2, and i had redpill mode then
08:18.11kerio1.2+, i mean
08:18.17jonwilAssuming Nokia has that key, it seems like a fairly simple request for them :)
08:18.18DocScrutinizer05please verfy and confirm
08:18.43keriojonwil: that also assumes that there's someone in nokia who knows how to operate a terminal
08:18.47DocScrutinizer05jonwil: basically Nokia is asking us what to do
08:18.51freemangordon:D
08:18.52jonwilok
08:19.24DocScrutinizer05so if we're polite and don't ask them to do BS, we will have a smooth cooperation
08:20.21keriograb this other key, sign these two files, KEEP HOSTING THOSE REPOS FOREVER AND EVER
08:20.37DocScrutinizer05there might Nokians show up here and join the discussion, please be nice and welcome them. don't bash them as they're not the ones who messed up stuff
08:20.45keriothe weird thing is, it's probably a lot more reasonable than asking for permission to rehost
08:20.55DocScrutinizer05/mode +q kerio
08:21.05kerioDocScrutinizer05: i promise to not curse at elop too much :3
08:22.16freemangordonkerio: like fhj fhdsfha gfdhghsd dlporew Elop?
08:22.44kerionot the lovecraftian curse
08:52.23DocScrutinizer05kerio: you seem pretty savvy about how stuff in repo signing works, could you write up a short but precise description of the "normal case" on http://wiki.maemo.org/Fremantle/Repositories#Basics_of_Operations please
08:53.15DocScrutinizer05sth so a noob like me is able to grok it
08:53.28kerioi would, if the wiki loaded
08:53.37DocScrutinizer05ummm
08:53.48keriodamn, static. is sloooooooooow
08:53.55DocScrutinizer05a tad slow but basically flawless here
08:55.31DocScrutinizer05yeah, actually right now it's extremely slow
08:56.10DocScrutinizer05so better keep a copy of your edits in copy buffer when hitting "save"
08:56.28DocScrutinizer05kerio: many thanks
08:56.56kerioit's ok, i was actively looking for something to do instead of studying
09:00.46kerioDocScrutinizer05: i don't know what to write D:
09:01.16DocScrutinizer05start at beginning ;-D
09:01.30freemangordonkerio: express yourself :P
09:01.35DocScrutinizer05"once there been a virgin OS, with a signing key shipped on it..."
09:02.01freemangordon"but a bad wizard came and ..."
09:02.20DocScrutinizer05"when user start HAM, it does <foo< <bar> and for that it goes to that signing key... bla bla bla"
09:02.21freemangordons/wizard/dragon/
09:09.31kerioDocScrutinizer05: does your vanilla HAM at least "refresh" the repos correctly?
09:14.38DocScrutinizer05kerio: right now I doubt anything vanilla does work
09:14.47DocScrutinizer05aah wait, you meant Nokia repos
09:15.07kerioyep
09:15.18kerioso disable extras and do a refresh
09:15.51*** join/#maemo-ssu joshgillies (~josh@58-6-102-119.dyn.iinet.net.au)
09:19.07keriohold on now, why do we have a problem again?
09:19.12keriocssu ships his own packages
09:20.48keriodo we want nokia to ship something to notify people of CSSU?
09:21.03freemangordondeffinitely
09:30.11kerioDocScrutinizer05: done
09:34.08*** join/#maemo-ssu ivgalvez (~ivgalvez@89.140.113.138.static.user.ono.com)
09:34.34kerioDocScrutinizer05: i split my explanation in two, half in Basics of Operations and half in Issue 1
09:35.40DocScrutinizer05kerio: I get error "DNS server returned answer without data" for "Nokia SSU" and "Nokia apps" here
09:35.47kerio...wat
09:36.13keriothe fuck does that mean?
09:36.38kerioDocScrutinizer05: iirc HAM has a "log"
09:38.39DocScrutinizer05could not resolve host: downloads.maemo.nokia.com (DNS server returned answer with no data)
09:38.48kerioDocScrutinizer05: connection?
09:39.34DocScrutinizer05meh, wlan fscked
09:39.38keriolol
09:41.29DocScrutinizer05that looks more like it now
09:43.13DocScrutinizer05or not, seems stalled
09:43.19DocScrutinizer05aaah
09:43.49DocScrutinizer05failed catalogs: maemo.org (no surprise)
09:44.33keriomr0 and apps update correctly, right? then my analysis is correct
09:44.56DocScrutinizer05however no updates available (20.2010.36.2-2.203.1)
09:45.12keriois this a pr1.3 or a pr1.3.1 device?
09:45.21DocScrutinizer05^^^
09:45.28kerioyeah, you're missing 1.3.1
09:45.35keriomy analysis is *awesome* :D
09:45.45kerioDocScrutinizer05: open a terminal, `apt-cache mp-fremantle-generic-pr`
09:46.02DocScrutinizer05haha, missing root to do that
09:46.13keriojust do what i tell you to do
09:46.22kerioi am aware that you have no root access :)
09:46.45DocScrutinizer05you're also aware that this looks like 'syntax error'?
09:47.23kerio...ok, now `apt-cache policy mp-fremantle-generic-pr`
09:47.45keriothe candidate should be 21.2011.38-1
09:47.52kerioand the installed should be less than that
09:47.53DocScrutinizer05unable to locate pkg
09:47.59DocScrutinizer05spellchecking...
09:48.16keriowell, maybe you don't have generic, you have a localized one
09:48.28keriobut why would you not flash Global, anyway?
09:48.45DocScrutinizer05because that's a *virgin* device
09:48.58kerio...is it still pr1.3?
09:49.08DocScrutinizer05however no updates available (20.2010.36.2-2.203.1)
09:49.54kerioDocScrutinizer05: dpkg -l | grep mp-fremantle-
09:49.58DocScrutinizer05second time it booted here
09:50.09kerioyou haven't even reflashed it yet?
09:50.31DocScrutinizer05nope
09:51.05DocScrutinizer05mp-fremantle-203-pr
09:51.18DocScrutinizer05surprise surprise
09:52.01kerioDocScrutinizer05: ok, apt-cache policy mp-fremantle-203-pr
09:52.02keriowhat's 203?
09:52.08keriolike, which nation?
09:52.17DocScrutinizer05nfc
09:52.37merlin1991oh god, they have no plan whatsoever
09:52.46keriomerlin1991: who?
09:52.47merlin1991just read the mail
09:52.49kerio:D
09:52.51DocScrutinizer05candidate 21.2011.38-1.203.1
09:52.52kerioit's good
09:52.58keriothat means that we can supply our own plan
09:53.14kerioDocScrutinizer05: my analysis *is* correct
09:53.17kerio^_^
09:53.24DocScrutinizer05good
09:53.25merlin1991DocScrutinizer05: did you email Pali?
09:53.26kerioHAM updates correctly, but doesn't give a fuck
09:53.43DocScrutinizer05it better is, or we'll find you... ;-P
09:53.56merlin1991he's the one who read the important ham code bits, I just talk out of my arse based on what I've experienced playing with the system
09:54.04DocScrutinizer05sure, he already answered awesome elaborate mail
09:54.28merlin1991can you forward that to me too? (I'm interested in the details aswell :D)
09:54.34DocScrutinizer05wonder where he is
09:56.09DocScrutinizer05merlin1991: first 2 letters of your mail pls
09:56.29merlin1991starts with my full name seperated by dot ;)
09:56.47merlin1991also ch
09:57.00keriomerlin.nineteenninetyone
09:57.09merlin1991kerio: :D
09:58.22*** join/#maemo-ssu Guest44961 (~phr3ak@ip-213-220-198-105.net.upcbroadband.cz)
10:00.19DocScrutinizer05GOD, dafaq, seems Nemein playing with bottleneck again
10:01.01DocScrutinizer05hmm, no, tmo is lightning fast
10:01.11DocScrutinizer05wiki though refuses connection
10:01.52merlin1991DocScrutinizer05: you hit the old address seperated by _ not . ;)
10:02.01DocScrutinizer05phoooooh, once it connects it works like....
10:03.54*** join/#maemo-ssu Estel_ (~Estel@d56-215.icpnet.pl)
10:03.54*** join/#maemo-ssu Estel_ (~Estel@Maemo/community/contributor/Estel-)
10:16.52jonwilok, so do we have a plan to keep the Nokia device repos going in the long term or not?
10:17.01jonwilor is it still to-do?
10:24.01DocScrutinizer05jonwil: for now it seems downloads.maemo.nokia.com is not getting transferred to HiFo, nor planned to get scrapped
10:24.19DocScrutinizer05jonwil: so what do you mean by "we got a plan"?
10:24.55jonwilok, so the plan is for that repo to keep working and keep being hosted by Nokia and for the key issue to be sorted
10:25.09jonwilbut for no further changes to that repo to be made (i.e. no future security updates)
10:26.26ivgalveza list of repositories hosted at Nokia have been forwarded to Nokia representatives
10:26.58ivgalvezand we have asked them to provide the  HiFo the right to redistribute the binaries hosted on those repositories
10:27.04*** join/#maemo-ssu ruskie (ruskie@sourcemage/mage/ruskie)
10:27.37ivgalvezhowever is very unlikely that they can give us that permission unless we examine all the content in a per package basis
10:28.01jonwilyeah I suspect there are 3rd party packages there that Nokia cant legally allow HiFo to redistribute
10:28.04jonwillike say Flash
10:28.06jonwilor say Facebook
10:28.09ivgalvezas for 3rd party binaries will be more difficult to obtain that permission
10:28.12ivgalvezyes
10:28.21ivgalvezor worse: TI drivers
10:28.51ivgalvezbut we are still negotiating that, and it could take a while, with their legal department
10:29.14ivgalvezin the meantuime we have asked them not to shut down downloads
10:29.18jonwilok
10:29.55ivgalvezthey are also more reluctant with Harmattan stuff
10:30.57merlin1991kerio: who found out that the maemo sw key is still valid, and also linked to the ssu repo domain? (btw nice find :D)
10:32.26kerioi found that today, but iirc i also knew that from the past
10:32.42*** join/#maemo-ssu arcean (~arcean@aacv200.neoplus.adsl.tpnet.pl)
10:32.48kerioit's not a nice find, it's a combination of less and apt-key list
10:33.09merlin1991and a bit of gpg unless you can magically build fingerprints in your head :D
10:33.16keriomerlin1991: apt-key finger
10:33.32keriojonwil: aiui we plan on shipping a single update there
10:33.55kerioto enable a system-level repo controlled by us
10:33.57merlin1991kerio: damn, I went the long road to double check it :D
10:34.14jonwilWhat would go in this new system-level repo?
10:34.27keriojonwil: something to tell people "hey, there's cssu if you want more updates"
10:34.31jonwilok
10:34.34kerioand security updates
10:34.57jonwilso security updates as in the recent changes to maemo-security-certificates-* or whatever?
10:35.17jonwilAnything else we have (e.g. in CSSU) that would count as a security update?
10:35.18keriowhatever we'll need in the future, too
10:35.21kerioyep
10:35.58merlin1991jonwil: a plentora of library upgrades because of known cves
10:36.22jonwilOne of these days I want to see someone update Gecko in microb to pick up x number of years worth of security improvements
10:36.37kerioto be fair, we could make it easier and just enable cssu-stable on people
10:37.08ivgalvezI would bet for that
10:37.09merlin1991freemangordon and romaxa have been workign on microb lately
10:37.18ivgalvezinstead of yet another CSSU flavour
10:37.40jonwilDo we have any clue if Nokia would even allow this community-repo idea? Or is that something else still under discussion?
10:38.03jonwilgreat if someone is working on microb
10:38.06ivgalvezthey are willing to transfer all support for devices so probably yes
10:38.24ivgalvezfrom a technical POV they are alligned with us
10:38.28merlin1991from the top of my head we have a newer libxml, openssl, libcurl, pango and even some patches to the microb-engine
10:38.38ivgalvezthe problem is with legal department around IP
10:39.07jonwilWhy are they more wary regarding Harmattan?
10:39.44ivgalvezthat one of the reasons why they asked us to wipe out any reference to Nokia as supporter or maintainer or anything related to warranties from maemo.org
10:40.02ivgalvezprobably because Harmattan sold a few millions of devices
10:40.26ivgalvezbut let's accept what they offer now and we will push for more later
10:40.39ivgalvezthat's the motto
10:40.40jonwilyeah lets do that
10:41.01jonwilAre we asking for permission to redistribute the contents of the nokia-binaries SDK repository?
10:41.08ivgalvezyes
10:41.49DocScrutinizer05ivgalvez: I request to get into the loop as HiFo technical and admin officer
10:42.36ivgalvezno problem with me, we are probably having a meeting tomorrow I will propose it
10:43.03ivgalvezbut you must know that they asked for absolutely confidentiallity
10:43.18DocScrutinizer05now that's not a problem with me
10:43.45DocScrutinizer05since I guess that confidentiality is between HiFo at large and Nokia
10:43.54ivgalvezanyway we are pushing during January with any luck or response
10:43.58ivgalvezwithout
10:44.22ivgalvezat least the technical guys contacted me about the gpg keys
10:44.24jonwilme, I guess the most useful thing I can do here is to go back to working on reverse engineering the GPRS bits (starting with csd-gprs and then moving to libicd-network-gprs and stuff after that)
10:44.43*** join/#maemo-ssu xes (~xes@unaffiliated/xes)
10:44.56DocScrutinizer05seems Nokia starts to realize they have some responsibility still for their product that they can't simply drop on community's feet
10:45.09ivgalvezyep
10:46.23DocScrutinizer05they did an awesome job to gain full control over their stuff, now thei're locked in their own prison, so to say
10:47.43DocScrutinizer05and then they dropped the key and lost it, literally ;-P
10:47.57ivgalvezthere should be a mess in there right now
10:48.11ivgalvezlooking all the movements in staff and technical
10:48.14keriolet's hope they still have the key to the backdoor
10:48.18kerioaka MaemoSW Admin
10:48.26ivgalvezor to the toilets :D
10:50.17ivgalvezDocScrutinizer05 have you talked to rzronline or MAG about the old proposal to create a community repo for Harmattan
10:50.26ivgalveznow we will be in position to do that
10:51.18DocScrutinizer05nope, I didn't
10:52.04DocScrutinizer05ivgalvez: we're also in a good position now to ask Nokia about supporting maemo.org hosting for a bit longer, since it seems they realize they might *need* us
10:52.06ivgalvezwe should have a proper package manager though
10:52.24DocScrutinizer05ivgalvez: you noticed quote of Nemein?
10:52.36keriodoesn't harmattan use yum?
10:52.49ivgalvezyes, as I told you before we are pending response to our latest emails
10:53.24ivgalvezI'd like to have a new conference call with the Nokia guys in order to clarify a few things and to insist about that
10:53.59jonwilI recon Corporate Lawyers need to go on the list of things that should never have been invented :)
10:54.01ivgalvezDocScrutinizer05: as we suspected, the quote is unnafordable
10:56.07thedead1440kerio: no its apt... also Harmattan has the same MaemoSW Admin key as Fremantle
10:56.51keriothedead1440: just that one key?
10:57.22DocScrutinizer05ivgalvez: it's not exactly unaffordable, it's reasonable and it's scalable
10:57.42ivgalvezunafordable to our current financial status
10:57.52thedead1440kerio: nope the repo signing keys are the same and expired also same on 2012-10-03
10:57.56keriohm
10:58.08keriowell, here's to hoping that they still have the private key to that key :)
10:58.22thedead1440but no error about the expiry on Harmattan
10:58.38thedead1440this means they should have it since its on Harmattan
10:59.22kerio~seen X-Fade
10:59.28infobotx-fade is currently on #maemo (7h 20m 20s) #harmattan (7h 20m 20s) #meego (7h 20m 20s) #maemo-ssu (7h 20m 20s), last said: 'ZogG_laptop: ?'.
11:00.21DocScrutinizer05ivgalvez: (current status) ack
11:01.16DocScrutinizer05ivgalvez: regarding your question on that gpg mail re flashing a PR1.4: I simply thought it's overly inconventient to most lusers
11:21.51*** join/#maemo-ssu andre__ (~andre@wikimedia/aklapper)
11:29.46*** join/#maemo-ssu kolp (~quassel@212.255.232.227)
11:38.00*** join/#maemo-ssu Martix_ (~martix@ip-62-245-106-78.net.upcbroadband.cz)
11:58.55*** join/#maemo-ssu Estel_ (~Estel@d56-215.icpnet.pl)
11:58.55*** join/#maemo-ssu Estel_ (~Estel@Maemo/community/contributor/Estel-)
12:11.24*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-jvhmyhbptfukbjpv)
13:30.52*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
13:39.59*** join/#maemo-ssu freemangordon (~freemango@130.204.50.168)
14:12.25*** join/#maemo-ssu jon-kha (~jon-kha@hoasnet-50dd32-87.dhcp.inet.fi)
14:19.04*** join/#maemo-ssu arcean (~arcean@aacv200.neoplus.adsl.tpnet.pl)
14:39.26*** join/#maemo-ssu ShadowX (~7350@195.24.90.254)
14:42.22*** join/#maemo-ssu NIN101 (~NIN@p5DD283F1.dip0.t-ipconnect.de)
14:59.57*** join/#maemo-ssu freemangordon (~freemango@130.204.50.168)
15:02.23*** join/#maemo-ssu Martix_ (~martix@ip-62-245-106-78.net.upcbroadband.cz)
15:32.05*** join/#maemo-ssu Martix_ (~martix@ip-62-245-106-78.net.upcbroadband.cz)
15:58.55*** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se)
16:02.03gregoakerio: it seems the "MaemoSW Admin" key is the file /usr/share/keyrings/maemointernal-keyring.gpg, package maemointernal-keyring, and imported by /var/lib/dpkg/info/maemointernal-keyring.postinst
16:02.36kerioooh, neat
16:02.38freemangordonyay :)
16:02.56keriofreemangordon: it doesn't matter, it just eases my mind
16:03.12freemangordonkerio: so, what is the current status?
16:03.18keriofreemangordon: same as before
16:03.40keriowe tell nokia to look for the matching secret key and we hope that they can find it
16:04.00freemangordonkerio: so a simple resign will do the job?
16:04.12keriosure, why not?
16:04.16freemangordongreat
16:05.56freemangordonwe should ask HiFo to ask Nokia if they agree to push a "cssu-enabler" package
16:06.14keriohow do you "push" something like that?
16:06.38freemangordonupgrade xterm for example
16:06.51freemangordonor some other nokia pre-installed application
16:06.55keriolike the metapackage
16:06.56kerio:)
16:07.04freemangordonno nee of metapackage
16:07.05kerioyou'd have to push it in a way that makes it uninstallable
16:07.06freemangordon*need
16:07.10kerioyes, need
16:07.18keriobecause xterm won't be updated by HAM by itself
16:07.39kerioif we're going with that route, we might as well do it with n900-fmtx-enabler
16:07.53freemangordonevery package in user section will do the job aiui
16:07.57kerioyeah
16:08.16kerioonce the repo is fixed, we can think of what to do
16:08.21freemangordonand there are a couple of them.
16:08.24freemangordonsure
16:08.45freemangordonkerio: iirc there are some links by default on the desktop
16:08.45keriothe easiest thing to do would be to decide that cssu-stable is stable enough, and push that
16:08.53freemangordonyep
16:09.18kerioespecially considering that "backporting" all the security fixes isn't really a possibility
16:09.27kerioDocScrutinizer05: yay or nay?
16:11.10freemangordonbtw (if thedead1440 is right and harm has the same sysadmin key) Nokia has not lost the private
16:11.21DocScrutinizer05freemangordon: why would HiFo deal with such topic?
16:11.28keriofreemangordon: it can be a historical relic
16:11.53keriofreemangordon: the harm repos use the same keys as repository.maemo.org
16:11.54freemangordonDocScrutinizer05: because aiui they are the ones to talk to Nokia
16:12.07freemangordonDocScrutinizer05: though it does not really matter who will do it
16:12.11DocScrutinizer05no they are talking to Nokia LAWYERS
16:12.20freemangordonok
16:12.29freemangordonthen the council :)
16:12.47thedead1440freemangordon: you can check it out here: http://pastebin.com/XWCtw0s1
16:13.18keriothedead1440: will the harmattan package manager accept the maemosw key, though?
16:13.28kerio(and do we care?)
16:13.37freemangordonoh, it is the same as on fremantle
16:13.50freemangordonyeah, could be some leagscy :(
16:13.56freemangordon*legacy
16:13.58thedead1440kerio: what I'm wondering is why when it has the same expiry date as on fremantle does only fremantle have the expired key issue
16:14.19keriothedead1440: it's a HAM trust issue
16:14.20freemangordonthedead1440: that key has not expired
16:14.31keriothe repos *are* updated correctly
16:14.32thedead1440freemangordon: it has: expired: 2012-10-03
16:14.48kerioHAM just doesn't like that the key is expired, and won't accept updates to system packages from that repo
16:15.05freemangordonthedead1440: "MaemoSW Admin <admin@maemo.research.nokia.com>"?
16:15.11freemangordonno, it is not
16:15.17freemangordonand aiui it never expiers
16:15.28thedead1440no Nokia repository signing key 4v1 that's the one that is expired on fremantle too
16:15.43keriothedead1440: which key is used for the repos?
16:15.47thedead1440all the Nokia repository signing keys are expired on both Harm and Fremantle
16:16.03freemangordonthedead1440: which key is used for ovi?
16:16.19*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
16:16.41thedead1440freemangordon: not too sure
16:17.25freemangordoni guess it is either "GenSS (GenSS System)" or "...file distribution..."
16:18.32thedead1440let me ask Jonni
16:19.38keriofreemangordon: the fremantle ovi uses the 4v1 key
16:20.12freemangordonkerio: I asked what harm uses
16:29.03DocScrutinizer05on HARM there's no HAM
16:29.24freemangordonsure
16:29.35thedead1440but even when you apt-get update on Fremantle you get the W: Error while you don't get the same on Harmattan
16:29.48freemangordon:nod:
16:30.07keriothedead1440: really?
16:30.18DocScrutinizer05blame aegis and the black magic it introduces
16:30.20keriohm, i don't know how to check the contents of a .gpg
16:30.23thedead1440yes kerio hence I'm banging on the same thing like a broken record
16:30.27kerioDocScrutinizer05: nah, it's probably just a different key
16:31.14thedead1440if there is a W: Error in one and not in another it means the server can be tweaked to adjust it, no? Device wouldn't need to have any changes be made then?
16:32.23thedead1440after all, Harmattan accesses downloads.maemo.nokia.com too for SSU etc so its the same repo
16:34.20keriothe server can't be tweaked to adjust it
16:34.26kerioit's not the same repo
16:35.31*** join/#maemo-ssu Lava_Croft (lcd@satgnu.net)
16:37.58thedead1440kerio: fremantle hits downloads.maemo.nokia.com/fremantle while harmattan hits downloads.maemo.nokia.com/harmattan so its just a different branch, isn't it?
16:38.06kerioit's a different apt repository
16:38.10keriothere are at least 3 just for fremantle
16:38.19thedead1440same there are 3 for harmattan too
16:43.18*** join/#maemo-ssu xes (~xes@host44-237-dynamic.14-87-r.retail.telecomitalia.it)
16:43.19*** join/#maemo-ssu xes (~xes@unaffiliated/xes)
17:06.49*** join/#maemo-ssu ShadowX (~l4m3rx@darknet.escom.bg)
17:12.15*** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm)
17:37.51keriodid someone ask nokia if they have that key?
18:20.40thedead1440freemangordon: GenSS is what is used for the Harmattan keys according to Jonni
18:27.26thedead1440those Nokia signing keys in Harmattan that are expired are not used anywhere confirmed hence no error message; apologies for the false alarm :S
18:31.23keriowho's actually talking to the nokia meego dudes?
18:32.27*** join/#maemo-ssu Martix_ (~martix@ip-62-245-106-78.net.upcbroadband.cz)
18:33.48thedead1440DocScrutinizer05 rec'd the email so i would presume him but he also has told them to join here...
18:42.39*** join/#maemo-ssu jaded (~jade@Jade.broker.freenet6.net)
18:42.39*** join/#maemo-ssu jaded (~jade@unaffiliated/jade)
19:03.00*** join/#maemo-ssu arcean (~arcean@aadc193.neoplus.adsl.tpnet.pl)
19:23.50*** join/#maemo-ssu arcean (~arcean@aadc193.neoplus.adsl.tpnet.pl)
19:48.35*** join/#maemo-ssu phr3akDom (~phr3ak@ip-213-220-198-105.net.upcbroadband.cz)
20:44.09*** join/#maemo-ssu arcean (~arcean@aadc193.neoplus.adsl.tpnet.pl)
20:44.35*** join/#maemo-ssu arcean (~arcean@aadc193.neoplus.adsl.tpnet.pl)
20:46.55*** join/#maemo-ssu _rd (~rd@p57B49071.dip0.t-ipconnect.de)
20:53.31*** join/#maemo-ssu arcean (~arcean@aadc193.neoplus.adsl.tpnet.pl)
22:10.22*** join/#maemo-ssu MrPingu (~MrPingute@86.92.226.97)
22:26.54*** join/#maemo-ssu joshgillies (~josh@hobart.office.squiz.net)
22:27.04*** join/#maemo-ssu arcean (~arcean@aadc193.neoplus.adsl.tpnet.pl)
23:21.52*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
23:59.11*** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au)

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