orignal
zzz what do you think to make crypto type 4 by default for all destinations?
orignal
including SAM
eyedeekay
orignal iirc it already is
orignal
I have 0,4 by default
orignal
let's confirm from zzz
dr|z3d
iirc, + is all 4 except for the http proxy which needs to support legacy sites.
orignal
how about SAM?
dr|z3d
hang on, let me see exactly what the defaults are.
dr|z3d
git.skank.i2p/i2pplus/I2P.Plus/src/commit/ed470ada9419fc150bf2c80af7e77565b03c70b6/installer/resources/i2ptunnel.config
dr|z3d
re SAM, I think that's left up to the client to configure.
dr|z3d
this is the correct link for + i2ptunnel.config, though it probably doesn't vary from what I pasted above: git.skank.i2p/i2pplus/I2P.Plus/src/branch/master/installer/resources/i2ptunnel.config
dr|z3d
eyedeekay: you've still got 4,0 for postman. that can be changed to 4.
eyedeekay
I checked my libraries, I do 4,0 at the library level
eyedeekay
ack about postman
dr|z3d
you might want to remove the connect http client tunnel, dunno. largely useless.
eyedeekay
Yeah that's been on the table for years and I never got a satisfactory answer as to who the heck actually uses it
dr|z3d
I think it's a legacy of the time when false.i2p was http only.
eyedeekay
Oh that makes sense
eyedeekay
Probably need to put up a forum post to call out for people who are using it before ditching a default tunnel though
dr|z3d
no, you don't.
dr|z3d
because removing it from the config won't impact existing users.
eyedeekay
True
dr|z3d
and in it's current state, no one will be using it.
dr|z3d
tunnel.5.proxyList=outproxy-tor.meeh.i2p
eyedeekay
Yeah nothing at the end of that tunnel anymore
dr|z3d
*its
eyedeekay
false is gone too
eyedeekay
Obviously
eyedeekay
The other option of course would be to fix it, if there's a reason to fix it, not sure that there is
eyedeekay
mostly sure there isn't
dr|z3d
no, it just adds unneeded complexity for new users.
dr|z3d
is there a benefit to using a connect server to the outproxy? maybe? does it end-to-end encrypt to avoid revealing hostnames? dunno, possibly. if that's required, then the user can configure it, right?
eyedeekay
Yeah and I don't think that's an added benefit either, the only benefits I can think of require some mental gymnastics at best
eyedeekay
because end-to-end encryption is already preserved, and I don't think the connect server changes anything about how it's handled
eyedeekay
in practice
zzz
change default where (besides sam)?
dr|z3d
i2ptunnel.config
zzz
that's orignal's proposal or your guess?
dr|z3d
it's what orignal was suggesting. defaults.
zzz
"defaults" doesn't necessarily mean i2ptunnel.config to me
dr|z3d
ok, then I'll let orignal chime in with a clarification.
zzz
it's also not something that concerns i2pd or requires any cross-project discussion
orignal
eveywhere
orignal
in client and server tunnels
orignal
4 by deafault
orignal
I want to set 4 at least for server tunnels by default
orignal
not 0,4 as now
orignal
zzz any plans to discntinue elgmal completely?