[Multi Unlock Software V64.00 Cra
Rapheal Charlton
I've just updated to v64 today, while the pass through experience is much better, I noticed that multi-modal (where the quest tracks both controller and hands at the same time allowing for instant swapping between them, or even controller in one hand and hand tracking on other hand.) wasn't working anymore. I've tried looking in settings, couldn't find a way to enable it. I've also tried restarting quest, turning hand and body tracking off and on, and it still would not work. Has anyone else had this problem, if so could you solve it? Thanks.
Hey there, @raygon2000! Thanks for bringing this to the Meta Community Forums! From what I've found, it doesn't appear the multi-modal tracking feature doesn't work in conjunction with body tracking at the moment. You may need to have body tracking disabled in order to take advantage of the multi-modal tracking feature. It's also worth mentioning that fast and wide hand tracking cannot be enable in order to utilize multi-modal tracking. If you don't mind giving this a try (disabling the previously mentioned tracking settings) to see if multi-modal tracking works properly, it would be great appreciated! If you're still having troubles after turning of the settings, please let me know, as I want to bring this up to our internal team to look into further if the feature isn't currently functioning as intended. I hope to hear from you soon!
That is strange. I was able to have multimodal enabled, while also having body tracking in games. Wide hand tracking on the other hand, I also don't believe I can turn off body tracking since body tracking and hand tracking are combined in one on/off switch. Turning one off turns the other off too. Wide hand tracking, I don't know where the setting for that is, I have tried looking.
Hey, @raygon2000, thank you for trying those steps and my apologies for the late reply. That's certainly interesting, because from what I can tell the feature wasn't removed from any of the release notes. I'd recommend using the "Report a Problem" feature, so that out engineers can collect some information and have a better chance of resolving the issue. I'd recommend trying to join the PTC to see if v65 has corrected any of these bugs as I've seen most soft patches go live in the PTC before the live test channel. Here are some steps on how to join the PTC: Meta Quest PTC. I hope this is able to help! Please feel free to share any update or news you come across along the way!
I also have a Meta Quest 3, with update version 65. My friend has the same headset. It has a multimodal feature that mine doesn't have. This feature is not activated anywhere in the settings. What should I do? How can I enable it? And yes, I connected to PTC but to no avail. All the same functions are enabled as my friend, but again, he has this function, I don't..
Thank you for the requested information, @AborigenNik! I've gone ahead and provided the team with this information to see if we can get some answers about this feature not working properly. I'll keep an eye out for updates from the team, and I'll be sure to relay them here when I do. Thank you both for your patience during this time! Feel free to let me know any other information that may be of use to the team!
Hey everyone! I got an update from the team, and it appears they were already aware of this issue, so it's actively being worked on! I'll continue to reach out to the team for updates regarding a resolution to this issue and I'll be sure to provide any news I receive here. Thank you all for your patience!
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
In 2021, I finally spent some time looking at a consumer router I had been using for years. It started as a weekend project to look at something a bit different from what I was used to. On top of that, it was also a good occasion to play with new tools, learn new things.
I downloaded Ghidra, grabbed a firmware update and started to reverse-engineer various MIPS binaries that were running on my NETGEAR DGND3700v2 device. I quickly was pretty horrified with what I found and wrote Longue vue ? over the weekend which was a lot of fun (maybe a story for next time?). The security was such a joke that I threw the router away the next day and ordered a new one. I just couldn't believe this had been sitting in my network for several years. Ugh ?.
Anyways, I eventually received a brand new TP-Link router and started to look into that as well. I was pleased to see that code quality was much better and I was slowly grinding through the code after work. Eventually, in May 2021, the Pwn2Own 2021 Austin contest was announced where routers, printers and phones were available targets. Exciting. Participating in that kind of competition has always been on my TODO list and I convinced myself for the longest time that I didn't have what it takes to participate ?.
This time was different though. I decided I would commit and invest the time to focus on a target and see what happens. It couldn't hurt. On top of that, a few friends of mine were also interested and motivated to break some code, so that's what we did. In this blogpost, I'll walk you through the journey to prepare and enter the competition with the mofoffensive team.
At this point, @pwning_me, @chillbro4201 and I are motivated and chatting hard on discord. The end goal for us is to participate to the contest and after taking a look at the contest's rules, the path of least resistance seems to be targeting a router. We had a bit more experience with them, the hardware was easy and cheap to get so it felt like the right choice.
At least, that's what we thought was the path of least resistance. After attending the contest, maybe printers were at least as soft but with a higher payout. But whatever, we weren't in it for the money so we focused on the router category and stuck with it.
Out of the 5 candidates, we decided to focus on the consumer devices because we assumed they would be softer. On top of that, I had a little bit of experience looking at TP-Link, and somebody in the group was familiar with NETGEAR routers. So those were the two targets we chose, and off we went: logged on Amazon and ordered the hardware to get started. That was exciting.
The TP-Link AC1750 Smart Wi-Fi router arrived at my place and I started to get going. But where to start? Well, the best thing to do in those situations is to get a root shell on the device. It doesn't really matter how you get it, you just want one to be able to figure out what are the interesting attack surfaces to look at.
As mentioned in the introduction, while playing with my own TP-Link router in the months prior to this I had found a post auth vulnerability that allowed me to execute shell commands. Although this was useless from an attacker perspective, it would be useful to get a shell on the device and bootstrap the research. Unfortunately, the target wasn't vulnerable and so I needed to find another way.
After googling a bit, I found an article written by my countrymen: Pwn2own Tokyo 2020: Defeating the TP-Link AC1750 by @0xMitsurugi and @swapg. The article described how they compromised the router at Pwn2Own Tokyo in 2020 but it also described how they got a shell on the device, great ??. The issue is that I really have no hardware experience whatsoever. None.
But fortunately, I have pretty cool friends. I pinged my boy @bsmtiam, he recommended to order a FT232 USB cable and so I did. I received the hardware shortly after and swung by his place. He took apart the router, put it on a bench and started to get to work.
It was time for me to figure out which areas I should try to focus my time on. I did a bunch of reading as this router has been targeted multiple times over the years at Pwn2Own. I figured it might be a good thing to try to break new grounds to lower the chance of entering the competition with a duplicate and also maximize my chances at finding something that would allow me to enter the competition. Before thinking about duplicates, I need a bug.
At first sight, the following processes looked interesting:- the uhttpd HTTP server,- the third-party dnsmasq service that potentially could be unpatched to upstream bugs (unlikely?),- the tdpServer which was popped back in 2021 and was a vector for a vuln exploited in sync-server.
Because I was familiar with how the uhttpd HTTP server worked on my home router I figured I would at least spend a few days looking at the one running on the target router. The HTTP server is able to run and invoke Lua extensions and that's where I figured bugs could be: command injections, etc. But interestingly enough, all the existing public Lua tooling failed at analyzing those extensions which was both frustrating and puzzling. Long story short, it seems like the Lua runtime used on the router has been modified such that the opcode table appears shuffled. As a result, the compiled extensions would break all the public tools because the opcodes wouldn't match. Silly. I eventually managed to decompile some of those extensions and found one bug but it probably was useless from an attacker perspective. It was time to move on as I didn't feel there was enough potential for me to find something interesting there.
One another thing I burned time on is to go through the GPL code archive that TP-Link published for this router: ArcherC7V5.tar.bz2. Because of licensing, TP-Link has to (?) 'maintain' an archive containing the GPL code they are using on the device. I figured it could be a good way to figure out if dnsmasq was properly patched to recent vulns that have been published in the past years. It looked like some vulns weren't patched, but the disassembly showed different ?. Dead-end.
Why is there no process name associated with those sockets uh ?? Well, it turns out that after googling and looking around those sockets are opened by a... wait for it... kernel module. It sounded pretty crazy to me and it was also the first time I saw this. Kinda exciting though.
795a8134c1