Nothing about this website really gives a whole lot of confidence. It claims to be "Started from US", but the broken English that's prevalent on every single page says otherwise, there's no information about what company is supposedly behind its creation, and the webserver is behind cloudflare. Both the git repo and the website proper are filled with broken links and errors, text that does exist readably is close to complete nonsense.
> Traffic over OmniEdge is end-to-end encrypted by Twofish/AES128/ChaCha20 cipers' P2P MESH network.
I'm grasping at straws to find a single thing which looks legitimate about it. You'd have to be completely nuts to even begin looking into this as a solution for anything.
If you're interested in what the technology behind this is, it's just a thin veneer of https://github.com/ntop/n2n.
Supporting Twofish is really bizarre. It's basically dead and would be slow compared to AES or ChaCha unless someone rolled their own SIMD implementation (why?). AES128 is weird too since 128-bit key ciphers are kind of deprecated unless your target is a fridge magnet.
AES256 or ChaCha20 would be sane as they are both roughly equivalent security-wise (in practice, people will debate theory) and both still recommended for use in new stuff, but most cryptographers would recommend that you pick one and only one of these two for a new system unless something forces you to support both.
Agreed. It's also super weird to have designed a new protocol that supports multiple cipher suites, it's very well established through the design of SSL and SSH now that there is absolutely no place for cipher negotiation in protocols.
Yeah, right now any new protocol should pick either ChaCha if you want to be fast on general purpose hardware and/or be hipster certified or AES (256) if you want to be fast on AES accelerated hardware and/or be FIPS(ter?) certified. I can't think of a single reason to pick anything else right now or to support negotiation.
The reason negotiation is in this product is that the underlying code is actually from 2008, which explains why the cipher selection exists in the protocol, as well as the inclusion of TwoFish.
Thank your for mentioning OmniEdge.
Founder here.
OmniEdge is founded by a single tweet from twitter. We are bringing everything into intranet. Computers, Cloud instances, MacBooks, Mobile Phones, Homelab servers, Docker containers, and Github action (https://github.com/marketplace/actions/omniedge-for-github-a...).
OmniEdge is built by a global remote team. OmniEdge uses the N2N as the protocol, and is backed by the N2N team. The founder of N2N Luca is technical advisor of OmniEdge.
We attended the ntopconf2022 in Italy, and gave a presentation.
24 comments
[ 3.1 ms ] story [ 47.9 ms ] threadhttps://vpn.net/
I've using it on few Linux boxes and Macs. Awesome service!
> Traffic over OmniEdge is end-to-end encrypted by Twofish/AES128/ChaCha20 cipers' P2P MESH network.
I'm grasping at straws to find a single thing which looks legitimate about it. You'd have to be completely nuts to even begin looking into this as a solution for anything.
If you're interested in what the technology behind this is, it's just a thin veneer of https://github.com/ntop/n2n.
Supporting Twofish is really bizarre. It's basically dead and would be slow compared to AES or ChaCha unless someone rolled their own SIMD implementation (why?). AES128 is weird too since 128-bit key ciphers are kind of deprecated unless your target is a fridge magnet.
AES256 or ChaCha20 would be sane as they are both roughly equivalent security-wise (in practice, people will debate theory) and both still recommended for use in new stuff, but most cryptographers would recommend that you pick one and only one of these two for a new system unless something forces you to support both.
So yeah, weirdness abounds here.
Why is AES128 preferred over AES256 by browsers then?
https://www.ssllabs.com/ssltest/viewClient.html?name=Chrome&... https://www.ssllabs.com/ssltest/viewClient.html?name=Firefox...
I tend to derive trust that I put into a product from spelling errors, can't help.
OmniEdge is built by a global remote team. OmniEdge uses the N2N as the protocol, and is backed by the N2N team. The founder of N2N Luca is technical advisor of OmniEdge.
We attended the ntopconf2022 in Italy, and gave a presentation.
Go and check: https://www.ntop.org/ntopconf2022/
Thanks.
So you can access nodes/devices from CI workflows.
https://github.com/marketplace/actions/omniedge-for-github-a...