verspielt verspult 🫠

  • 0 Posts
  • 32 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2024

help-circle






  • mstsc.exe was exactly the one I used. I vaguely remember that I had used that successfully some years ago (in a much bigger environment with proper certs) and it worked.

    Regarding NLA: I believe that I would have to disable that on purpose no? It was on a very vanilla Windows 11 install. I just looked and regarding any other settings than the ones listed in mstsc.exe, I get told that Windows 11 Home edition doesn’t support RDP lol.


  • I recently used the old Windows RDP client they refer to. I tried to connect to a Windows VM and it didn’t work. Had to pull out some old log utility tool and filter a while to recognize the server didn’t use a valid TLS certificate (lives inside a VPN) and the handshake failed. Tried disabling cert validation (although I’m not sure if that one obfuscated option did exactly that), still no luck.

    I then tried KRDP in KDE. It asked me if I’m sure I wanted to connect since the cert is self signed. It even showed me the cert info and I know the issuer in person. I accepted and got in. Easy as that.


  • This is a great summary. Also, see the GrapheneOS teams list of hardware prequisites. They have said themselves before that this is not a very high bar, but that there are just no other manufacturers focusing on security. Apple claim they do, and get recommended as second best option in the forums sometimes, but given the walled garden approach, it must be next to impossible to develop against, even if they unexpectedly completely open up their ecosystem.

    They would probably also have to take a lot of criticism for their implementation approaches and their brand integrity would suffer immensely. Maybe there would even be some new undisclosed vulnerabilities to fix, like the goto fail bug breaking SSL encryption ten years ago.

    Compare it to the new open source Nvidia drivers for Linux, they have taken quite a while to develop since Nvidia announced the release, and I don’t know if they have yet reached the performance levels of the proprietary ones. Doing this for a whole Phone, given they even fulfil the requirements hardwarewise, will probably take a decade. And in this decade, ten new iPhones will be released…



  • There are no phones with working encryption (a must imho and a lot of others) except the ones I listed in my initial comment. iPhones are no option because they are not unlockable. Samsung recently announced they will remove the option to unlock the bootloader as well. They also have a very broad and everchanging lineup of phones.

    Google Pixel has been more of a hardware and software reference to developers than a Phone people would usually buy up until the redesign with the Pixel 6. There are so many hardware and software features that make it the perfect device to develop against (up until the recent events lol).

    I’d recommend you to read their own documentation on this topic.










  • There are numerous benefits in IoT / smart home and ubiquitous computing. Used in the right ways it can make your life so much better and even save lives. It is just sad to see all the wasted potential, the greediness and straight up noncompliance with basic human rights and needs for simplicity and privacy in its design.

    Funny enough, it got me into reading some threads of people reverse engineering air fryer APIs (didn’t expect that to ever happen) and it reminded me again of how great and compassionate some people are. Makes the stupid cat and mouse game seem even more stupid when 3 guys in their spare time can rebuild a 5 layer deep authentication stack with some unknown Philips / Xiaomi server that probably needed tens or even hundreds of engineers to build in an obfuscated manner in the first place.