~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
+Anomaly
+FreefallHeavens
+Xeha
+acetone
+bak83
+cumlord
+hk
+poriori
+profetikla
+uop23ip
+weko
Arch
Danny
DeltaOreo
FreeRider
Irc2PGuest12106
Irc2PGuest32754
Irc2PGuest43409
Nausicaa
Onn4l7h
Onn4|7h
Over1
anon2
anu3
boonst
floatingspawk
itsjustme
mareki2pb
not_bob_afk
plap
shiver_
simprelay
solidx66
thetia
u5657_1
hk
seems like the attack subsided hpdbe6o6qqqqvgygbcznssat46kybsm7rcauofqaoly4ajdi2jeq.b32.i2p/file/Dsz0CRbDhQ_6jyjlfiki54lhOlVWnM3osVaJSv5Fo_VMzuYuER8H/bw.combined.svg
dr|z3d
for now, sure, but I don't think we're out of the woods just yet.
hk
yeah
hk
oof
hk
if the trend continues, it should peak again
hk
in 2 days it seems
hk
~2 days*
RN
hey dr|z3d, or eyedeekay, or zzz, what should I be checking when I get "Unsupported encryption options" on 'website unreachable"
RN
I've tried both Canon and Plus on this url, it works for someone else on plus, and I didn't modify my 4444 tunnel settings.
RN
I think I ran into this before but don't remember the solution
RN
looks like around April and September there were mentions about it and 'lifecycle' fixes in progress.
RN
on IRC
dr|z3d
nothing, RN. it's probably running i2pd-exclusion crypto like gostcoin.
dr|z3d
*exclusive
dr|z3d
works on plus?
dr|z3d
make sure you have both crypto types enable in your http proxy then.
eyedeekay
Yeah the lifecycle issue was temporary and only happened in some cases where it got confused about which keys to use on sites that supported old and new keys, it should be impossible now
RN
nope, the target site is running on I2P+ with same config as another site that works fine
RN
I tried to load it with both Canon and I2P+
RN
I do have both enabled (at least on the Canon one)
dr|z3d
ElG+ECIES in http proxy tunnel. failing that, dunno. what's the site?
eyedeekay
Well that's pretty weird...
RN
yhttp://y.i2p/about
dr|z3d
Unsupported encryption options
RN
ok, so not just me
RN
sorry eyedeekay, I guess this one has come back to bite butts
dr|z3d
errrweeeeeemfvikotnqzkruxczpchzrh6mjvpbdnvbqkllmfcgq.b32.i2p -> Destination LeaseSet not found
RN
the start of the b32 looks sus
dr|z3d
could be a vanity dest.
RN
cumlord, did you make a vanity b32 for it?
dr|z3d
maybe cumlord's been randomly messing with his tunnel configs.
cumlord
No I didnt
RN
he did mention he registered it simultaneously on stats, identiguy, and reg
dr|z3d
not relevant.
RN
cumlord, is that the correct b32?
cumlord
wait that b32 doesn't look right
cumlord
it started with zz
dr|z3d
address conflict then.
RN
notbob's index hasn't found it yet
RN
seems I already have one in my address book
dr|z3d
nuke the existing address and then addresshelper.
RN
from reg.i2p Jan 6, 2023, 10:25 AM
RN
yeah that'll fix it for me
RN
this is why reg expiring them is a problem
cumlord
Ah that makes sense. I checked stats.i2p first but didn’t see anything for that one
RN
and the reg jump gave me 404
cumlord
thank you 🎉 🎉🎉
RN
(after deleting old one)
cumlord
The normal b32 works?
RN
yep
RN
deleting the old entry got it working, but the jump from reg.i2p did not work even though they have the right b32. The jump from stats worked.
RN
seems a bug at reg.i2p since selecting that for the jump did not work
RN
also a bug at reg for expiring old ones. IMHO
cumlord
i think i had that issue from reg randomly the other day
dr|z3d
delete and then jump worked for me.
RN
that's odd
RN
delete and jump did not work for me
RN
(using reg)
RN
but stats jump did work
onon_
Something with ilita?
dr|z3d
or something with orignal's hosting?
orignal
another attack
orignal
incoming streams flood
orignal
RN reg will be back shorlty