<P-G>
Even in the middle of a normal paragraph, just those words are capitalised.
<P-G>
It works in voice. :p
dal2 has quit [Quit: Leaving.]
<DocScrutinizer05>
btw the above is particularly shabby, he's using "free" for "free as in beer" on a conference about FOSS stuff where everybody automatically assumes the "free as in speech" meaning
<DocScrutinizer05>
I sometimes wonder if he actually speaks about the bottle in his hand ;-)
<DocScrutinizer05>
"it's open source software - you get it for free"
<DocScrutinizer05>
what a nonsense statement is this really now?
<P-G>
Funny guy.
<DocScrutinizer05>
is this a "we have lots of (paying commercial) customers asking for all sorts of weird features. You on the other hand are not paying, you get it for free so STFU nd don't pester about what we do with linux"?
<DocScrutinizer05>
P-G: you know who's that funny guy, right?
<P-G>
I don't.
<P-G>
I don't know people. :(
<DocScrutinizer05>
Lennart Poettering
<DocScrutinizer05>
lead propagandist for systemd
<P-G>
And a PulseAudio developer?
<DocScrutinizer05>
yes
<DocScrutinizer05>
and avahi and...
<P-G>
Reading the "Controversies" section now.
<P-G>
This guy seems like a jerk.
<P-G>
And he works for Red Hat?
<DocScrutinizer05>
yes
<P-G>
I'm not really comfortable with Red Hat either.
<DocScrutinizer05>
well, that's what Canonical made out of a Project that started with sourcing several millions during a few days and somewhat triggered Neo900 idea, after almost 2 years
<DocScrutinizer05>
I can promise that our results are better and in shorter time
<DocScrutinizer05>
Canonical always was about hijacking Linux, not supporting its principles
<DocScrutinizer05>
and Mediatek... :-X
<DocScrutinizer05>
Prolly the two are the ideal partnership
dal2 has quit [Ping timeout: 256 seconds]
<DocScrutinizer05>
next step: conference with RH about how to conquer the world and/of linux
<drathir>
wonder if they buy licensing right or something lkike that...
dal2 has joined #neo900
<DocScrutinizer05>
nah, mediatek delivers the kernel (+ lots of closed crap, incl whole radio stack aka "modem firmware) to canonical
<DocScrutinizer05>
since basically linux kernel runs in a container/VM under the modem OS
<DocScrutinizer05>
and mediatek gives the finger to any GPL and licencing in general, as long as it's not THEIR license which is "you CANT"
<bencoh>
16:47 <+DocScrutinizer05> since basically linux kernel runs in a container/VM under the modem OS
<bencoh>
wait, what ?
<DocScrutinizer05>
see Jolla, the poor sods are not even allowed to distribute the mediatek blobs packaged into a flasher tool so users could properly coldflash their devices
<bencoh>
jolla, mediatek ? wait, what² ?
xes has quit [Quit: Lost terminal]
<DocScrutinizer05>
jolla snapdragon
<DocScrutinizer05>
it's all the same
<DocScrutinizer05>
regarding this aspect
<DocScrutinizer05>
some non-free "secure" boot code ensures that effective protection for the otherwise in "user RAM" and on "user CPU" modem firmware gets established
<DocScrutinizer05>
when modem and linux share RAM and CPU, it's basically mandatory that the modem OS has the absolute control
<bencoh>
last time I checked, snapdragon is qualcomm :)
<bencoh>
and ... the rest is stuff we all agree on I think
<DocScrutinizer05>
but yeah, sorry s/to distribute the mdeiatek blobs/the modem formware blobs/
<bencoh>
shouldn't you be afk/recovering ? :)
Dejavu_Glitch is now known as OlgoiKhorkhoi
<DocScrutinizer05>
that got cancelled
<bencoh>
>_>
<DocScrutinizer05>
due to pressing affairs and poor weather
<DocScrutinizer05>
~weather eddn
<infobot>
Nuernberg, Germany; (EDDN) 49-30N 011-03E 318M; last updated: 2015.03.18 1550 UTC; Dew Point: 30 F (-1 C); Pressure (altimeter): 30.18 in. Hg (1022 hPa); Relative Humidity: 33%; Temperature: 59 F (15 C); Visibility: greater than 7 mile(s); Wind: Variable at 3 MPH (3 KT)
<DocScrutinizer05>
while e.g. on fuerte ventura or also in Gibraltar the weaher is even worse
<DocScrutinizer05>
at least that been the forecast last week, for this week
Oksana has quit [Ping timeout: 244 seconds]
<DocScrutinizer05>
hellekin has an awesome signature: >>We are free to share code and we code to share freedom<<
Oksana has joined #neo900
OlgoiKhorkhoi has quit [Quit: Leaving]
joecool has quit [Ping timeout: 256 seconds]
ddark has joined #neo900
paulk-collins has joined #neo900
vakkov has quit [Ping timeout: 244 seconds]
vakkov has joined #neo900
paulk-collins has quit [Remote host closed the connection]
<DocScrutinizer05>
no, since PR1.2 iirc you need to flash both COMBINED *and* VANILLA
<DocScrutinizer05>
and even that will not *reset* the code to default 1234, only disable it afaik
<DocScrutinizer05>
which is actually a bug
<DocScrutinizer05>
the trick is the echo root:$(grep -A 13 lock_code /dev/mtd1|tail -1): line
<DocScrutinizer05>
which btw only works like that in busybox, not with proper unix-tools
xes has joined #neo900
<drathir>
DocScrutinizer05: the disable it also is good solution...
<DocScrutinizer05>
however meanwhile there are more sophisticated approaches known than just reflashing. E.G. you could boot into a rescue system and then do whatever needed to crack or disable the lock code, and of course also rescue all data from all partitions on the N900
<kerio>
you can just crack it
<kerio>
it's numbers-only, and crypted with crypt()
<DocScrutinizer05>
while the above echo root:$(grep -A 13 lock_code /dev/mtd1|tail -1): trick only works when you still have access to the device
<DocScrutinizer05>
so yet another possible attack vector would be to write "12345" to the CAL record
<DocScrutinizer05>
to do that we lack proper CAL manipulation tools particularly in a rescue system
XDS2010_ has quit [Ping timeout: 265 seconds]
XDS2010_ has joined #neo900
dal2 has joined #neo900
<drathir>
DocScrutinizer05: pali patches multiboot and backup menu always save the ass...
<drathir>
DocScrutinizer05: and ofc Your liblary in the brain, thanks a lot... writed solution for later usage...
<drathir>
and yea crac it its a seconds... when hash extracted...
<DocScrutinizer05>
:nod:
<drathir>
DocScrutinizer05: its a complement...
<DocScrutinizer05>
:-)
<drathir>
ofc iin case if that not secured by root login and password will be really scary...
<DocScrutinizer05>
"ssh client and server" package sets proper root password
<DocScrutinizer05>
on install time
<drathir>
DocScrutinizer05: You knowledge is amazing and im alwaays appreciated about all ideas and solutions...
<drathir>
DocScrutinizer05: yes correct...
<DocScrutinizer05>
thanks :-)
wazrus has joined #neo900
<drathir>
DocScrutinizer05: me thanks too...
unclouded has quit [Ping timeout: 256 seconds]
unclouded has joined #neo900
wazrus has quit [Quit: Lost terminal]
Oksana has quit [Ping timeout: 264 seconds]
Oksana has joined #neo900
freemangordon has quit [Quit: Leaving.]
phre4k has joined #neo900
norly has joined #neo900
freemangordon has joined #neo900
che11 has quit [Ping timeout: 240 seconds]
che1 has joined #neo900
ddark has quit [Ping timeout: 256 seconds]
dal2 has quit [Quit: Leaving.]
dal2 has joined #neo900
mvaenskae has joined #neo900
joecool has joined #neo900
joecool has quit [Ping timeout: 256 seconds]
che1 has quit [Ping timeout: 245 seconds]
joecool has joined #neo900
Pali has quit [Remote host closed the connection]
<Oksana>
(linux kernel runs in a container/VM under the modem OS) Why is that? I would have expected - for RAM-CPU-sharing devices - Modem and Linux to be like two tasks of equal priority, multi-tasking on same RAM-CPU-whatever...
<kerio>
because that requires cooperation between linux and modemos
<kerio>
and to do that, you either violate the gpl, or you disclose intimate details of how modemos works
paulk-collins has quit [Quit: Quitte]
<DocScrutinizer05>
when both would be equal tasks then there needs to be a superviser, and that again lives in modemOS
<DocScrutinizer05>
unless you actually suggest both doing cooperative multitasking, which panned out so well for windows2 ;-)
<Oksana>
Why cannot there be a third thingie, which puts both ModemOS and LinuxOS into boxes?
<DocScrutinizer05>
we actually don't know if there is
<kerio>
that still counts as modemOS
<DocScrutinizer05>
anyway such thingie will be a supervisor that also lives in modem space
<Oksana>
You could even disclose intimate details of supervisor - it would not disclose details of ModemOS...
<DocScrutinizer05>
tbh I am not interested in any "intmate details" of that thingie
<DocScrutinizer05>
I am not allowed to change it anyway
<DocScrutinizer05>
so what interesting stuff i'd want to know about it?
<DocScrutinizer05>
it for sure won't tell me the cert it's using to make sure the modemOS is genuine and untampered
<DocScrutinizer05>
and it won't tell me about means of modemOS to access and mangle linux userland
<DocScrutinizer05>
the DMA that's transferring data from linux land to modem land (or the MMU mapping that swaps memory pages, or whatever method they use) will definitely be under control of modem and/or "the thingie" and no way linux could stop it from sending a complete memory dump via internet to NSA
<DocScrutinizer05>
actually "the thingie" could completely freeze linux land and map all memory into modemOS addr space, so the modem can do with it whatever it likes
<DocScrutinizer05>
either you are in control or you are being controlled
<Oksana>
That's the problem with the thingie. It should not be able to violate privacy of either Linux or Modem this way; it should limit interaction of Linux and Modem to the minimum necessary, to the minimum agreed with consent of both parties...
<DocScrutinizer05>
it *should* yeah
<DocScrutinizer05>
however there's no way to make sure it does
<DocScrutinizer05>
when you're root there's a lot of things you *should not* do, but who would make sure you actually don't
<DocScrutinizer05>
definitely not one of your lusers you manage
<Oksana>
Okay, do all mobile phones (except BlackPhone, Pyra and Neo900) share RAM-CPU between Linux and Modem to this absurdly high level?
<DocScrutinizer05>
I think yes, and even blackphone does for all I know
<DocScrutinizer05>
that's why balckphone is a laugh
<Oksana>
I heard something about BlackPhone... Will send you a link, if I find it...
<DocScrutinizer05>
on a sidenote: had much fun with dolibarr today. Webshop getting closer :-)
<Oksana>
In such shared-RAM-CPU thingies, is there a way to shut down ModemOS completely and guarantee that it has shut down? I know that I would then have to attach a USB dongle for any cellular connection, but it would be interesting...
<DocScrutinizer05>
no
<DocScrutinizer05>
actually there's no way at all to shut down the modemOS
<DocScrutinizer05>
I mean, the thing *boots* into modemOS
<DocScrutinizer05>
to shut that down, you remove the battery ;-)
<bencoh>
modemOS ? what are you talking about ?
<bencoh>
the thing that runs on the baseband ?
<DocScrutinizer05>
about shared-mem/cpu architecture in phones
<bencoh>
oh, okay
<DocScrutinizer05>
((shut down)) as well you could ask if there's a way to shut down the server that runs your VM
<DocScrutinizer05>
you can shut down your own VM, you can ask supervisor to shut down the server. The server can tell you whatever it likes, even pretending to shut down the complete machine. You'll never know what *really* happens
<DocScrutinizer05>
you're confined in your little VM world
<bencoh>
twinkle twinkle little VM world
phre4k has quit [Quit: Leaving]
<bencoh>
(sorry, made me think of "Twinkle Twinkle little Earth")
<DocScrutinizer05>
sounds like a SF movie
<bencoh>
not so far ... a Leonard Nimoy song :-)
<DocScrutinizer05>
aaah
<DocScrutinizer05>
LLAP
* DocScrutinizer05
heads out for _finally_ starting some RL activities