@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+lbt
+orignal
+postman
+snex
+weko
+wodencafe
Arch
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest12735
Irc2PGuest13718
Irc2PGuest36180
Irc2PGuest40608
Irc2PGuest41133
Irc2PGuest59134
Irc2PGuest73814
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4_
Teeed
aeiou
ardu
b3t4f4c3___
bak83
cumlord
death
dr4wd3
eyedeekay_bnc
hagen_
not_bob_afk
onon_
phil
poriori
profetikla
qend-irc2p
radakayot_
rapidash
shiver_
solidx66
theoddone
thetia
u5657
uop23ip
x74a6h
orignal
zzz, I have a question
orignal
can crypto type NONE be applied to non-PQ signatures?
orignal
meaning that the key start from offset 0 and the rest is padding?
zzz
orignal, the only signature types longer than 128 bytes now are RSA, and they are not allowed to be used for RI or Destinations. So we don't need it.
orignal
not only RSA
orignal
also ECDSA521
orignal
and it's allowed now
zzz
oh yeah. That's only 4 bytes extra, not worth the trouble to save 4 bytes
orignal
but my whole idea is not saving some bytes
orignal
also you will have the key at the start of identity
orignal
it might me matter
orignal
and why can't we make it generic?
orignal
no crypto key means signature only
orignal
but let's discuss it during the meeting
zzz
we can if you think it's important, I don't think it is, I already marked all the ECDSA types as "legacy/deprecated" in our UI
orignal
my point we should support this mode even for EDDSA
zzz
sure, we can talk about it, although it's a minor detail, at the meeting we should probably start on the big picture issues
zzz
if you want to do it, we can, not a hill for me to die on
orignal
I'm just working on the code to process NONE crypto type
orignal
and thinking to impemnent it generic way
zzz
yeah
zzz
the reason I did NONE is I tried to do it with type 0 but use the whole 384 bytes, and I ended up with about 50 bugs
orignal
e.g. if no crypto doesn't matter what signing key type is
zzz
it was a big mess
orignal
it always start from the beginning
zzz
so NONE is a lot cleaner
zzz
yes
orignal
I agree about NOONE
zzz
good. I thought maybe you wouldn't like it ))
orignal
btw why 255 rather than -1?
orignal
e.g. OxFFFF
orignal
0 is ElGmamal
zzz
in a couple places like 'b33' we only have one byte for types, not 2, I think?
zzz
so it seemed safer to use 255
orignal
lemt me check
zzz
probably should have been one byte from the start of key certificates, oh well
orignal
right, then 255 is fine
zzz
we'll both be long dead I think before we go past 255
orignal
you can change the spec to use that bytes as "reserved"
orignal
and crypo/sig type is always 1 byet
orignal
we might want use that extra byes for seomthing else laters
orignal
like flags, etc.
zzz
maybe
zzz
it will be eyedeekay's grandchildren's problems ))
zzz
along with the year 2106 rollover
zzz
correction,in b33 there is no enc type, and the sig type can be 1 byte or 2
zzz
but I still like 255 better, yeah maybe we could redefine the high byte as flags some day
orignal
yes 255 is fine
orignal
finally
zzz
and they announced it's going to be a LTS release
orignal
it became avaiable today
orignal
so I can start working
zzz
yup, as scheduled
zzz
orignal, are you ok with a 4 PM eastern review time next week with daylight savings, or do we need to move it back to 7 PM UTC / 3 PM eastern?
orignal
3 pm EST please
orignal
I will be busy at 4
zzz
ok
zzz
heads up eyedeekay dr|z3d ^^^^
orignal
they are all in EST
zzz
yeah but for the int'l folks...
orignal
you were asking idk and drozd
zzz
right
zzz
maybe they live their lives in UTC? what do I know...
orignal
because we agreed for 3 pm
zzz
sure but all my announcements everywhere are in UTC
dr|z3d
roger that, zzz.
zzz
timezones are annoying. DST is more annoying.
orignal
is Trump going to change it?
zzz
dunno