669 Commits (c2f719c99634f9b2c7b8b720275c7e238b6d8f9d)

Author	SHA1	Message	Date
Stephen Shelton	c2f719c996	Build endpoint paths at even[ish] intervals	4 years ago
Jeff Becker	bf0416cab8	remove Time_t, add operator overload for printing llarp_time_t and add to_json function for serializing llarp_time_t to json	4 years ago
Jeff Becker	524726e4cc	cast interval to std::chrono::milliseconds before dividing by 4	4 years ago
Jeff Becker	d2d109e92c	llarp_time_t is now using std::chrono	4 years ago
Jeff Becker	f4520ac920	make decaying hashset use llarp::Time_t and move unit tests to use catch2	4 years ago
Jeff Becker	39cdc9e6dd	shift intro on introset update	4 years ago
Jason Rhinelander	54186c4a89	Replace absl string_view with string_view from lokimq ... When we add loki-mq has a dependency we can just alias it, but for now it's easier to copy the header than add the whole submodule library.	4 years ago
Jason Rhinelander	089056ca5b	Remove all ABSL_ATTRIBUTE_UNUSED uses	4 years ago
Jason Rhinelander	f84ce61d66	Removed empty cpp files ... These aren't needed: CMake already knows how to follow #includes and rebuild when headers change as long as the headers are included *somewhere*. The extra .cpp files here just require building a bunch of .cpp files with just header content that we just end up throw away during linking (since the same things will also be compiled in whatever other compilation units include the same headers).	4 years ago
Jason Rhinelander	b4440094b0	De-abseil, part 2: mutex, locks, (most) time ... - util::Mutex is now a std::shared_timed_mutex, which is capable of exclusive and shared locks. - util::Lock is still present as a std::lock_guard<util::Mutex>. - the locking annotations are preserved, but updated to the latest supported by clang rather than using abseil's older/deprecated ones. - ACQUIRE_LOCK macro is gone since we don't pass mutexes by pointer into locks anymore (WTF abseil). - ReleasableLock is gone. Instead there are now some llarp::util helper methods to obtain unique and/or shared locks: - `auto lock = util::unique_lock(mutex);` gets an RAII-but-also unlockable object (std::unique_lock<T>, with T inferred from `mutex`). - `auto lock = util::shared_lock(mutex);` gets an RAII shared (i.e. "reader") lock of the mutex. - `auto lock = util::unique_locks(mutex1, mutex2, mutex3);` can be used to atomically lock multiple mutexes at once (returning a tuple of the locks). This are templated on the mutex which makes them a bit more flexible than using a concrete type: they can be used for any type of lockable mutex, not only util::Mutex. (Some of the code here uses them for getting locks around a std::mutex). Until C++17, using the RAII types is painfully verbose: ```C++ // pre-C++17 - needing to figure out the mutex type here is annoying: std::unique_lock<util::Mutex> lock(mutex); // pre-C++17 and even more verbose (but at least the type isn't needed): std::unique_lock<decltype(mutex)> lock(mutex); // our compromise: auto lock = util::unique_lock(mutex); // C++17: std::unique_lock lock(mutex); ``` All of these functions will also warn (under gcc or clang) if you discard the return value. You can also do fancy things like `auto l = util::unique_lock(mutex, std::adopt_lock)` (which lets a lock take over an already-locked mutex). - metrics code is gone, which also removes a big pile of code that was only used by metrics: - llarp::util::Scheduler - llarp:🧵:TimerQueue - llarp::util::Stopwatch	4 years ago
Jeff	7c5a721457	Merge pull request #1114 from notlesh/redundant-introset-lookup-improvements-2020-02-20 ... Redundant introset lookup improvements	4 years ago
Stephen Shelton	0429bafbb3	Merge pull request #1111 from notlesh/redundant-introset-propagation-2020-02-19 ... Redundant introset propagation	4 years ago
Stephen Shelton	66cb30fa58	Refactor: remove recursionDepth from DHT lookups	4 years ago
Jeff	6ac5f19b3a	Merge pull request #1110 from jagerman/no-abseil-optional ... De-abseil, part 1: remove absl::optional	4 years ago
Stephen Shelton	4c499fb076	Make format	4 years ago
Stephen Shelton	dff9aeb250	Propagate Introset publishing redundantly	4 years ago
Jeff Becker	dc7828941f	add log statement	4 years ago
Jason Rhinelander	ac1486d0be	Replace absl::optional with optional-lite ... Step 1 of removing abseil from lokinet. For the most part this is a drop-in replacement, but there are also a few changes here to the JSONRPC layer that were needed to work around current gcc 10 dev snapshot: - JSONRPC returns a json now instead of an optional<json>. It doesn't make any sense to have a json rpc call that just closes the connection with returning anything. Invoked functions can return a null (default constructed) result now if they don't have anything to return (such a null value won't be added as "result").	4 years ago
Jeff	20bc168d1c	Merge pull request #1093 from majestrate/toggle-publishing-introsets-2020-02-11 ... make publishing introsets optional	4 years ago
Jeff Becker	1874f439b7	add comment	4 years ago
Jeff Becker	e907d2ae19	handover fixes	4 years ago
Jeff Becker	f7f5d893a5	use endpoint path for lookup because outboundcontext does not implement pathset::HandleGotIntroMessage	4 years ago
Jeff Becker	c9866b6a0b	simplify	4 years ago
Jeff Becker	9aeee37347	short circuit	4 years ago
Jeff Becker	6a495dd090	ammend outbound context logic	4 years ago
Jeff Becker	02228ded08	spread out path builds	4 years ago
Jason Rhinelander	9e096d1996	Reduce introset publishing interal to 2.5min instead of 1.25min ... We want to have some redundancy, but having 8 active at once seems extreme; reduce to 4.	4 years ago
Jason Rhinelander	c3637c81fd	Remove another unused randomize parameter	4 years ago
Jason Rhinelander	24469daefb	Remove unused parameter ... We always randomize now.	4 years ago
Stephen Shelton	9dfcfbc3ac	Bencode/decode relayOrder in lexigraphical order, make it uint64_t	4 years ago
Stephen Shelton	906803e387	Refactor DHT introset lookups to use redundant lookup strategy	4 years ago
Jeff Becker	4d4b33607f	dont use optional	4 years ago
Jeff Becker	23bcfa4abb	revert change	4 years ago
Jeff Becker	df8c56343d	refactor GetManyPathsWithUniqueEndpoints to go into service/endpoint_util.hpp	4 years ago
Jeff Becker	fc5e6b4d77	log location	4 years ago
Jeff Becker	3cc2adae31	paralell publish and lookups	4 years ago
Jeff Becker	e30c720446	redundant publish for service endpoint	4 years ago
Jeff Becker	2b6f27d60d	remove connect back logic for dead inbound sessions	4 years ago
Jeff	671c765161	Merge pull request #1085 from majestrate/check-for-initial-current-introset-2020-02-06 ... check for current introset being zero (initial state)	4 years ago
Jeff Becker	792fd4132c	only make default endpoint non-reachable if no keyfile option presented	4 years ago
Jeff Becker	6c67cc1f01	make default endpoint non reachable by default	4 years ago
Jeff Becker	70eb353c42	make publishing introsets optional using reachable=false to disable	4 years ago
Jeff Becker	5b87a9419e	default recursion depth to 2 not 12	4 years ago
Jeff Becker	8c698a1cd1	* rename i to foundIntro ... * check for zero timestamp * use > not >=	4 years ago
Jeff Becker	41210a8ae1	check for current introset being zero (initial state)	4 years ago
Stephen Shelton	37e4f26be1	s/LogInfo/LogDebug @ 'signed/verify encrypted introset'	4 years ago
Jeff Becker	e6174efa21	don't derive x25519 key from ed25519 key	4 years ago
Jason Rhinelander	f1171ed7a2	make format 😠 🤮	4 years ago
Jason Rhinelander	46f3459b79	Fixed EncryptedIntroSet signing to use PrivateKey ... We can generate both root and derived signatures from a PrivateKey, but only root from a SecretKey, so just change it to use a PrivateKey.	4 years ago
Jason Rhinelander	860c5efd47	Derived key fixes ... The reason things weren't working here is because libsodium does something completely unintuitive and called the seed the "secret key" when it isn't, it's the seed. This adds a new PrivateKey class (alongside the existing SecretKey and PubKey) that holds just a private key value but no seed -- which we need to do because there is no way we can get a seed after calculating a derived keypair. With these changes, we now generate exactly the same keys and subkeys as Tor (and a new test case uses values generated in Tor to verify this). This is incomplete -- the subkey signing code is still not implemented; it has to be adapted to create a signature from a PrivateKey rather than a SecretKey which will probably requiring working around/reimplementing some of what libsodium does for creating a signature since it expects "secret keys" i.e. the seed.	4 years ago