minimaltom
Joined 9 months ago
Joined 9 months ago
If all your tailscale-ssh ACLs allow you into an account with sudo, or allow you into root, theres no impact (you cant do anything with these vulns you couldnt do a month ago). Thats the nuance I'm trying to get across (admittedly my english is bad).
Having done my own review of the vulns and the fixes as they are landing in github, its pretty clear to me that this only affects situations where you use ACLs to permit ssh into a node (via tailscale ssh, not via opensshd), but dont give a path to sudoers/root.
If a user had no SSH access and/or connectivity to a vulnerable node, none of these vulns give them access.
However, if you have a vulnerable tailscaled and you give ssh access as some non-root account/privs, then yes, these vulns are relevant as theres now known privilege escalations that give access beyond some specific user account.
Not trying to play down the vuln (its important), but its not a free-for-all RCE that some ppl are acting like it is.
Is there anything like a getting-started for working with MACE or orbmol, a 'hello world'? Like maybe simulating Allolactose binding to lac1 ?
Very cool
For example, that french dude that bet on a prediction market what the temperature would be, then broke into the weather station at the airport with a hair dryer. The prediction was still specific and falsifable!
One pony’s trash is another pony’s treasure, so I guess here one persons pedanticism is another persons hobby.
Bad (form) prediction: OAI is gonna be wobbly in a bit Good (form) prediction (could be totally wrong): OAI as we know it today is going to collapse due to running out of money around/at 20xx.
And sure we can be pedantic about detail, but the litmus test is: is the prediction useful if you had a crystal ball and you could know if it was true/false a priori?
Another fun fact: there’s a list of things with tails.txt and scales.txt (see GitHub) and that list is used to generate the random tailnet name :)
(Or at least it used to, it’s been years)