208600+ entries in 0.133s
Framedragger: oh, did mp's client connect
to server before, without autossh etc? need
to confirm fingerprint
Framedragger: some suggest
to
try with stock openssh server,
to see if same happens. anyway, curious if sshd_config on your end has custom knobs (e.g. prefers one crypto format over another), but i guess
the whole
thing's a
timesink
Framedragger: then again, it'd be a more powerful filter
to deter stupid people.
Framedragger: i won't insist - you're right, we've already just had
that chat on #b-a
a111: Logged on 2017-02-28 13:38 asciilifeform:
to wind it up,
the casks algo is asciilifeform's attempt at
the 'high vacuum pump' from earlier --
to get
the max possible removal of something-to-allcomers element ,
to
the extent possible without running an entirely closed wotronic system (and consequently
turning into visa or swift)
Framedragger: ..which means
that
the latter should be dropped eventually, i guess (but
then cue my question 'why not just work on
trb-i if no compatibility with heathen prb network')
Framedragger: i
think it makes sense,
thinking of
the future,
to eventually move
to a model where
there is no 'public
trb node ip list'.
Framedragger: asciilifeform: btw regarding bitcoin, sure re. 1000 machines but if/when
there's only 15 or however many
trb nodes....
Framedragger: aha, good stuff, i guess
the point is
that
this kind of ddos is *easy*.
Framedragger: (one day i'll dup up logs why
tae fuck mircea_popescu allegedly filters out udp by default)
Framedragger: also, ip packets with custom proto number would (1) stand out more easily
to enemy, and could be more easily filtered out (vs. udp header with rng-data within) - see how chinese firewall blocked
tor bridges etc etc; and (2) i'm sure quite a few appliances would filter
them out by default (like how
they filter out icmp, etc.)
Framedragger: asciilifeform: can you not use raw sockets (with some kind of linux cap
to allow program
to open
them without root), defining udp-like struct within? (i'm sure performance
tuning may not be easy, i mean
to achieve same level of optimisation as in kernel stack)
Framedragger: aha. it's funny
this little difference is 'forgotten' in most
tutorials etc. heh.
Framedragger: yes
that i know, but you still gotta reserve
things
to parse
things...
Framedragger: i'm sure it's less
than
that especially as you don't need
to save state/session info
Framedragger: asciilifeform: hm, sure. (and i forgot about arbitrary RSTs by anyone in
the path which destroy
the session, heh.) do you know how
the resource allocation compares
to udp in a
typical (say, linux kernel) networking stack?
Framedragger: (this is just
to juxtapose
topics of
trb and gossipd for a second and
to maybe show why some folks really like
the lighthouse idea) :)
Framedragger: mircea_popescu: re. blackholing and
to be alf-pessimistic for a second, node is exposed
to risk of being blackholed as long as it uses
TCP; because not only can enemy make it read packets (unavoidable in
the end it seems), but
there may be ways
to making it send packets back.
☟︎ mod6: ok. i
think we've got something we can work with. :]
mod6: so either user creates ~/trb-deps and
then pulls all .asc's from deedbot manually in offline mode. or makefile creates ~/trb-deps and pulls .asc files in `make ONLINE=1` mode and dumps files in
there.
trinque: then
they can sit
there for
the rest of your life and
that's
that
trinque: makefile would make
the dir, maybe ~/trb-deps as default, or w/e
mod6: so yeah, something other
than what I did is preferred (at least
to me).
mod6: but having it set up as i just did in
the above paste is unpressable in current vtronics.
trinque: could just drag deps/Makefile into
the root Makefile, and put
the dep-files someplace else
trinque: I
tend
to have a couple
trees pressed right next
to each other, when
testing a patch, when writing my own
trinque: whole idea is
to get
them outside
the press, so you don't have
to copy
them in each
time you press
trinque: could do
the same for deps path, provide some default, and if you want something else:
trinque: this is
the kind of
thing I provided defaults for, like what your copy of your checksum proggie is
trinque: nah makefile can make
those dirs if absent
mod6: this would leave, for instance, a 'trb' output press directory along side of
the above stated dirs. of which, all
that would be contained in
there is a bitcoin directory, and
the underlying 'src' directory.
mod6: so
that'll be
the next
thing
to
take a look at.
mod6: problem will be with pressing and a vpatch. press wants
to put everything underneath of
the given press directory. not place contents adjacent
to a press directory.
mod6: interestingly, i just
tried moving 'bin', 'deps', and 'build' and all of
their makefiles + a few small
tweaks up ../../.. and was able
to build.