IRC log for #maemo-ssu on 20140609

00:01.56*** join/#maemo-ssu lostak (~lostak@10.47.255.123.static.snap.net.nz)
00:13.26*** part/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
00:28.15DocScrutinizer05RST38h: I'm not planing to switch to Android
00:31.23FIQRST38h, did you ever update the xchat build on n900?
00:31.41FIQthere was this crash vulnerability from a crafted string
00:31.47FIQin n900's version
00:32.40FIQDocScrutinizer05, how much was scratchbox.org?
00:32.54DocScrutinizer0511EUR iirc
00:33.50DocScrutinizer05FIQ: the vulnerability got fixed
00:34.09DocScrutinizer05afaik
00:34.19FIQDocScrutinizer05, but not in the n900 build
00:34.29DocScrutinizer05yes, in N900 build
00:34.31FIQat least not last time I checked
00:34.37DocScrutinizer05o.O
00:34.47FIQwhich was a couple of months ago
00:35.11FIQI don't have the bad string handy
00:35.13DocScrutinizer05[CTCP] Received CTCP-VERSION reply from DocScrutinizer51: xchat 2.8.6.
00:35.22FIQbut I managed to consistently crash xchat
00:35.27FIQback then
00:35.46DocScrutinizer05mybe you didn't update?
00:36.01FIQmine is 2.8.6...
00:36.40FIQI can try dig my logs for it
00:36.47FIQand look into it
00:38.53DocScrutinizer05dang, pastebin refuses to accept pastes
00:39.08DocScrutinizer05so here it goes, sorry for spamming
00:39.41DocScrutinizer05IroN900:~# apt-cache policy xchat
00:39.42DocScrutinizer05<PROTECTED>
00:39.44DocScrutinizer05<PROTECTED>
00:39.45DocScrutinizer05<PROTECTED>
00:39.47DocScrutinizer05<PROTECTED>
00:39.48DocScrutinizer05<PROTECTED>
00:39.50DocScrutinizer05<PROTECTED>
00:39.51DocScrutinizer05<PROTECTED>
00:39.53DocScrutinizer05<PROTECTED>
00:39.54DocScrutinizer05<PROTECTED>
00:47.04DocScrutinizer05http://maemo.cloud-7.de/clean-N900xchat-scrollback-from-rogue-string.sh  21-Jan-2012 13:31   |||   xchatFremantle Extras-devel free armelPackage importedSystem2011-12-02 14:42 UTC   ( http://maemo.org/packages/view/xchat/ ) seems to be the update I recall
00:56.16DocScrutinizer05RST38h: you actually should know best whether or not this issue git fixed by you (I think yes) and where the fixed version supposed to be
00:56.29DocScrutinizer05s/git/got/
00:57.58DocScrutinizer05hmmmm
00:58.08DocScrutinizer05FIQ: maybe I'm completely mistaken
00:58.22DocScrutinizer05IroN900:~# ll /opt/maemo/usr/bin/xchat
00:58.23DocScrutinizer05-rwxr-xr-x 1 root root 611408 2010-11-14 21:34 /opt/maemo/usr/bin/xchat
00:58.41FIQ2010...
00:58.58DocScrutinizer05yeah, but then... I think the fix actually been in a lib
00:59.31DocScrutinizer05and that lib prolly dynamically linked
01:00.12DocScrutinizer05I even seem to remember I been somehow involved into that, back when
01:00.41DocScrutinizer05there might be a ticket I created on that, with suggested patch etc
01:00.55DocScrutinizer05can't recall details
01:01.17DocScrutinizer05too fresh for my alzheimer, I only recall stuff from last millenium
01:12.11DocScrutinizer05Libpango1.0 sounds strangely familiar
01:14.33DocScrutinizer05http://mg.pov.lt/maemo-irclog/%23maemo.2012-01-21.log.html#t2012-01-21T01:30:03
01:19.26DocScrutinizer05http://mg.pov.lt/maemo-irclog/%23maemo.2012-01-21.log.html#t2012-01-21T11:03:27
01:22.21DocScrutinizer05FSCK! https://code.google.com/p/xchat-wdk/issues/detail?id=132#c15 404!
01:22.38DocScrutinizer05http://mg.pov.lt/maemo-irclog/%23maemo.2012-01-21.log.html#t2012-01-21T12:25:55
01:23.46DocScrutinizer05http://mg.pov.lt/maemo-irclog/%23maemo.2012-01-21.log.html#t2012-01-21T14:38:04
01:25.33DocScrutinizer05http://mg.pov.lt/maemo-irclog/%23maemo.2012-01-21.log.html#t2012-01-21T16:05:05
01:28.25merlin1991freemangordon: I'm going to get into the stuff this week!
01:30.06merlin1991so far I've got my beloved n900 with -testing on it back alive, now I'm going to have a look at the various gitorous repos (and -devel) and will compare what is out there
01:33.27*** join/#maemo-ssu jonwil (~jonwil@27-33-80-219.tpgi.com.au)
01:34.10jonwilhi
01:35.48merlin1991hey jonwil
01:38.54DocScrutinizer05relevant: http://en.qi-hardware.com/irclogs/qi-hardware_2012-01-21.log.html#t13:06
01:39.24DocScrutinizer05hey jonwil!! long time no see!
01:41.49jonwilbeen thinking about openssl and all the bugs that have shown up lately, see http://talk.maemo.org/showthread.php?t=93296&page=2
01:48.38DocScrutinizer05hmmmm http://www.openwall.com/lists/oss-security/2012/02/01/9
01:49.29DocScrutinizer05jonwil: yeah, somebody should look into that
01:50.27jonwilI suspect the number of cases where we have closed packages that would be broken as a result of upgrading to 0.9.8za is much smaller than it looks
01:52.53DocScrutinizer05:nod:
01:53.29DocScrutinizer05the guys fixing openssl are not boneheads per se :-)
01:53.49DocScrutinizer05if they can find a way to keep ABI compatible, they for sure will do
01:54.22DocScrutinizer05for any ABI break, you MUST use a new .so-name
01:54.25DocScrutinizer05~2119
01:54.25infobotThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
01:55.05DocScrutinizer05that's how dll stuff is supposed to get handled on unix
01:55.23DocScrutinizer05update up a lib never breaks stuff
01:55.30jonwilbut it isn't always done that way unfortunately
01:55.53DocScrutinizer05yeah, there are idiots out there. EVEN among lib developers ;-)
01:56.46DocScrutinizer05lickily odds are none of them among openssl maintainers
01:56.52DocScrutinizer05luckily even
01:57.39DocScrutinizer05openssl is highly mission critical, nobody would accept maintainers with no clue messing up stuff for everybody using *nix on this planet
01:57.40jonwilthe number of closed packages using openssl isn't as big as I thought it would be
01:58.47DocScrutinizer05the fix would be more devastating than the vulnerability it been caused by
02:01.12DocScrutinizer05I mean, *every* *nix system using openssl lib in mission critical programs. A bug/mishap resulting in a libssl update breaking stuff would be the mega-disaster for all IT running in this solar system
02:01.59DocScrutinizer05instant collapse of complete internet
02:02.14jonwilI do wonder if anyone got any further with figuring out how to replace the essential closed-source packages for the Neo900/FPTF stuff
02:02.21jonwili.e. the ones that need to be replaced
02:03.48DocScrutinizer05well, I just a few hours ago tried to talk freemangordon into finally starting to try and build a freEmantle from FOSS and see what's missing to make a working system, then push all this into a git repo so others can checkout and see what to do
02:05.01DocScrutinizer05[2014-06-09 Mon 01:05:11] <DocScrutinizer05> I thougth since freemangordon already has a working kernel 3.1x for N900, it woukd be naturally if _he_ would try http://talk.maemo.org/showthread.php?p=1420525#post1420525 and then check in all that stuff into any conevnient repo under maybe "cssu-n900" or "neo900-n900" or "freemantle-rx51" or whatever
02:05.03DocScrutinizer05[2014-06-09 Mon 01:06:56] <DocScrutinizer05> Note Please: the thing doesn't even need to produce anything that works by whatever metrics, it just needs to provide the infra others can base on to carry on
02:05.04DocScrutinizer05[2014-06-09 Mon 01:09:52] <DocScrutinizer05> when somebody approaches me ans asks me "I want to help on freemantle! what shoukd I do?" (this happened several times already!) then I need to be able to answer something like "git checkout freemantle-n900 and see what's missing" - it doesn't help to tell that gal/guy "/join #maemo-ssu and ask freemangordon please!"
02:07.28DocScrutinizer05jonwil: ^^^ from #neo900 , you're welcome to /join ! ;-)
02:09.16jonwilhttp://wiki.maemo.org/Porting/Closed_Packages contains a list of the packages that still need to be replaced (rather than being able to be used as-is)
02:13.14DocScrutinizer05jonwil: thanks! :-) updated http://talk.maemo.org/showthread.php?p=1372710#post1372710
02:15.27jonwilbtw has there been any further hardware decisions made (i.e. exactly which hardware neo900 will use)?
02:15.55DocScrutinizer05err, we constantly do such decisions, and sometimes revert them later on
02:16.40DocScrutinizer05most recent thing we seem to have agreed upon: TiWi5 module (WLAN, BT, FM)
02:19.06DocScrutinizer05this "decision" started at http://projects.goldelico.com/p/neo900/issues/546/#ic1610 and yesterday we had a "looks good" chat
02:20.11DocScrutinizer05but that's actually a question ideally asked in #neo900 ;-)
02:30.54*** join/#maemo-ssu amiconn_ (quassel@rockbox/developer/amiconn)
04:26.29*** join/#maemo-ssu radekp (~radek@82.113.39.213)
05:55.15*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
06:23.35*** join/#maemo-ssu lostak (~lostak@10.47.255.123.static.snap.net.nz)
06:52.46*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
07:18.15*** join/#maemo-ssu sixwheeledbeast (~paul@2a01:348:6:860a:b5bf:e048:88b6:2777)
07:40.36*** join/#maemo-ssu freemangordon_ (~ivo@85-118-92-21.mtel.net)
07:41.45*** join/#maemo-ssu LauRoman (~LauRoman@5-14-80-162.residential.rdsnet.ro)
07:45.50*** part/#maemo-ssu freemangordon_ (~ivo@85-118-92-21.mtel.net)
07:52.09*** join/#maemo-ssu freemangordon_ (~ivo@85-118-92-21.mtel.net)
08:06.28*** join/#maemo-ssu gypsy (~whee@192.158.14.99)
08:15.24*** join/#maemo-ssu Gizmokid2005 (~Gizmokid2@dedi1.gizmokid2005.com)
08:23.48*** join/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
08:32.53*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
09:04.29*** join/#maemo-ssu freemangordon_ (~ivo@85-118-92-21.mtel.net)
09:36.43*** join/#maemo-ssu piscodig (~pig@unaffiliated/discopig)
09:40.36*** join/#maemo-ssu arcean (~arcean@aacs183.neoplus.adsl.tpnet.pl)
09:53.18*** join/#maemo-ssu freemangordon_ (~ivo@213.226.63.51)
10:00.05*** join/#maemo-ssu lostak (~lostak@10.47.255.123.static.snap.net.nz)
10:19.08*** join/#maemo-ssu Maxdamantus (~Maxdamant@2001:470:f078::dead:beef:cafe)
11:12.53*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-cgnmgunwicmjiqax)
13:32.27*** join/#maemo-ssu Guest90281 (~FIQ@fiq.se)
13:35.53*** join/#maemo-ssu NishanthMenon (~nmenon@nat/ti/x-dcyrvzrbgbasiocd)
13:42.05*** join/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
13:42.14*** join/#maemo-ssu Guest90281 (~FIQ@prgmr/customer/fiq)
13:58.57*** join/#maemo-ssu FredrIQ (~FIQ@fiq.se)
14:07.46*** join/#maemo-ssu Guest20589 (~FIQ@prgmr/customer/fiq)
14:09.34*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
14:49.13*** join/#maemo-ssu sunny_s (~sunny_s@pd95c1f18.dip0.t-ipconnect.de)
15:16.02*** join/#maemo-ssu edshin (~e@nat/ti/x-gadsybfknqpgyjhx)
15:25.40*** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm)
16:05.33*** join/#maemo-ssu eugene_ (~eugene@109.188.124.178)
16:09.41*** join/#maemo-ssu okias (~okias@berger.cust.centro-net.cz)
17:03.15*** join/#maemo-ssu freemangordon (~ivo@46.249.74.23)
17:43.02*** join/#maemo-ssu arcean_ (~arcean@aafq108.neoplus.adsl.tpnet.pl)
17:55.40*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
18:36.55*** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse)
18:48.57*** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm)
19:14.42*** join/#maemo-ssu NIN101 (~core@n900.quitesimple.org)
19:36.18*** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse)
20:02.20*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
21:06.52*** join/#maemo-ssu javispedro (~javier@Maemo/community/contributor/javispedro)
22:22.15*** part/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
22:28.11*** join/#maemo-ssu Maxdamantus (~Maxdamant@2001:470:f078::dead:beef:cafe)
22:40.54*** join/#maemo-ssu dos1|N900 (~dos@unaffiliated/dos1)
22:43.28*** join/#maemo-ssu xes (~xes@unaffiliated/xes)

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