so i can prove my address and my qualified teacher status using tlsnotary now :)
it's amazing how utterly clueless government agencies are. they let you download a pdf stating your qualifications. no digital signature, nothing.
llllllllll joined the channel
beyond bitcoin latest episode worth a listen stefan thomas, codius. talks about a lot of issues that we talk about. i think he might be referring to you at 31 minutes dansmith_btc , although it's a bit mixed up..
oakpacific
well dat key would have been worth billions
it's crucial to the government that they operate in a way that makes sure nothing goes out of its control(i.e., violence)
waxwing
oakpacific, you mean digital sigs introduce a risk (having to keep it safe)?
oakpacific
waxwing: i mean, if the govt issues you a qualification, and later wants to revoke it, they can do nothing other than changing the key or waiting for your qualification to expire
waxwing
oakpacific, well they can put an expiration date on the qualification cert. - but, you are right, that is a good point.
but isn't that problem also an existing problem even for let's say, signed paper qualifications?
tlsnotary solves it though, because you audit in real time.
so if the qual is out of date or revoked, it will show up.
waxwing: signed/stamped paper qualifications is a mess
waxwing
yes. and tlsnotary solves it :)
oakpacific
i don't think you are going to just show someone a signed piece of paper and be authorized to do something, there is usually a whole bureaucracy in place handling that
waxwing
you'd be surprised how often in the real world that paper qualifications are just taken at face value.
oakpacific
waxwing: that's because-they check your bio-identification
waxwing: hey i live in the RL :)
waxwing
not the halls of academe? :)
oakpacific
halls of academe are all over ZKP, IBT, nonlinear quantum computing and so on. Non regulated p2p ecash? Pfffft
for once Koreans may really help with the adoption of a new technology that actually makes sense
TLSNotary maybe good for Hearn's proof of passport
makes the case of a TLSNotary sidechain even more appealing
waxwing
well tlsn just seems like a better implementation of the PoP idea to me; the latter has problems in the lack of challenge-response, which itself is because of how passports were designed.
but for sure it's interesting to compare the two technologies.
as for tlsn-sidechain, uhh, ok ...?
oakpacific
waxwing: the obvious non-ideal attribute for TLSNotary as PoP is the need for a centralized auditor/a bunch of them
waxwing
oakpacific, i don't think so; if i use tlsn to prove my address, let's say, then the auditor is the person that wants proof. there is no third party (or 4th depending on how you look at it)
just as, if i want to prove my identity using pop i prove it directly to another party without a middleman, right?
oakpacific
waxwing: the thing is, with pop, the check of the validity of the proof doesn't require the proving party to involve
you just, e.g., visit the govt's website
waxwing
sorry, who visits the gov website? can you walk me through it, i'm vague on the details/forgotten
oakpacific
waxwing: AFAICR, the proving party first generates a ZKP of his passport info using the gov's signing key
waxwing
yes
oakpacific
now he publishes his proof, and since everyone can access the gov's signing key, they need to bother the proving party no more
waxwing
right, so he thereby links it to some pseudonymous id he has (eg bitcoin pubkey, let's say)?
oakpacific
yeah i guess so, so a miner could only collect his reward with this additional proof?
not too clear with the details
waxwing
(wow. crude wti at 76, usdjpy at 114. the dollar is killing everything.)
oakpacific
waxwing: not cny obviously
waxwing
i think the ideal scenario, as i remember it from discussions with MH, is the challenge-response scenario, e.g. whatever system it is that needs the ID proof issues the user with a token, then he uses NFC on the passport chip and it uses the chall-resp protocol to sign, and generate the ZKP. Or something like that.
then, only that physical passport could have done that. so for voting, for example. of course, this assumes the govt didn't screw up their crypto.
as for example korea or taiwan (i forget which) did famously.
oakpacific
waxwing: ???!!
waxwing
are you asking about the korea/taiwan statement?
oakpacific
yes
waxwing
gonna be hard to find it. i'll try.
oakpacific
waxwing: no no need
just, surprised
okay, i guess in RL, govts still deliver important decrees/orders with a representative in person?
and now i remember where i heard about it (one of the places): it was that fantastic talk by djb et al on RSA factoring on youtube.
interesting. in the research they scanned every IPv4 address on the internet, and grabbed the pubkey. that is not a particularly difficult thing to do ( a few billion).
oakpacific
waxwing: i knew you went for a diving :)
despite what i said, thanks a lot
well, it was in 2003 so i guess i can forgive them for that
attacks on desktop wallets more pernicious i guess. at least this clipboard one *can* be avoided.
my daily reminder: msig pubkeys? any feedback on new status bar?
has anyone tried to audit a pdf? if i'm remembering right, it should work ok, except that tlsn will try to open it directly in the browser on the auditee side, but that's just an optics thing i guess.
oakpacific
oops, new status bar
so much stuff, where to begin where to begin
waxwing: it's my understanding that there is no authentication in PGP other than the signature
omg, thanks allah
wtf is this securedolphin guy doing
he uses rc2-40bit-cbc for his symmetric encryption, u kidding me?
the library he uses supports AES
yet he chooses RC2
clueless
waxwing
oakpacific, where are you seeing the code?
oakpacific
okay, to be fair, it's not 40 bits as i initially thought, the key is actually 256 bits, the code is in the chrome extension directory, it's all js after all
waxwing
ok so you have to install it or something?
oakpacific
yes, but i got it form chrome store so no linking of account yet
waxwing
i don't know anything much about RC2 except who its author is. but obv i'm sure you're right that it's a crappy old technology to be using given what's available.
oakpacific
well, 1995-2005 in general was indeed a dry spell for symmetric encryption
waxwing
oakpacific, how do you get it from chrome store without linking account? do i have to do it on the phone?
oakpacific
waxwing: no why, you just install it, linking the account requires particular operations which you can just ignore
waxwing
ah, i guess i can just disable the extension
it does request permission to read mail accounts
ah i see, it doesn't get that until you configure it
oakpacific
waxwing: yes
waxwing
ah yeah. forge was the project i first saw with a complete TLS implementation in a few thousand lines of JS. I am only slightly less amazed than i was when i first saw it.
i should tell the guy that it'd probably take him 1 hour to implement RC4 himself.
oakpacific, do you think it's possible he chose RC2 to avoid performance issues with AES?
oakpacific
waxwing: it's for email, saying performance issue sounds like a bit of a joke
waxwing
well ... attachments maybe?
oakpacific
consider that forge would not be your first choice when it comes to crypto lib
i would say it's more likely cluelessness
and implementing rc2 yourself is really easy
waxwing
well i don't think that's at issue; he's using forge's rc2, right, so the discussion is why he used that instead of forge's aes (or aes-gcm maybe?)
oakpacific
although it's also possible
that somehow the js engines of the browsers perform better with rc2
attachment seems like a minor issue, e-mail protocols are notorious for their slow transfer of files, any encryption would be much faster
waxwing
sure, rc2 like rc4 will be enormously faster than aes, whatever the implementation.
oakpacific
waxwing: hmmm....that really depends i should say
waxwing
ok, well, let's leave it - let's say you're right that there is no performance issue, then it's just stupidity that we can't analyze.
oakpacific
think again it's more like irresponsibility than stupidity, but well, i agree there is no need to go on consider the code overall is not that good
waxwing
well; i wouldn't dismiss the entire code as bad because of that. i think the overall design, using namecoin with rsa encryption (pgp) and symmetric encryption is, let's say, of interest.
oakpacific
waxwing: right, but....it looks to me like the key-validation is done through a server
waxwing
key validation maybe? but last question on FAQ suggests it's OK ?
oakpacific
obviously privkeys shouldn't reach the server, but i am thinking of other things, like verifying the key is really in the blockchain
also i don't think making use of the blockchain itself really makes much sense, we still have a Cpof here
waxwing
wow you're hard to please :) a blockchain is a very different type of object, difficult to see how you could get further away from cpof than using that.