DocScrutinizer05 changed the topic of #neo900 to: http://neo900.org | conversations are logged to http://infobot.rikers.org/%23neo900/ and http://irclog.whitequark.org/neo900
che1 has quit [Ping timeout: 252 seconds]
vakkov has quit [Ping timeout: 252 seconds]
Decypher has joined #neo900
Decypher has quit [Quit: Leaving]
vakkov has joined #neo900
Kabouik__ has quit [Ping timeout: 245 seconds]
vakkov has quit [Ping timeout: 252 seconds]
vakkov has joined #neo900
SylvieLorxu has quit [Quit: ZNC - http://znc.in]
phre4k has quit [Quit: Leaving]
Kabouik has joined #neo900
Kabouik has quit [Ping timeout: 240 seconds]
Humpelst1lzchen has quit [Ping timeout: 246 seconds]
Humpelstilzchen has joined #neo900
raccoon_ has quit [Ping timeout: 272 seconds]
nox- has quit [Quit: Leaving]
b1101 has quit [Quit: b1101]
ashneo76 has joined #neo900
ecloud is now known as ecloud_wfh
Pali has joined #neo900
quatrox has quit [Ping timeout: 252 seconds]
afics has quit [Quit: afics]
afics has joined #neo900
sparetire has quit [Quit: sparetire]
illwieckz has quit [Ping timeout: 256 seconds]
illwieckz has joined #neo900
modem has joined #neo900
SylvieLorxu has joined #neo900
chainsawbike has quit [Ping timeout: 255 seconds]
chainsawbike has joined #neo900
phre4k has joined #neo900
che11 has joined #neo900
che11 has quit [Ping timeout: 245 seconds]
Kabouik has joined #neo900
che11 has joined #neo900
mvaenskae has joined #neo900
mvaenskae has quit [Ping timeout: 246 seconds]
phre4k has quit [Ping timeout: 250 seconds]
<Pali> "All am35xx GPs have the SHAM and AES modules except some very old ones."
<Pali> which means that there are some TI GP devices with AES hw support
<DocScrutinizer05> sounds about correct then, yes
<DocScrutinizer05> if I hadn't already closed the relevant TRM pages in my reader, I'd look up the relevant bits in config registers and read them out from processor
<DocScrutinizer05> well, I would if I had a working OS image on a uSD for BB-xM
<DocScrutinizer05> when you think about it, it makes not much sense TI building _two_ different chips, one for GP and one for HS. If I were do build those OMAP3, I'd simply fuse to death the HS features for my GP series
<DocScrutinizer05> prolly GP simply has a few according commands in ROMBOOT that disable and hide the HS stuff
<Pali> do you know what is timer12?
<Pali> timer@48304000
<DocScrutinizer05> sorry no
<Pali> reg = <0x48304000 0x400>;
<Pali> it is disabled on omap3 hs devices
<DocScrutinizer05> o.O
<Pali> in DT file
<Pali> also in hwmod
<DocScrutinizer05> disabled on *HS*?
<DocScrutinizer05> so it must cause a threat to the whole TrustZone thing
<DocScrutinizer05> or cause malfunction when using it in HS mode
<DocScrutinizer05> maybe something about profiling?
<Pali> "On secure devices the 12th timer is reserved for secure usage and so cannot be used by the kernel, where as for a GP device it is available."
<Pali> funny, it is disabled at two places
<Pali> first explicitly disabled in DT
<Pali> and second it has special flag that only GP device can use it :D
<DocScrutinizer05> well, actually it's "disabled" only in MShield/TrustZone setup, by assigning it to the secure domain
<DocScrutinizer05> it's not disabled, it's simply not available to 'normal' processes (incl kernel)
<DocScrutinizer05> waaaah, systemd reports segfault in kernel
<DocScrutinizer05> cya later guys, time to reboot
<DocScrutinizer05> err systemd segfaulted
<bencoh> krkr
<bencoh> wait, how comes it still works then ?
<DocScrutinizer05> FFS!!
<DocScrutinizer05> nfc
<bencoh> I guess pid1 is still alive
<DocScrutinizer05> yoh
<DocScrutinizer05> Message from syslogd@localhost at Feb 18 14:43:35 ...
<DocScrutinizer05> kernel:[1566879.692218] systemd[1]: segfault at 1fc6ac0 ip 0000000001fc6ac0 sp 00007fff9f2ab858 error 15
<DocScrutinizer05> http://privatepaste.com/991ed14e62 fsckng scary
DocScrutinizer05 has quit [Quit: EEEEEEK]
DocScrutinizer05 has joined #neo900
<DocScrutinizer05> hmm, still not feeling as calm as I did an hour ago
<kerio> ?
<kerio> oic, systemd
<kerio> report it as a bug
<DocScrutinizer05> yes, incl pam
<DocScrutinizer05> system also suddenly switched to console0 out of nothing
<DocScrutinizer05> :-O
<DocScrutinizer05> feels like somebody exploited a vuln in systemd to try and gain root access
<wpwrak> his name is poettering :)
<DocScrutinizer05> honestly what do you think of http://privatepaste.com/991ed14e62
<Wizzup> hilarious and saddening
<wpwrak> looks like a case of a complex system failing (or maybe not ?) in a messy and incomprehensible way
<DocScrutinizer05> two things attract my suspicion: dhclient in there, and the completey out-of-sync timestamp 2015-02-18T09:15:01.951233+01:00
<bencoh> I think you worry too much about a broken by design piece of software :)
<DocScrutinizer05> I do since it's on my system - which is bad enough
<bencoh> I'd tell you to move to devuan, but you wouldnt be able to ask for info on their channel :>
<DocScrutinizer05> yeah
<wpwrak> why, does the bouncer only let you in if you have a 50+ cm white beard ?
<DocScrutinizer05> no, a sucker banned me
<DocScrutinizer05> for qurstioning his ban of a complete IP subnet
vakkov has quit [Ping timeout: 264 seconds]
<DocScrutinizer05> channel owner told me in query "we need to do sth about this whole topic" but that's been it
<DocScrutinizer05> [BanList:#devuan] *!*@openmoko/engineers/joerg set by ChanServ on 2015-01-28 Wed 16:49
<DocScrutinizer05> by *chanserv*, aka /akick
<DocScrutinizer05> no sane chanop using akick
<DocScrutinizer05> rationale why this guy did: "I want to establish bans that no other chanop can revert" - OMG
<DocScrutinizer05> what for he needs other chanops (+o) then, anyway?
<kerio> you don't understand veterans
<wpwrak> we need that on a t-shirt :)
<DocScrutinizer05> this is no veteran, this looks like a noob and allegedly is very young, according to chan owner
<DocScrutinizer05> when you don't want somebody to do - or undo - bans on your channel, you don't accesslist +o him, neither +b. When you need somebody to do minor "chan moderator" tasks like changing topic (+t) or giving voice (+v) to other chan users, you set accesslist flags accordingly
<bencoh> DocScrutinizer05: just ask chanowner to revert that
<DocScrutinizer05> bencoh: I did, chan owner answered "we need to do sth about that. But later, busy now". Last I heard of him
<bencoh> meh
<DocScrutinizer05> (very young) his IRC account is 10 years old though
<bencoh> haha
<DocScrutinizer05> which seems doesn't help to grok how IRC chan admin works
<bencoh> compared to a veteran vax admin maybe :>
<bencoh> note my irc account is 7yo and I'm "only" 25yo as well, so ...
<bencoh> s/irc/freenode/
<wpwrak> if devuan doesn't want you, maybe try openbsd. i've heard they have pretty decent security. you'll have to set theo right on some things, but i'm sure he'll be appreciative of any constructive input.
<DocScrutinizer05> anyway, I offered to forget about it and keep up support and contribution to #devuan and the project, if they feel like rethinking this mad ban. Chan owner said we will take care. He didn't
<bencoh> wpwrak: is it friday yet ? :D
<wpwrak> bencoh: almost :)
<DocScrutinizer05> wpwrak: I'm not going to change OS just to get rid of poettering malware
<Wizzup> wpwrak: or freebsd, which is more advanced than openbsd
<bencoh> I wouldnt exactly say "more advanced" on every aspect
<DocScrutinizer05> [2015-02-18 Wed 16:09:21] [Notice] -NickServ- Information on coagen (account coagen):
<DocScrutinizer05> [2015-02-18 Wed 16:09:21] [Notice] -NickServ- Registered : Oct 02 00:09:25 2005 (9y 20w 1d ago)
<DocScrutinizer05> OhMyGod, NoOp
<DocScrutinizer05> [2015-02-18 Wed 16:09:21] [Notice] -NickServ- Flags : HideMail, NoOp, Private
<DocScrutinizer05> [Notice] -ChanServ- 2 coagen +AORVefiorstv [modified 11w 4d 20h ago]
<DocScrutinizer05> sure, set own access list to +O+V, then say NoOp to block that nonsense
* DocScrutinizer05 headdesks
<DocScrutinizer05> [Notice] -ChanServ- +V - Enables automatic voice. [Notice] -ChanServ- +O - Enables automatic op.
<DocScrutinizer05> Note that >>[Notice] -ChanServ- 2 coagen +AORVefiorstv [modified 11w 4d 20h ago]<< has -ChanServ- +f - Enables modification of channel access lists.
<DocScrutinizer05> (besides dropping flags is always possible, even without +f)
<DocScrutinizer05> dropping *own* accesslist flags that is
<DocScrutinizer05> simple /msg ChanServ FLAGS #devuan coagen -V-O would suffice
<DocScrutinizer05> while for /msg chanserv voice #devuan coagen he needs +v (or +o) which he has, for +O he needs +o
kerio is now known as stenno`
stenno` is now known as kerio
<DocScrutinizer05> /cs access list #debianfork
<DocScrutinizer05> LOL
<drathir> +O if good remember also allow to give +o to ppl...
<DocScrutinizer05> no
<DocScrutinizer05> +o allows that
kerio is now known as stenno`
<DocScrutinizer05> well, +o allows /cs op #channel
stenno` is now known as kerio
mvaenskae has joined #neo900
<DocScrutinizer05> once you're op'ed, you can op others
<drathir> the same behaviour with +V allow give ppl +v only...
<DocScrutinizer05> you need to distinguish accesslist flags and channel/usermode flags
<DocScrutinizer05> drathir: right now I'm only voiced but not oped
<DocScrutinizer05> trying to voice you results in [2015-02-18 Wed 16:38:59] [Error] You need to be a channel operator in #neo900 to do that.
<DocScrutinizer05> I however can tell chanserv to voice you
<drathir> DocScrutinizer05: with +V in acceslist?
<DocScrutinizer05> with +v
<DocScrutinizer05> in access list
<DocScrutinizer05> +V means chanserv will auto-voice _me_
<drathir> with +v if good remember You can apply voice to ownself with +V if good remember also allowed to assign other ppl too voice...
<DocScrutinizer05> no
<DocScrutinizer05> +V needs +v
<drathir> still op needed?
<DocScrutinizer05> for chanserv? no
<DocScrutinizer05> I can do /cs flags #neo900 add drathir +v
<DocScrutinizer05> and then you're allowed to do /cs voice #neo900 <$user>
<DocScrutinizer05> you also can set own +V on access list iirc
<drathir> DocScrutinizer05: in that case i can add by myself op to me, but cant enable other ppl?
<DocScrutinizer05> with +o on accesslist you can do /cs op #neo900 <$user>
<DocScrutinizer05> please check /msg chanserv help flags
<DocScrutinizer05> these are *accesslist* flags, *not* /mode flags
<DocScrutinizer05> for mode flags see http://freenode.net/using_the_network.shtml "User and channel modes"
<DocScrutinizer05> /help umode
<DocScrutinizer05> to do /mode drathir +o I need to be chanop (+o)
<DocScrutinizer05> chenserv doesn't need to be +o to op you. I need +o on *access list* to tell chanserv to op you
<drathir> DocScrutinizer05: dont have access to list user flags i guess...
<drathir> bc no info access #neo900 list
<DocScrutinizer05> /msg chanserv access #neo900 list
<drathir> its protected i guess...
<DocScrutinizer05> ooh, that shouldn't be
<drathir> ok now works...
<drathir> 6 rules
arcean has joined #neo900
_whitelogger has joined #neo900
vakkov has joined #neo900
<DocScrutinizer05> 'Live kernel patching support via KDBUS' WAAAAHHHH!!!
<bencoh> :D
<Pali> :D:d
<DocScrutinizer05> I just wonder who's providing that free LSD they are on
<Pali> suse and redhat :D
<Pali> and maybe canonical too
paulk-collins has joined #neo900
<bencoh> oh, didnt know hellekin was part of the staff
raccoon_ has joined #neo900
mvaenskae has quit [Ping timeout: 256 seconds]
<wpwrak> hah, didn't know either. he's everywhere ! :)
<bencoh> :)
sparetire has joined #neo900
<DocScrutinizer05> please help me out, too many names
<DocScrutinizer05> I guess googling won't help
Kabouik has quit [Ping timeout: 250 seconds]
jake42_ has joined #neo900
sixwheeledbeast^ has joined #neo900
Kabouik has joined #neo900
jake42 has quit [Ping timeout: 245 seconds]
sixwheeledbeast has quit [Ping timeout: 245 seconds]
quatrox has joined #neo900
che11 has quit [Remote host closed the connection]
<Pali> just to note: omap AES, SHA and MD5 HW support is enabled for all GP devices by linux kernel
<Pali> no idea if this is bug or feature
<Pali> just fact
<Pali> and DISABLED for all HS devices (because it cause L3 firewall error and kernel crash -- on devices where bootloaders does not enable that HW support)
<Pali> DocScrutinizer05: it is easy to check if bbmx board has support for AES. just load kernel driver omap-aes.ko
<Pali> and check dmesg log for errors :D
xray256 has joined #neo900
xray256 has quit [Client Quit]
xray256 has joined #neo900
xray256 has quit [Quit: WeeChat 0.3.7]
paulk-collins has quit [Quit: Quitte]
vakkov has quit [Ping timeout: 250 seconds]
<Pali> systemd-fsckd
<Pali> this is not a joke
<Pali> another stuff in systemd
<DocScrutinizer51> Pali: coherent. when mounting then also fsck
<Pali> yes fsck+mount should be one action
<Pali> but why systemd-fsckd as separate?
<DocScrutinizer51> no idea
<DocScrutinizer51> I just hate it redhat hijacks linux
<DocScrutinizer51> whitehat grayhat blackhat redhat. now it starts making sense
<kerio> illuminati confirmed
<DocScrutinizer51> what's next? steelhat? asshat?
<DocScrutinizer51> skinhat
vakkov has joined #neo900
<kerio> systemd-linux
<DocScrutinizer51> System D
<DocScrutinizer51> forget linux
<DocScrutinizer51> D like demolition
<kerio> or like dong
<kerio> ( ͡° ͜ʖ ͡°)
<DocScrutinizer51> long dong silver?
<DocScrutinizer51> ...was a hoax
<DocScrutinizer51> maybe somebody should tell poettering
<bencoh> 23:57 < Pali> systemd-fsckd
<bencoh> wtf
<bencoh> and ... how comes I *always* learn about it from Pali ? :D
<Pali> systemd-fscks is invention from canonical, not red hat
<bencoh> :/
<Pali> >>> [00:35:11] <DocScrutinizer51> maybe somebody should tell poettering <<< no, maybe canonical people do not tell this plan to poettering..
<Pali> :D
<bencoh> or ... poettering fanboys are hiding in Canonical and lurking in the dark
<bencoh> cant be too sure these days
<DocScrutinizer05> I thought when he knows it was a hoax, he suffers less inferiority complex so doesn't need to compensate with monstrous systemd
<DocScrutinizer05> kerio: btw kudos for this fontset
<kerio> which fontset
<DocScrutinizer05> ͜ʖ ͡° etc
<DocScrutinizer05> whatevr it is
<kerio> k
<DocScrutinizer05> incredible kerning
<DocScrutinizer05> and it renders on opensuse konversation and on maemo xchat ;-)
<kerio> it doesn't work with droid sans
<kerio> ._.
<DocScrutinizer05> I think that long dong silver reference should go with systemd factoid ;-D
<DocScrutinizer05> meh, I's starting to feel silly
<bencoh> it doesnt work with misc/fixed-iso10646 either :(
<bencoh> (unluess the rectangle is intended, but I doubt it)
<DocScrutinizer05> ok neo900 server down