&zzz
+R4SAS
+RN
+Romster
+cumlord
+dr|z3d
+mareki2p
+not_bob_afk
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Birdy
BubbRubb1
Chrono
Danny
DeltaOreo
Guest99
Irc2PGuest28078
Irc2PGuest63096
Irc2PGuest65936
Irc2PGuest6790
Irc2PGuest718
Irc2PGuest74254
Irc2PGuest88931
Irc2PGuest93934
Irc2PGuest95708
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
T3s|4_
Teeed
aargh2
ac9f
acetone_
anontor
b3t4f4c3__
b4dab00m
dr4wd3
duanin2_
eyedeekay_bnc
gelleger1
leopold
makoto
matean
n1
namenick
nilbog
poriori_
profetikla
r00tobo
rapidash
shiver_1
solidx66_
thetia
uop23ip
vivid_reader56
w8rabbit
x74a6
anonymousmaybe
test
anonymousmaybe
Interesting, im using Konversation instead of hexchat, cool
anonymousmaybe
yesterday i got disconnected from irc2p though my tunnel were working fine.. couldnt figure out why
anonymousmaybe
nevertheless i believe dr|z3d you said that user should adjust the RAMs manually? thats bad as well I2P interface gonna configure automatically the bandwidth needed for the output/input so if hes on a high end connection it will be configured based on high outcome
anonymousmaybe
128mb is really bad beed choice from nowadays default PC standards, 500mb looks efficient.
anonymousmaybe
for*
anonymousmaybe
echo|on i think you said that repository needs its own maintain ability, well thats true, i2p-go can go to distro repo and/or flathub repo and/or i2p self own repo
anonymousmaybe
many apps they have all of the choices
dr|z3d
I suggested you could modify wrapper.config, anonymousmaybe, and unless you reinstall i2p you'll need to. however, for new installs, zzz has now made 512MB the default allocation.
anonymousmaybe
oh great then, but thats weird i reinstalled before like couple of months.. nevertheless if its a fixed issue then skip it.
dr|z3d
not weird, the change was only commited to the repo yesterday, so will be in the next release installer unless you build it yourself.
anonymousmaybe
thank you for the info <f>
anonymousmaybe
oh nice, glad to hear
dr|z3d
np.. if you want to change your own allocation, these are the keys you'll want to change in i2p/wrapper.config:
anonymousmaybe
awesome, appreciated
dr|z3d
wrapper.java.initmemory=512
dr|z3d
wrapper.java.maxmemory=16384
dr|z3d
adjust to taste.. you probably don't want to allocate 16GB to the JVM :)
dr|z3d
128 init, 512 max is probably what you want.
dr|z3d
you'll need to stop and then restart the service/wrapper to apply those changes. a simple restart won't apply them.
anonymousmaybe
i assume you mean full restart right?
dr|z3d
no. I mean stop and then start.
anonymousmaybe
oh alright
dr|z3d
ie shutdown router, start router. do not restart router, that won't apply the changes.
anonymousmaybe
got you
anonymousmaybe
if it give it wrapper.java.maxmemory=1000, it wont harm anything right?
dr|z3d
should be fine if you have the ram available.
dr|z3d
I'd work in hex, not decimal, though. git it 1024.
dr|z3d
*give
dr|z3d
and init @ 256.
anonymousmaybe
brilliant idea, will change
dr|z3d
the higher the init ram, the less work you make garbage collection do.
snex
run i2p on dedicated device and give it all the ram
anonymousmaybe
# Initial Java Heap Size (in MB)
anonymousmaybe
#wrapper.java.initmemory=4
anonymousmaybe
this you mean by init?
dr|z3d
yup.
anonymousmaybe
@snex im running it on a VM (Qubes OS)
snex
lol why
anonymousmaybe
well thats safer than directly on baremetal hardware
snex
if its a dedicated machine then who cares how "safe" it is
anonymousmaybe
yeah but its a waste of machine to have it just for i2p, while you can have i2p in a VM as a router and the server on another VM and the IRC on another VM.. (compartmentalization)
anonymousmaybe
this level of security separation you need to have each on a dedicated hardware..
anonymousmaybe
invisiblethingslab.com/resources/2014/Software_compartmentalization_vs_physical_separation.pdf
anonymousmaybe
clean log, nice, thank you dr|z3d
dr|z3d
*thumbs up*
anonymousmaybe
wonder if we can have x448 encryption with or instead of x25519, anybody discussed this matter?
eyedeekay
Not that I recall but if it's something you're interested in I would reference the i2pd GOST proposal for how to ask
eyedeekay
Most crypto talk has been focused on PQ
anonymousmaybe
I see, even PQ, can be used a hybrid with x448 instead of x25519, because i didnt see yet usage of pure PQC atm
eyedeekay
No we're going to do hybrid until the research seems a little less new and a little more stable
anonymousmaybe
yep, good thing
anonymousmaybe
e.g of x448 hybrid pqc WOLFSSL_X448MLKEM768
eyedeekay
Well we're Noise-XK(mostly, on the outside) not SSL so it's going to be different for us
eyedeekay
Regardless though my initial point was that a crypto type is probably a "write a proposal" thing
anonymousmaybe
oh i see, its ok just wanted to mention that as a side note since PQC integrated
eyedeekay
It might be as easy as copypasta from the GOST proposal though
anonymousmaybe
question: how will my router get a PQC if my router itself announce its encryption as "Encryption Key: ECIES_X25519" without the mention of hybrid key, or am i missing something?
anonymousmaybe
(i have changed all my tunnels default to hybrid pqc + ECIES_X25519)
dr|z3d
make sure you're using 768 and not 512 or 1024 for pqc.
dr|z3d
the router doesn't yet support pcq keys, that's "coming soon".
anonymousmaybe
oh.. ok, thanks for the info thought something wrong from my end
eyedeekay
Yeah it's pretty complicated stuff, pays to follow along with the spec and the proposals