<pie_> idea: probably name it something different but maybe a secureReadFile alternative of readFile that will check permissions and stuff of say a file containing a password hash or something?
<pie_> arguably if the hash is good and the password is good it shouldnt matter but idk
* pie_ ponders but doesnt particularly care at the moment about the "secure data" github issues he never read
<sphalerite> pie_: or even have readFile refuse to import non-world-readable stuff?
<pie_> sphalerite, im not sure im reading that right
<pie_> you might have double negated that by accident, in which case yet?
<pie_> *yes
<sphalerite> no that was an intentional double negation, I suppose I should have phrased it as "only import world-readable stuff"
<pie_> oh
<pie_> actually i guess that doesnt...oh i get it
<pie_> ^ sent that wrong
<pie_> *that doesnt [make sense]....oh i get it
<pie_> yeah ok, maybe. im not quite sure it would help?
<sphalerite> what do you actually mean by "check permissions and stuff"? :p
<pie_> i guess if you for the sake of argument copied your .ssh somewhere it could warn you
<sphalerite> exactly
<pie_> the whole point would be that if you have something tha tneeds to be secure, youd mark that semantically by using secureFileRead
<pie_> so i guess its kind of a converse thing to that
<sphalerite> and then what happens with it?
<pie_> it checks "stuff" and aborts the compile if it deems something unsafe?
<sphalerite> what would you consider an example of something unsfe?
<pie_> world readable perms on a "secure" file?
<pie_> well
<pie_> i guess that doesnt matter if its going to end up in the store anyway
<pie_> i cant quite remember, wasnt readfile actually a workaround for that?
<pie_> that doesnt sound right
ckauhaus is now known as ckauhaus[afk]
<andi-> Has anyone attempted building nixos with ASAN enabled? Sounds tempting..
<pie_> sounds like a good idea, though i would hate to think of the output
<ivan> I compiled znc with ASAN once and it leaked enough memory to crash repeatedly
<andi-> ivan: and you did report/patch all of the issues? :)
<ivan> I think I might have used one of those memory-intensive stack tracking options, I just noticed it mentioned as a possible cause on a list
<ivan> 'Turn off "detect_leaks" or "detect_stack_use_after_return" (though this one was off by default)'
<ivan> a new thing for future reference: EffectiveSan https://www.youtube.com/watch?v=PsiYUBeEnVg (though still not yet released on github)
<andi-> I hate those PDF layouts.. So hard to properly read :/
<andi-> Especially since I am out with just the phone for the weekend..
<pie_> shouldnt that be easier since you can zoom in to a coulumn and actually see the letters? :P
<andi-> But you end up scrolling left and right..
<pie_> well when you're done with a column, yeah i guess?
<andi-> Yes and if there is figures you end up searching and scrolling :/ I just don't get why people aren't using epup or whatever for standard publications.
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-security
<pie_> because the typesetting in epubs is fucking horrible? >_< :x
<pie_> i dont actually know
<pie_> having to search for figures seems to be a thing almost everywhere though :/
<andi-> anyone aware of the mattermost stable policy? Our 18.03 verison (4.7.x) is a bit dated and the newer (>=4.8.x) branch recently added a bunch of fixes.. I fail to find sufficient documentation regarding what are the supposed stable release channels... (unstable also carries an outdated version, haven't checked what is broken there tho..)