IRC log for #maemo on 20151228

00:14.42*** join/#maemo andril (~andril@c-66-229-28-40.hsd1.fl.comcast.net)
00:17.15*** join/#maemo pozitrono (~nu@ce.85.7a9f.ip4.static.sl-reverse.com)
01:09.46*** join/#maemo Roth (~quassel@2601:18c:c700:c4d3:566:aedd:2c20:dd8f)
01:20.30*** join/#maemo p771 (~chatzilla@195-241-37-43.ip.telfort.nl)
01:58.01*** join/#maemo protem (~protem@unaffiliated/protem)
02:10.37*** join/#maemo pozitron (~nu@104.238.169.66)
02:26.44*** join/#maemo LauRoman (~LauRoman@5-14-87-59.residential.rdsnet.ro)
02:46.28*** join/#maemo eMHa_ (~mh@p579DB49C.dip0.t-ipconnect.de)
02:49.52*** join/#maemo Defiant (erik@f050171047.adsl.alicedsl.de)
03:01.21*** join/#maemo Venusaur (~wdwrwf@wikipedia/Antonio-Lopez)
03:20.55*** join/#maemo vahe (~funtoo@130.193.124.135)
04:09.59*** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
04:24.21*** join/#maemo vahe (~funtoo@130.193.124.135)
04:31.31*** join/#maemo geaaru (~geaaru@95.237.228.205)
05:19.48*** join/#maemo githogori (~githogori@c-73-70-12-67.hsd1.ca.comcast.net)
05:28.18*** join/#maemo wnd (~wnd@katei.fi)
06:11.07*** join/#maemo krnlyng (~liar@77.117.19.234.wireless.dyn.drei.com)
06:12.38*** join/#maemo povbot (~supybot@178-236-196-236.csc.lt)
07:14.38*** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix)
07:46.36*** join/#maemo Ex-Opesa (~Ex-Opesa@unaffiliated/ex-opesa)
08:11.35*** join/#maemo krnlyng (~liar@77.116.123.209.wireless.dyn.drei.com)
08:22.36*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
08:24.52*** join/#maemo vahe (~funtoo@130.193.124.135)
08:32.26*** join/#maemo FReaper-PC (~FR@115.132.88.188)
08:50.38*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
09:17.42*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
09:24.04*** join/#maemo eMHa__ (~mh@p579DB49C.dip0.t-ipconnect.de)
09:42.12*** join/#maemo RedW (~redw@89-76-164-87.dynamic.chello.pl)
10:00.05*** join/#maemo krnlyng (~liar@178.112.237.143.wireless.dyn.drei.com)
10:19.01ceenei think i got openssl-1.0.1k to build a .deb for maemo
10:19.14ceenewell, it's compiling after a couple fixes to the debian/ directory
10:19.28ceeneit's compiling now on scratchbox for x86
10:19.44ceenei thought it was going to fail so I didn't document anything
10:19.54ceenebut maybe this afternoon i got something testable on the device
10:20.15kerioceene: but why
10:20.34ceenewhy?
10:20.41kerio1.0.2 is the latest stable
10:20.45ceeneah!
10:20.46ceenelol
10:20.46ceenei know
10:20.46keriowe don't have backwards compatibility to maintain
10:20.54kerioand 1.1.0 is going to come out soonish
10:20.59ceenei know, i know
10:21.09ceenebut that was what i could get the easier
10:21.16keriodoesn't debian sid have 1.0.2?
10:21.17ceenedue to my available debian distro
10:21.22ceenei just did want to do a quick test
10:21.24kerioyea
10:21.34ceeneif it goes well, i'll definitely import latest openssl available on sid
10:21.41kerioyea sid has 1.0.2
10:21.42ceenei didn't thought it was going to be this easy
10:21.46ceene1.0.2 will be then
10:22.01ceeneif this thing finishes compiling and the .deb installs, i'll start again from 1.0.2 and document everything
10:22.12ceeneshould I request repo access to upload these changes somewhere?
10:22.35kerioceene: well, you can't actually ship it that way
10:22.54ceeneopenssl is part of the main system, isn't it?
10:22.57kerioyep
10:23.04kerioyou can't replace openssl 0.9.8
10:23.13ceenethere are api mismatches, i guess
10:23.26ceenemaybe this package should be anew and called openssl-1
10:23.33ceeneso both of them can be kept
10:23.37keriohm
10:23.45KotCzarnyalso, i think all apps are linked to libssl.0 or something
10:23.47ceeneat least until all openssl users are upgraded
10:23.50kerioyou should ask freemangordon or merlin1991
10:23.53KotCzarny1.x would make it libssl.1
10:24.10kerioKotCzarny: i think the libssl and libcrypto versions are weirder than that, but yea
10:24.11keriosomething like that
10:24.24ceenelol
10:24.24ceenewell
10:24.31ceenefirst of all i want to have something that compiles
10:24.35ceenei'll ask them later then
10:24.40ceeneto see what must be done
10:24.41KotCzarnyso you should just create libopenssl-1 or something
10:24.45KotCzarnydont know what is the debian way
10:24.51ceenei think it is
10:25.09ceenepython is python2.5, python2.7 and python3
10:25.11KotCzarnyso in turn you dont need repo access to openssl-0
10:25.37kerioeither that or you keep shipping openssl 0.9.8 together with your openssl
10:25.37KotCzarnyii  libssl1.0.0:armhf              1.0.1k-3+deb8u2           armhf        Secure Sockets Layer toolk
10:25.54keriooh
10:25.55kerioOH
10:25.58kerioyea that works
10:25.58KotCzarnyand metapackage openssl that relies on it
10:26.16kerioit's not a metapackage if it actually has files
10:26.25keriothe openssl commandline utility is in the openssl package
10:26.30ceenewell, package build failed :/
10:26.34ceenebut it's probably easily fixable
10:26.44keriodoes maemo have the same package layout?
10:26.45KotCzarnyfixable, maybe, stable?
10:26.57KotCzarnykerio, maemo is a debian spawn
10:27.05ceeneit's gonna be a matter of rewritting a couple debian/ directory things
10:27.18ceeneeverything compiled
10:27.23ceenebut dpkg-build is protesting about something
10:27.23*** join/#maemo eMHa (~mh@p579DB49C.dip0.t-ipconnect.de)
10:27.24kerioyes, but who knew what debian did in 1945 when they began working on maemo?
10:27.28kerio*who knows
10:27.30ceenelol
10:27.38ceenewell, i gotta go now
10:27.44ceenejust wanted to report this back
10:27.47ceenethat it looks good
10:28.06ceenecya!
10:28.33KotCzarnyhttp://repository.maemo.org/extras-devel/pool/fremantle/free/libs/libssl0.9.7/
10:28.34kerioif we have versioned libssl and libcrypto packages then it's not a problem
10:28.41keriodear LORD
10:29.27KotCzarnyand NO openssl package
10:29.38KotCzarnyfunny as it is
10:29.49KotCzarnyno libcrypto either
10:29.58keriocan someone with a handy access to a n900 right now do an apt-cache rdepends openssl
10:30.06kerioKotCzarny: those are not in extras, obviously
10:30.31KotCzarnylets check nssu mirror then
10:30.38KotCzarny(im too lazy to reach for my n900)
10:30.54keriohttp://maemo.org/packages/view/openssl/ doesn't do rdepends
10:30.56Wizzuphttp://sprunge.us/QSRF
10:31.14keriowhy the hell does libssl depend on openssl
10:31.20Wizzupopenssl provides libssl
10:31.23Wizzupit may be split up
10:31.36WizzupNokia-N900:~# apt-cache rdepends libssl
10:31.36Wizzup<libssl>
10:31.47KotCzarnydid you compile 0.9.8 for yourself?
10:31.51keriofucking nokia bullshit
10:32.10keriowell that is actually a problem
10:32.21keriobut i guess it's a problem that has to be fixed at some point
10:32.29KotCzarnyin cssu probably
10:32.35keriowell yes
10:32.45KotCzarnyas jonwil suggested repackaging/recompiling things
10:32.59kerioin theory we don't need cssu for libssl1.0.2 and libcrypto1.0.2
10:33.35KotCzarnydoes the interface really changes between minor versions?
10:33.40keriobut to get them to be used, we need an update to the sdk
10:33.40KotCzarnywhy not just libssl1
10:33.48kerioKotCzarny: the minor version is the letter
10:33.57kerio1.0.1 and 1.0.2 are not abi-compatible
10:34.15KotCzarnyso you will have to recompile EVERY package or keep fuckton of libssl versions?
10:34.24keriofuckton = 2
10:34.26KotCzarnyon every libssl update?
10:34.41kerio1.0.2 is the major version
10:34.52kerio1.0.2a 1.0.2b 1.0.2c... are abi-compatible
10:34.56KotCzarnywhat would happen with 1.0.3 ? or 1.1.0 ?
10:35.00keriothere's no 1.0.3
10:35.05kerio1.1.0 is also not abi-compatible
10:35.14KotCzarnywhat would happen on 1.1.1 ?
10:35.42kerioopenssl 1.0.2 was released on january 2015
10:35.59kerioopenssl 1.1.0 entered prealpha a couple weeks ago
10:36.16kerioKotCzarny: 1.1.1 is likely not going to be abi-compatible with 1.1.0
10:36.21keriostuff changes
10:36.36KotCzarnyso, recompile every package relying on libssl on every libssl change
10:36.41keriosure
10:36.47KotCzarnyfun
10:36.50kerioit's not manual labor
10:36.56kerioa compiler does that for you
10:37.12KotCzarnywhat about packages not maintained by cssu?
10:37.25keriothey're going to stay on 0.9.8
10:38.17KotCzarnybtw. 1.x is api compatible with 0.9.x? (ie. recompilation is enough)
10:38.26keriothey're mostly api-compatible with each other
10:39.51sixwheeledbeastHow many packages not maintained by CSSU will depend on 0.9.8? I can't imagine lots.
10:40.07kerioxchat has been broken for quite a while now
10:40.10keriobecause it forces ssl3
10:40.17keriowhich is not actually usable anymore
10:40.42kerioso it's not like the packages are perfectly working with 0.9.8, anyway
10:42.10Wizzup11:33 < kerio> 1.0.1 and 1.0.2 are not abi-compatible
10:42.12Wizzupare you sure?
10:42.22kerioyes
10:42.25WizzupI upgraded from 1.0.1 to 1.0.2 on my gentoo and didn't recompile anything
10:42.39Wizzupthey are even in the same slow
10:42.41Wizzupslot*
10:42.45Wizzup[I] dev-libs/openssl Available versions: (0.9.8) 0.9.8z_p7^d ~0.9.8z_p8^d (0)    1.0.1p^d ~1.0.2a^d ~1.0.2b^d ~1.0.2c^d 1.0.2d^d ~1.0.2d-r2^d 1.0.2e^d
10:43.05WizzupIf they are not compatible ABI wise, gentoo would have made a new slot
10:43.07keriooh nvm maybe i suck cocks
10:43.14KotCzarny:)
10:43.24kerioMinor releases that change the last digit, e.g. 1.0.1 vs. 1.0.2, can and are likely to contain new features, but in a way that does not break binary compatibility.
10:44.00KotCzarnyoh, fun, libssl 0.9.8z
10:44.07kerioz is quite old
10:44.10keriowe're at ze i think
10:44.22keriozh
10:44.31kerio...we should upgrade to zh
10:44.33KotCzarnycan at least someone compile 0.9.8zWHATEVER into extras?
10:44.42kerio*cssu
10:44.45keriothey already are
10:45.04KotCzarnyextras would benefit people without cssu
10:45.16kerioextras is not a system repository
10:45.42kerioextras is absofuckinglutely not the place to put an updated openssl into
10:45.45KotCzarnyotoh, f*ck people who didnt update and release fremantle-1.4cssu
10:45.52WizzupKotCzarny: people should just switch to cssu :)
10:46.13keriocssu-testing is at 0.9.8zf
10:46.17KotCzarnybecause really, fremantle-1.3.1 was LONG time ago
10:46.19kerioso we're missing two security updates
10:46.41KotCzarnywe need roadmap for cssu!
10:46.45kerioKotCzarny: yeah but we have like 1.5 full-time devs
10:46.48KotCzarnywith releases every 6 months
10:47.22keriooh man, httpredir.debian.org is so weird
10:47.25KotCzarnyi bet 1.5ftdev would be enough for a release in 5 year period
10:47.36keriothe mirror keeps changing as apt-get downloads packages
10:48.37kerioanyway, NOTE: WE ANTICIPATE THAT 1.0.0t AND 0.9.8zh WILL BE THE LAST RELEASES FOR THE 0.9.8 AND 1.0.0 VERSIONS AND THAT NO MORE SECURITY FIXES WILL BE PROVIDED (AS PER PREVIOUS ANNOUNCEMENTS). USERS ARE ADVISED TO UPGRADE TO LATER VERSIONS.
10:49.06kerioit's a shame we're going to upgrade openssl to something without chacha20, but meh
10:49.11keriomaybe they'll backport that onto 1.0.2
10:49.37kerio(it's the only reasonable non-hardware-accelerated cipher)
10:54.01Wizzupkerio: what do you mean
10:54.08Wizzupkerio: why would people not pick 1.0.2?
10:54.20kerio1.1.0 will support chacha20-poly1305
10:54.41kerioidk about 1.0.2
10:54.42Wizzupor get libressl to make it more messy :P
10:54.52Wizzupkerio: pretty sure it supports it
10:54.55keriothat's also an option, since we're breaking abi-compatibility anyway
10:55.00kerio1.0.2 mainline doesn't
10:55.11keriothere's a 1.0.2 fork that does, so it's definetely possible
10:55.19WizzupHost * Ciphers aes256-ctr,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com MACS hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com KexAlgorithms curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256
10:55.33keriothat's ssh you dolt
10:55.36Wizzupworks on 1.0.2 (openssl) and openssh7.1
10:55.42WizzupDoesn't ssh use openssl for this?
10:55.46kerionot for chacha20
10:55.54kerioin fact, it's the only available cipher if you compile without libcrypto
10:55.57WizzupRight - you mean for TLS?
10:56.00kerioyep
10:56.04Wizzupokay, my bad :)
10:56.24kerioalso you should definetely put chacha20-poly1305 as your first cipher
10:56.39kerioin the ssh protocol the client decides
10:56.51WizzupI am not unhappy with AES ;-)
10:57.12kerioas implemented by openssh, chacha20poly1305 is slightly more secure
10:57.16keriothe packet sizes are also encrypted
10:57.26keriowhich is pretty crazy
10:57.42keriois this on your computer or your n900?
10:57.53kerioif it's your computer then using aes is understandable
10:58.04kerio(but you should put aes-gcm over aes-ctr)
10:58.32WizzupThe latter is my arm chromebook
10:59.16keriothen you should most definetely put chacha20 before aes
10:59.35kerioaes is pretty crummy without hardware acceleration :c
11:00.54kerioWizzup: it's not a conclusive test, but if you manage to find a libressl or an openssl 1.0.2-chacha, could you run `openssl speed -evp aes-128-gcm` and `openssl speed -evp chacha20`?
11:01.11keriosorry, openssl speed -evp chacha
11:01.51KotCzarnyhehe, and to be even more n900-realistic, do it without hardfloat
11:02.15Wizzupn900 supports hf
11:02.18Wizzupit's just that maemo is not
11:02.22KotCzarnyyes
11:02.27kerio>floats
11:02.29kerio>crypto
11:02.32keriou wot m8
11:03.20WizzupI will start using libressl when gentoo unmasks it for arm
11:03.28Wizzupif I was on intel I'd already start using it.
11:03.45keriothere's some software compatibility issues
11:03.52kerioit's always pretty simple stuff, but still
11:03.52WizzupNot enough to bother me ;-)
11:04.04kerioa missing include here, a missing #ifdef there
11:04.17Wizzupgentoo patched/fixed most iirc
11:04.51kerioi would imagine that openbsd fixed most
11:05.05kerioconsidering that they don't have openssl anymore
11:05.08kerio:3
11:05.53*** join/#maemo vahe (~funtoo@130.193.124.135)
11:06.22kerioWizzup: `openssl speed -evp aes-128-gcm` on your chromebook?
11:07.26WizzupThe 'numbers' are in 1000s of bytes per second processed.
11:07.27Wizzuptype             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
11:07.27Wizzupaes-128-gcm      25792.88k    30015.20k    36974.36k    39912.37k    40617.98k
11:08.55keriodear lord
11:09.25Wizzup?
11:09.26keriothat right there is the reason why google is using chacha20-poly1305 for tls
11:09.32Wizzup:)
11:09.45WizzupI have four cores, and never push out this much data anyway
11:09.47kerioyou're getting 40MB/s, i'm getting 1.3GB/s
11:09.52WizzupAES-NI.
11:09.55WizzupNo doubt
11:09.58kerioindeed
11:09.59KotCzarnyaes-128-gcm      38158.76k    42308.12k    43319.21k    43606.70k    43929.94k
11:10.02KotCzarnythis is on coreduo
11:10.13KotCzarnywhich is, well, old
11:11.00kerioWizzup: do you have a toolchain on the device?
11:11.01KotCzarnyaes-128-gcm       8372.02k     9347.86k     9743.87k     9846.78k     9874.09k
11:11.09KotCzarnyand this is on banana pi r1
11:11.15KotCzarny(clocked at 720mhz)
11:11.21keriooh are we racing to the bottom?
11:11.47Wizzupkerio: the chromebook?
11:11.48kerioaes-128-gcm       7643.64k     9001.69k     9388.59k     9547.02k     9571.08k
11:11.51kerioon sheevaplug
11:11.52kerioWizzup: yea
11:12.08WizzupIt runs gentoo hardened
11:12.17kerioyou should totally compile libressl and run the benchmarks to fulfill my curiosity
11:12.18Wizzup(so, yes)
11:12.24Wizzupwell, later :)
11:12.29kerionu :c
11:12.31Wizzupif I have time I will first set up SB and IDA
11:12.38keriohttp://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.3.1.tar.gz
11:12.49KotCzarnyno libressl in debian repos
11:12.50kerioyou don't need to install it at the system level
11:12.58keriojust compile it and run ./apps/openssl speed -evp chacha
11:13.15kerioKotCzarny: how's the bananapi?
11:13.24kerioi was kinda interested in the router-like one
11:13.27KotCzarnyamazingly stable
11:13.32keriothe one with space for a 3.5" hd
11:13.35KotCzarnyi have only 10mbit at home tho
11:13.41Wizzupp.s. the chromebook is cheap http://linux-exynos.org/wiki/Samsung_Chromebook_2_XE503C32
11:13.49Wizzupso you can always get one yourself ;-)
11:13.53KotCzarnybut dont get banana
11:13.58KotCzarnyit has too many issues
11:14.06WizzupKotCzarny: tolya :)
11:14.07KotCzarnygrab olinuxino and gbit switch/router
11:14.31KotCzarnywizzup, but works good enough for me, i've already replaced my  2x x86 + 2x gbit switch setup
11:14.42Wizzupwhat kernel version?
11:14.46kerioKotCzarny: but it's got linux right in the name
11:14.49KotCzarnynow i have single machine that does routing, switching, audio, nas etc
11:14.54kerioand linux sucks
11:14.59KotCzarnywizzup: legacy
11:15.05KotCzarnyLinux lamobo 3.4.110-sun7i #2 SMP PREEMPT Sat Nov 28 19:53:25 CET 2015 armv7l GNU/Linux
11:15.05WizzupKotCzarny: 3.4.x
11:15.07Wizzupk
11:15.24keriohm, the olinuxino is an A8 at least
11:15.26KotCzarnyi'll switch to mainline somewhere around 4.5
11:15.47KotCzarnyas it will have audio and other features done for my banana
11:16.16Wizzupkerio: olinuxino's are allwinner a10 and a20 (so probably A8)
11:16.19KotCzarnykerio, you have basically 2 options, if you want sata, grab a20 based thingie
11:16.24KotCzarnya20 is a7
11:17.37KotCzarnythe other option would be getting a83t based (without single hub and 4 real usb ports) and raiding on usb-uas
11:17.56keriohm, considering that i already have a usb drive...
11:17.57KotCzarnyunless you have dedicated nas box
11:18.09KotCzarnyusb drive < uas-usb
11:18.35KotCzarny30-35M < 35-40M
11:18.36kerioyeah but having real usb ports still helps
11:18.45KotCzarnyhttp://linux-sunxi.org/A20
11:18.48kerio...are you missing a zero
11:19.17KotCzarnyits all on usb2
11:19.29KotCzarnyit will be even more of a difference on usb3
11:19.40kerioright
11:19.51Wizzupkerio: the olinuxino things are quite well built imho
11:19.53Wizzupnicer than most others
11:20.12kerioi guess i'll wait
11:20.17kerioi'm changing internets soon
11:20.19Wizzupbut get the proper LIME ones
11:20.22kerioidk what i'm getting
11:20.27keriobut i'll likely have to use the ISP-provided modem
11:20.32Wizzuphttps://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2/open-source-hardware
11:20.35Wizzupthis is the one I use
11:21.04KotCzarnyhttp://linux-sunxi.org/Olimex
11:21.34keriohm
11:21.43keriowhy would i buy something like this instead of a beaglebone, though?
11:21.54Wizzupbeaglebone is way less powerful, but also cute
11:22.10KotCzarnyolimex is the only real oshw company
11:22.17keriohm, dual core A7
11:22.18KotCzarnyand they support their boxes
11:22.22keriooh and sata
11:22.43kerioyeah ok this a20 olinuxino is the current winner to replace my current home server
11:22.54KotCzarnya20 has inherent problem with sata, max is 200/50M (read/write)
11:23.04kerio:\
11:23.18KotCzarnyit affects all boxes, not only bananas
11:23.48WizzupKotCzarny: weird that the write would be slower than the read
11:23.50KotCzarnybut those boxes are so cheap you should get one just for funsies
11:23.51WizzupKotCzarny: are you sure that is with DMA?
11:24.07Wizzupalso I use several HDDs in raid1 btrfs over USB2. still no performance issues.
11:24.18kerioah yes
11:24.23kerioi also really want freebsd support
11:24.25WizzupI guess I don't have a need to write 50MB+/s
11:24.31WizzupFreebsd supports some allwinners for sure.
11:24.39kerioi need to check that
11:24.40WizzupI also know they support some exynos' things
11:24.46keriobecause i'm not going to use those silly toy filesystems
11:24.47KotCzarnywell, my old x86 (c7@1ghz) also did ~40-50M/s max
11:24.59KotCzarnyand its enough for my need, so its not that i need more
11:25.02kerioalthough 1gb of ram is very little :c
11:25.02KotCzarny*needs
11:25.03Wizzupkerio: *cough*
11:25.12Wizzupkerio: for toy filesystems it is enough
11:25.13Wizzup;-)
11:25.17kerioi have seen the light, Wizzup
11:25.34KotCzarnyyou can run btrfs with mainline on them
11:25.36keriozfs is my personal lord and saviour
11:25.39Wizzupthat's fine, no need to rant about it to others :)
11:25.46WizzupI know zfs is very nice
11:25.56kerioit eats ram like crazy, though
11:25.58Wizzupit's just that btrfs is way easier to set up and I want a secure system
11:26.03Wizzupfreebsd doesn't offer half as much as grsecurity+linux does
11:26.16kerioayy lmao
11:26.50keriohm, do i care about the 4gb flash on the olinuxino
11:27.12KotCzarny+sd slot
11:27.19*** join/#maemo eijk (~eijk@x55b2d3f0.dyn.telefonica.de)
11:27.22Wizzupthere is 4gb nand if you pay more
11:27.29KotCzarnynot that much more
11:27.29Wizzupbeware: I do not yet have nand working on mainline
11:27.34Wizzupand on the legacy kernel it's a bit of a pain.
11:27.42Wizzupso I stick to sd cards only for now
11:27.51*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
11:28.18KotCzarnymy system is still in customizing state
11:28.31KotCzarnybut it works amazingly well
11:28.44KotCzarnythought that it will be unstable, but it's not
11:28.53kerioKotCzarny: no, the model without the nand still has a usd slot
11:29.00Wizzupyes
11:29.07KotCzarnykerio, yes, and one with nand also has sdslot
11:29.13KotCzarnywhich means more storage options
11:29.28kerioi don't see it listed here https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2-4GB/open-source-hardware
11:29.55keriojust the one microsd slot
11:30.47KotCzarnyyes, nand + microsd slot + sata + usb
11:31.13KotCzarnyanother cute option is that they have onboard charger for li-ion
11:31.38KotCzarnyi already ordered me 18650 and a holder
11:32.30KotCzarnyand if you are silly enough, you can add lcd (with touchscreen) and keyboard
11:35.37KotCzarnybut the best part is having current glibc/gcc
11:36.42KotCzarnyalso, r1 switch is supporting hw vlans, which is nice for my crazy config
11:36.55KotCzarny2x wan, 3x lan
11:38.46KotCzarnywizzup, do you know how durable is that nand?
11:39.11Wizzupno, I never used it. I never trust nand much
11:39.32KotCzarnywhere did you put your / then?
11:39.36KotCzarnysata?
11:39.41Wizzupfor some? SD. For others: SSD
11:47.54*** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au)
11:49.29jonwilhi
11:54.16jonwilpali: ping
11:55.26Palijonwil: pong
11:57.11KotCzarnyreal    21m51.443s                                                                                  user    36m15.250s
11:57.17KotCzarnyhah, libressl compiled
11:58.12jonwilneat that people are playing with newer openssl bits
11:59.16KotCzarnykerio: aes-128-gcm       8367.81k     9408.64k     9741.23k     9845.76k     9865.90k
11:59.35KotCzarnyalmost the same result
11:59.50KotCzarnyerm, im stupid
12:00.13KotCzarnyaes-128-gcm       4879.81k     5268.84k     5401.51k     5449.46k     5444.95k
12:00.38KotCzarnychacha           15944.60k    21795.50k    22880.68k    23189.16k    23270.74k
12:01.03KotCzarnyit was compiled without any tweaking tho (ie, default cflags)
12:12.00*** join/#maemo darkschneider (~gab@93-32-51-166.ip32.fastwebnet.it)
12:17.26*** join/#maemo krnlyng (~liar@77.117.21.205.wireless.dyn.drei.com)
12:29.34KotCzarnykerio: with some flags added (-Ofast etc)
12:29.38KotCzarnyaes-128-gcm       6009.51k     6766.70k     7017.64k     7087.10k     7102.46k
12:29.41KotCzarnychacha           16193.31k    22999.27k    24285.27k    24663.72k    24778.07k
12:30.16kerioKotCzarny: can you compare `speed -evp aes-128-cbc` for libressl and the builtin openssl?
12:31.12KotCzarnylibressl: aes-128-cbc      12619.07k    14438.61k    15055.19k    15214.25k    15248.04k
12:31.21KotCzarnyopenssl: aes-128-cbc      14222.51k    17020.05k    17958.66k    18199.55k    18323.78k
12:31.28kerioweird as fuck
12:32.37KotCzarnyopenssl             1.0.1k-3+deb8u armhf
12:32.41keriooh
12:32.47kerioi thought this was on n900
12:32.56KotCzarnynope, all on bpi-r1
12:32.58kerioyea then it's likely just a matter of enabling optimizations
12:33.11keriolike -O3 -funroll-loops and the like
12:34.16jonwilanyone know where I can get libgtkadi-dev (for maemo) from? Its not in the SDK repos and I cant get libgtkadi to compile locally for some reason
12:34.37KotCzarnythe reason is probably too old libgtk
12:34.49KotCzarnytry compiling newer libgtk and linking statically
12:35.17jonwilno, I am using libgtkadi from maemo repos
12:35.28jonwilmaemo SDK repo includes libgtkadi source and binary
12:35.32jonwilbut no libgtkadi-dev package
12:35.35jonwiland I need that
12:36.01KotCzarnythen just compile it on pc, do make DESTDIR=/tmp/adi install and grab the headers?
12:37.24KotCzarnykerio, i would try sb build, but it's on the disconnected hdd for now
12:38.40KotCzarnyalso, i think one could expect results ~20% lower on n900 and ~30% higher on stock clocks for a20
12:51.52*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
13:07.19ceenei'm not happy anymore with my ssl build :(
13:07.27ceenei'm getting into problems i don't know how to solve
13:15.29*** join/#maemo Bono_NL (~Bono@dhcp-077-250-079-027.chello.nl)
13:41.21jonwilhttp://talk.maemo.org/showthread.php?p=1492799#post1492799
13:42.42bencohhmm, why a new thread?
13:42.51bencoh(but thx nonetheless :)
14:01.42*** join/#maemo krnlyng (~liar@77.116.105.85.wireless.dyn.drei.com)
14:04.35*** join/#maemo Vajb (~Vajb@85-76-9-104-nat.elisa-mobile.fi)
14:06.03*** join/#maemo Mekkis (~Mekkis@2a02:2a38:1:571:a::2)
14:08.24keriowhy would there be extra maemo patches apart for maybe the packaging ones
14:11.19*** join/#maemo LauRoman (~LauRoman@5-14-87-59.residential.rdsnet.ro)
14:30.33*** join/#maemo till (~till@vispillo.org)
14:40.16ceeneok, i got openssl to build .deb packages on sbox-FREMANTLE_X86 :)
14:40.39ceenenow i'm happier than an hour ago
14:40.46KotCzarny:>
14:43.47bencohwhy on _X86?
14:44.04ceenebecause why not
14:44.09ceenethat's where i started
14:44.13bencohah
14:44.17bencohokay
14:44.34ceenei've just changed to sbox-FREMANTLE_ARMEL and it in facts seems to finish early with some error
14:46.33ceenetest BN_mod_exp_mont_consttime
14:46.33ceeneunable to dump 00150800
14:46.33ceenemake[2]: *** [test_bn] Error 126
14:56.33bencohreminds me of https://mg.pov.lt/maemo-ssu-irclog/#maemo-ssu.2015-01-24.log.html (see bottom)
14:58.01ceenei think i've just disabled unit testing
14:58.14ceenemaybe it's something related to the cross compilation and scratchbox
14:58.35KotCzarnyfailing tests isnt a good sign tho
14:58.35ceenegotta go now, i'll leave that building and maybe later tonight i can report some progress
14:59.31bencohKotCzarny: I'm quite sure it's qemu-related
14:59.51KotCzarnyits a possibility
15:00.02KotCzarnysb's qemu is old
15:00.18KotCzarny(i've managed to use current one with a little hack)
15:18.36*** join/#maemo at1as (~at1as@kurios.r4780y.com)
15:22.51*** join/#maemo lobito (~lobito@190.177.219.60)
15:35.21*** join/#maemo FlameReaper-PC (~FR@115.132.88.188)
15:41.31*** join/#maemo zGrr (~GrR@user-46-113-167-78.play-internet.pl)
15:44.46zGrrmoin :)
16:03.05*** join/#maemo krnlyng (~liar@77.116.84.135.wireless.dyn.drei.com)
16:27.03*** join/#maemo FReaper-PC (~FR@115.132.88.188)
16:33.56*** join/#maemo sunshavi (~user@190.234.106.189)
16:57.52*** join/#maemo lobito (~lobito@190.177.195.61)
17:07.25Paliehm.. I totally forgot, perl6 was released!!!
17:07.27Palihttps://twitter.com/TimToady/status/680511168713064448
17:07.37KotCzarnywho uses perl anyway?
17:07.45Palihttp://perl6.org/
17:07.54PaliKotCzarny: me :-)
17:07.57KotCzarny:)
17:09.59Pali...language with full unicode support
17:10.17KotCzarnyhave you ever tried coding in mandarin?
17:10.38Paliunicode string representail
17:10.43Pali*representation
17:11.02KotCzarnyon another note, getting segv in ao_shutdown(), wth
17:15.42kerioPali: python had unicode support for ages
17:16.10Palikerio: but not unicode graphemes
17:16.28KotCzarnywho needs unicode anyway (apart from teens using icon ilanguage)
17:16.36kerioPali: as in?
17:16.44Palikerio look: http://jnthn.net/papers/2015-spw-nfg.pdf
17:17.33PaliU+0044 U+0323 U+0307 is LATIN CAPITAL LETTER D COMBINING DOT BELOW COMBINING DOT ABOVE
17:17.39Paliit is one letter
17:17.58keriothat's three codepoints
17:18.09kerio:\
17:18.13Palibut one grapheme
17:18.16kerioso what
17:19.54PaliKotCzarny: everybody who does not use just ascii
17:20.10KotCzarnypali, dont mind me, i'm just kidding
17:20.15kerioyeah that's pretty much everyone except english speakers :|
17:20.38keriolike, native english speakers with non-foreign origin on their paternal side
17:20.41*** join/#maemo krnlyng_ (~liar@77.117.125.166.wireless.dyn.drei.com)
17:20.51KotCzarnybut seriously, unicode attempted to be new chinese
17:21.02KotCzarnyie. representing everything it can
17:21.33KotCzarnyand introducing so much redundancy in the process
17:21.34keriounicode represents everything written
17:21.46kerioand it doesn't care about what you think is redundant
17:21.46KotCzarnykerio, how about pictograms?
17:21.50KotCzarnythose are drawn, not written
17:22.04kerioi think there's linear A characters
17:22.12kerioand those are dubious
17:22.21keriobut then again, there's also emoji
17:22.23kerio¯\_(ツ)_/¯
17:22.40KotCzarnytold you, drawings
17:22.46Paliツ is japan
17:23.03Paliand others ascii
17:24.17kerioidk about the ¯
17:24.58*** join/#maemo sparetire_ (~sparetire@unaffiliated/sparetire)
17:31.10Siceloi may dust off my SB, but not making solemn promise, lol
17:31.19Siceloaw .. sorry about that
17:31.59*** join/#maemo Hebi (penis@uk.co.foxbnc.co.uk)
17:32.37*** join/#maemo xorly (~xorly@ip-86-49-15-121.net.upcbroadband.cz)
17:53.30*** join/#maemo pozitron (nu@gateway/vpn/mullvad/x-hksklgjsebfpktti)
17:56.40*** join/#maemo futpib (~futpib@37.113.231.27)
18:03.53*** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr)
18:20.01*** join/#maemo lobito (~lobito@190.177.195.61)
18:26.25*** join/#maemo eMHa (~mh@p579DB49C.dip0.t-ipconnect.de)
18:28.06*** join/#maemo krnlyng (~liar@77.117.107.243.wireless.dyn.drei.com)
18:37.14*** join/#maemo shamus (~shmaus@ip-206-192-194-12.marylandheights.ip.cablemo.net)
19:01.20*** join/#maemo Vajb (~Vajb@85-76-8-195-nat.elisa-mobile.fi)
19:17.50*** join/#maemo Vajb (~Vajb@85-76-161-212-nat.elisa-mobile.fi)
19:19.42*** join/#maemo smhar (~salman@178.132.44.178)
19:21.18*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
19:21.50*** join/#maemo arossdotme (~zxy@host-84-13-235-151.opaltelecom.net)
19:32.40*** join/#maemo krnlyng (~liar@77.116.29.61.wireless.dyn.drei.com)
19:43.55ceeneopenssl has built for armel, provided tests are skipped
19:44.23ceenei guess i should check why the test fails and try to fix it
19:44.45ceeneor at least run the test on the n900, in case it's qemu's fault
19:44.46KotCzarnybuild on device and check?
20:15.49*** join/#maemo pozitrono (~nu@46.166.190.200)
20:15.59kerioDocScrutinizer05: do you have a source on the OMAP4 randomly missing interrupts?
20:17.59DocScrutinizer05well, I heard the whole sad story while fixing/patching the drivers for an interface which hung each time the IRQ got lost
20:18.19bencohhmm
20:19.40DocScrutinizer05I also *heard* that TI closed the ticket as "WONTFIX, gets fixed in $omap5 "
20:19.56kerioDocScrutinizer05: FIQ heard that from me and wanted an actual source
20:20.20DocScrutinizer05sorry, I couldn't find any sources for it myself
20:20.57bencohwell, if its a hw bug, you can only write a workaround anyway
20:21.20DocScrutinizer05err, wait. I *think* I've seen some "wake IRQ getting lost while PVR active" or similar ticket a long time ago
20:21.22bencohyou cant really "fix" it
20:21.34DocScrutinizer05bencoh: yep
20:23.20*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
20:23.51DocScrutinizer05anyway we inlemented a workaround in modem, repeating the IRQ wiggling of http://mipi.org/specifications/high-speed-synchronous-serial-interface-hsi when there occurred a timeout
20:24.11bencoh"we"?
20:24.18DocScrutinizer05ST-E
20:25.43bencohST electronics?
20:25.46DocScrutinizer05we deployed that fix/patch/botch to half a dozen customers who used omap4 in their phones together with our modem
20:25.58DocScrutinizer05ST-Ericsson
20:26.04bencohah, right
20:27.11DocScrutinizer05the bug tickets always been "your modem stops talking to our APE processor" - sure it stops talking when the APE doesn't react to an IRQ
20:29.02DocScrutinizer05actually the thing would recover when APE would start talking via HSI. But since it usually doesn't, eventually the 'syslog' of the modem was full and the modem 'coredumped'
20:30.33DocScrutinizer05and to make things more funny, since 'syslog' was via HSI to APE and got stored on APE side, never anything useful shown up in 'syslog' before the modem 'coredumped'
20:32.30*** join/#maemo krnlyng (~liar@77.116.25.94.wireless.dyn.drei.com)
20:32.56KotCzarnysounds like omap4 is 'dont buy it' flag
20:34.36ceenethe tests run fine on the n900!
20:35.02ceenewe got openssl1.0.2! :D
20:35.24KotCzarnyceene, compile ssh against it and test?
20:36.39ceenethat's probably quite complex. i want to try first with something simpler, telnet-ssl or something like that, socat or whatever, that'll let me test it against known https siites
20:36.40DocScrutinizer05\o/
20:36.54KotCzarnythere is always sconnect
20:36.55ceenebut it should definitely work :)
20:37.05KotCzarnyuse it to connect to some https
20:37.08ceenefor today that's gonna be all
20:37.15DocScrutinizer05kerio: does this info help you?
20:37.41ceenetomorrow I'll ask whou should I talk to in order to get this for everyone
20:37.43kerioceene: you have the openssl tool itself
20:37.43KotCzarnyalso, keep in mind openssl1.1.0 is to be released soon, so why not jump onto newer/better/shinier boat
20:38.13kerioKotCzarny: because nothing supports 1.1.0 yet
20:38.24kerioand 0.9.8 is EOL
20:38.25KotCzarnykerio, is it api incompatible ?
20:38.29DocScrutinizer05kerio: if FIQ wants to know more, he rather queries me, I already was too talkative about details
20:38.49kerioDocScrutinizer05: oh, it's seekrit stuff?
20:38.59DocScrutinizer05well, sort of
20:39.01kerioanyway, ty
20:39.13DocScrutinizer05yw
20:39.14kerioKotCzarny: yes
20:39.17ceenewell, I'll be back tomorrow, we'll get this thing working for everyone!
20:39.37ceeneif someone can tell jonwil he'll be happy too
20:39.46ceenecya!
20:40.26DocScrutinizer05I only told you hearsay mostly, which is OK. I however shouldn't disclose details of my own work at employers
20:41.45KotCzarnyVersion 1.0.2 will be supported until 2019-12-31.
20:41.54KotCzarnyoh, well, at least that buys us some time
20:42.18DocScrutinizer05even the MIPI HSI specs are 'sekrit'
20:42.54bencohceene: "openssl s_client"
20:43.01DocScrutinizer05>>Specifications are available to MIPI members only<<
20:43.19bencohthat'll be simpler than trying to build socat or any other ssl-dependant tool
20:45.20*** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps)
20:45.59*** join/#maemo githogori (~githogori@c-73-70-12-67.hsd1.ca.comcast.net)
20:47.00*** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil)
20:49.28FIQI see that I've been highlighted
20:49.58FIQDocScrutinizer05, sorry, I didn't mean to ask if it is secret stuff
20:50.14FIQI just wanted to read a bit more about it is all
20:52.54DocScrutinizer05not secret, just the usual "confidential"
20:52.56*** join/#maemo strohalm (~smoofi@unaffiliated/strohi)
20:53.51DocScrutinizer05which I dunno if it's 2 or 3 or even 5 years I'm supposed to act accordingly
20:55.34DocScrutinizer05I just wonder why I never found any SiErr notice from TI about all that
21:39.33*** join/#maemo Oksanaa (~Wikiwide@Maemo/community/ex-council/Wikiwide)
21:44.56OksanaaHmm, fsck 'corrected' 3 files, and seem to think that there is nothing else to be done. Suspiciously fast... Going into reboot to have MyDocs mounted back
21:51.13*** join/#maemo Oksanaa (~Wikiwide@Maemo/community/ex-council/Wikiwide)
21:51.56OksanaaOf course, the 'corrected' files are not-working henceforth. Not sure if they were working before that, though...
21:55.41*** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps)
21:55.50OksanaaHmm, recovered one file by web-searching for the info again. Others two, vidos recorded by device's camera, would @ave no such luck.
21:56.04*** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au)
21:57.57jonwilhi
21:58.56Oksanaahello
22:14.50*** join/#maemo sunshavi (~user@190.234.106.189)
22:19.08*** join/#maemo krnlyng (~liar@178.114.97.66.wireless.dyn.drei.com)
22:31.56jonwilwe need to find someone who knows enough about openssl to figure out just what the local patches in the maemo openssl0.9.8n are for and which ones we would need going forward...
22:32.22keriohow many patches are there?
22:32.43jonwilI dont know what differences/patches there are
22:33.47jonwilI am going to take a look and find out
22:40.16*** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
22:50.08jonwilhmmm, I cant make sense of all this
22:57.18OksanaaNice, links?
22:58.09jonwilnice what?
23:08.35NIN101well one of them is actually harmful
23:09.08NIN10112_valgrind.patch
23:10.53*** join/#maemo Cor-Ai (~cor-ai@c-9397e355.06-922-7570702.cust.bredbandsbolaget.se)
23:19.02*** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
23:24.28*** join/#maemo sunshavi (~user@190.234.106.189)
23:38.34*** join/#maemo Cor-Ai_ (~cor-ai@c-9397e355.06-922-7570702.cust.bredbandsbolaget.se)
23:45.59OksanaaNice idea, to upgrade openssl. And opening links is way easier than finding them...
23:59.28sunshavimmm, openssl. When You guys finish. I can port it to n800 too

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