tylerflint

6 ms·

1.
Show HN: QTap DevTools – Chrome-style encrypted traffic inspector for Linux(qpoint.io)
30 points by tylerflint 8mo ago|0 comments
2.
by tylerflint 1y ago
Java is supported, but currently in the pro version. Since JavaSSL is implemented in Java code, which runs in the Java VM and not exported as static symbols that can be uprobe'd, there is a bit more involved to generate a bridge betwee
3.
by tylerflint 1y ago
Great idea! On an unrelated note, your work has inspired most of my career in Solaris/Illumos/Linux systems and honestly this project likely wouldn't have happened if it wasn't for all of your books/blogs/proje
4.
by tylerflint 1y ago
The short answer is that we only have to calculate the offset per go version, no expensive runtime scanning is required. The long answer is that the offsets are the byte alignment offsets for the go structs containing the pointers to the fi
5.
by tylerflint 1y ago
The main benefit is complete coverage. In production systems there are many different workloads with many different binaries, each with different build processes. Leveraging eBPF enables seeing everything on a system without having to adjus
6.
by tylerflint 1y ago
Just run the qtap agent on whatever Linux machine has apps running on it and it will see everything through the kernel vs eBPF. You can customize config and/or integrate with existing observability pipelines, but initially you just nee
7.
by tylerflint 1y ago
We have Go support, but it is not open sourced yet. Go is a bit more complicated but we were able to get it after some cave diving in the ELF formats. To give you a little insight on how this works, because Go is statically linked, we need
8.
by tylerflint 1y ago
Great point! Yes it supports both scenarios. Qtap scans the binary ELF (curl, rust, etc) and looks for the TLS symbols. If they were statically compiled the eBPF probes will be attached directly to the binary, if dynamically linked the prob
9.
Show HN: Using eBPF to see through encryption without a proxy(github.com)
259 points by tylerflint 1y ago|78 comments
10.
by tylerflint 9y ago
https://content.nanobox.io/nanobox-vs-docker-swarm-kubernete...
11.
by tylerflint 9y ago
That's the highest requested feature! Should be available in Q1 of 2018.
12.
by tylerflint 9y ago
fixing now. Thanks for the heads up
13.
by tylerflint 9y ago
https://nanobox.io/why-nanobox/nanobox-vs-heroku/
14.
by tylerflint 9y ago
Some of those aren't PaaS, but container orchestration frameworks. If you're reading this list of comparisons out of genuine interest, I would suggest also looking into Nanobox: https://nanobox.io
15.
Getting Social with Mastodon and Nanobox(content.nanobox.io)
2 points by tylerflint 9y ago|0 comments
16.
by tylerflint 9y ago
I don't mean to be controversial here, but I really don't think so. If you're a quality engineer, you should stay away from Magento at all cost. I recently tried to download M2 and take it for a spin. It's very apparent
17.
by tylerflint 10y ago
Nanobox supports many languages. We are particularly excited about elixir though!
18.
by tylerflint 10y ago
Nanobox is free for developers to use for personal and open source projects.
19.
by tylerflint 11y ago
I think you're right. Thanks for the advice!
20.
by tylerflint 11y ago
NFS will be the default adapter for nanobox, but can be disabled.
21.
by tylerflint 11y ago
This is an issue we just became aware of. Working on a fix as we speak.
22.
by tylerflint 11y ago
Thanks for the feedback. You might want to keep any eye on Nanobox Cloud ( https://nanobox.io/cloud/ ).
23.
by tylerflint 11y ago
Thanks for the heads up! Please keep in mind this is an open-source project in the pre-beta phase. Any contributions are welcomed!
24.
by tylerflint 11y ago
Yes, nanobox will try to auto-configure your environment for you. If you would rather define your environment or if nanobox can't auto-configure your environment, you can either: 1- Explicitly define your app's environment with th
25.
by tylerflint 11y ago
You're right, not every scenario can be handled automatically. For that reason, the Boxfile is king: https://docs.nanobox.io/getting-started/boxfile/
26.
by tylerflint 11y ago
I couldn't agree more. We literally just introduced the nanopack cloud-initiative on friday ( https://blog.nanobox.io/nanopack-a-new-vision-for-automated-... ). Bear with us, we'll get there!
27.
by tylerflint 11y ago
Everything that mist does is "right in erlang's wheelhouse". Erlang is awesome and the actual reason we moved golang had nothing to do with erlang vs golang. I responded to that in detail at another spot on this thread (curre
28.
by tylerflint 11y ago
That's a pretty accurate assessment. Mist could be conceptualized as a self-hosted replacement for pusher ( https://pusher.com/ ). It's designed specifically to address building realtime web apps.
29.
by tylerflint 11y ago
The actual reason is much less exciting than you might have hoped and actually has nothing to do with erlang vs golang... The erlang version has been running successfully for about 2 years and we haven't had any issues whatsoever (exce
30.
by tylerflint 11y ago
Yeah we hear ya. The nanopack cloud-initiative was just announced last friday ( https://blog.nanobox.io/nanopack-a-new-vision-for-automated-... ). We're getting there slowly but surely!

More ›