#pfefferleGWG hmmm tough question... I am not sure if there is anything to make it better...
#pfefferleGWG the best way is to use a good theme, so the plugin will always be a bit hacky ;)
tantek, j12t and singpolyma joined the channel
#ZegnatRe: simple TOTP & password IndieAuth self-contained thingamabob, how about encrypting the TOTP secret with the user’s password? That way password isn’t stored on the server at all and TOTP secret is not stored in the clear. Any obvious drawbacks to that?
#Zegnatparagonie seem to have a totp lib too, but according to packagist also pinned to PHP 7
#aaronpkYou can test against signing in to Telegraph
#Zegnatsknebel, maybe not worry about PHP version as step one, but get the flow working first? When we have a working thing that is easily deployable we can work backwards to support older PHP versions
#ZegnatI was going to test against the wiki, aaronpk. But could do Telegraph too :)
#sknebelZegnat: sure, I just wanted to get a basic idea what libs and apis are useable
eli_oat joined the channel
#sknebel5.5 seems like a reasonable starting point, with password_hash being available
#ZegnatIt looks like most of the [HT]OTP libs on packagist have all moved on to 7.0+, so it would require loading a lower version in almost all cases and hoping they backport fixes
#ZegnatNice thing about encrypting the TOTP secret with password: no need for hashing algos in PHP, only encryption.
#ZegnatAnd AES encryption shouldn’t be too hard to access, I think
#ZegnatI wonder if we could package it as a PHAR so everything is contained in one file. Make it truly “drop this one file on your server, link to it, and use IndieAuth”.
#sknebelheh, I'd prefer to only use hashing if proper hashes are available, most encryption apis are a pain
#sknebelstill, thats the way to go without a way to safely store temp data
#ZegnatSurely the private signing key has a higher risk level? It would allow any endpoint to create keys that my endpoint accepts. The other two only have value together, and only to login through my actual endpoint (which could theoretically also be IP whitelisted etc.etc.)
#ZegnatOh, I am not disagreeing with you that signed codes are the way :) Just over-analysing
#sknebelyes, you are right, mentally ignored the hashing
#Zegnatto be honest, might as well store everything in the clear. The entire endpoint can only be as secure as the signing key storage, and the signing key must be stored in the clear...
#sknebelZegnat: allows signing only when knowing (password-protected) secret, verification possible without secret
#sknebelI don't think Loqi has a blacklist anymore
#ZegnatAlright, so you would be able to have your TOTP shared secret and your private signing key encrypted with the password and then a public key for verifying codes that are sent back.
#sknebelsame for password-only mode (which also should be a step before TOTP)
#ZegnatYes, this would be the same without TOTP, only difference is how much data is being stored encrypted
j12t joined the channel
#ZegnatI don’t know what asym libs are available to us though
#[miklb]sknebel well, I wanted to build a theme that was fully ready for the several IW WP plugins but you can’t require plugins with a theme, so I would have to write checks to see if each plugin was active and do a bunch of conditionals.
#[miklb]GWG when you have a few minutes, I’d like to discuss simple location a bit.
j12t, gRegorLove and [cleverdevil] joined the channel
#sknebelben_thatmustbeme: somewhat-recent php has a bunch of default functions for hmacs and such that I'd try to use instead (any specific reason you went for md5 everywhere?). and a few other small things. how do you want to work on it? Give me/us (I guess Zegnat is interested as well) access, or do you want issues and PRs?
#[miklb]GWG for one, trying to figure out where `$geodata['public']` is getting set
#[miklb]I switched to the master on micropub and a lot of stuff is working now that I thought was missing before. need to add the checkin post kind now.