ewindisch
The primary finding relevant to most users is the privilege escalation vulnerability in the opensource tailscale ssh server, when port forwarding is enabled (default), users may escalate privileges to root on the destination server.
The secondary finding is the ability to route to arbitrary subnets accessible via a host offering an App Connector. This is the one that really worries me, in regard to impact.
The third most important finding may be the `tailscale serve` authz bypass opportunity, but I suspect this may not impact many users. It may be significant in unlucky configurations.
Much of the report focuses on the security model and architecture of the software, with explanations of live scenarios conducted in our lab. Our concern is that an attacker could establish a foothold via something like a PHP exploit or supply chain exploit on a host, then `tailscale ssh` to another host and escalate, or route through an App Connector. They may even leverage the tailscale serve authz mechanism for an app-level privilege escalation for lateral movement. It is true that well managed policies mitigate some of these risks.
This report was called Tailworm because the research focused on the threat of a worm against an opensource headscale+tailscale network, and the capabilities of our agentic systems to defend autonomously against lateral movement across our systems. Our lab focuses on building secure infrastructure for recursive self improving intelligence, and this was the report from the red side of the experiment.
Finally, I believe we live in an age of continuous disclosure, continuous development, continuous integration, and continuous deployment. That's how we get through this.
>300 merged PRs/week
Astra low on the $200/mo "20x Pro" plan gets me through a single day.
git on my personal account (not an official Tor project):
AMA!
IOpipe provides tools for developers of serverless applications, helping devs and operators deliver and run with confidence. We are seeking to grow our team with strong candidates with a comfort in remote work, collaborative and product-driven development.
Our stack is built on AWS Lambda, Kinesis, Elasticsearch, React, and AWS Fargate.
Roles: Site Reliability Engineer (SRE) Solutions Architect
Hiring portal: https://hire.withgoogle.com/public/jobs/iopipecom
AWS also offers some of these pieces fully integrated via CodeDeploy (which we do not ourselves use).
Over in Microsoft land, Azure Functions natively supports Powershell according to this blog post: https://david-obrien.net/2016/07/azure-functions-PowerShell/
Multi-region S3 failover /w Route53
Laptops across the border: Best practices /w Chromebooks
Still, you're right that there's a logistic issue of physically locating, networking, and powering these devices.
IOpipe is seeking SENIOR candidates for remote, full-time positions:
- Senior Frontend Engineer: you will work on our real-time dashboard building the visual and interactive elements of our service. Seeking candidates with experience in React and charting / visualizations using D3.
- Senior Backend Engineer: You live in NodeJS and/or Go and want to build a great API that processes lots of data, really fast. The ideal candidate will have experience with Kafka, Kinesis, and/or Cassandra.
About IOpipe - we offer application performance monitoring (APM) for serverless applications. We are a Techstars company and have just completed the Summer'16 program in NYC.
Contact [email protected]!