Simply put, these changes destroy my application's ability to function, and that of Termux as well. The linked article - and others - explain that in Android 10+, (a) executable binaries can no longer reside in a read/write directory, and (b) access to /sdcard will go away. I should add that Termux is basically saying the same thing I am - they see this as the end of their current operational model as well, and who are also giving up. So a move away from an open environment is inevitable. Google also has to compete with Apple's iOS platform, which seems much more secure. They need to tighten up security to stay ahead of the black-hats who see Android as a way to access the mobile resources of Android's users - personal information, bank accounts, and so forth - users who aren't necessarily technical but who have valuable resources located on their devices and who rely on the security and integrity of this mobile platform. I plan to say I understand and appreciate Google's position. If I may impose, perhaps one last time, on behalf of all SSHelper users (when you get a chance, obviously):ġ) Can you move your "final message" to the top of the page to make it more visible? I'm planning that. I have successfully reinstalled your version 130 and it's working again. I can only imagine the frustration you must be feeling! Yes, it's frustrating, but I understand where Google is coming from, and their priorities. If you do not want to enable discovery, you can start msvsmon from the command line with discovery disabled: Msvsmon /nodiscovery.Paul: I just read your main page, at the bottom, where you announce the final version of SSHelper. This is a standard port for discovery, so the port number cannot be configured. It is used only for discovering a machine running the remote debugger, so it is optional if you have some other way of knowing the machine name or IP address of the target computer. UDP 3702 is used for finding running instances of the remote debugger on the network (for example, the Find dialog in the Attach to Process dialog). Azure App Service uses port 4024 for the remote debugger. Currently, Azure App Service does not use the default ports associated with your version of Visual Studio. Remote Debugger Ports on Microsoft Azure App Service This port is configurable from the command line: Msvsmon /wow64port. If you run the 32-bit remote debugger, it uses 4024, and 4025 is not used.
If you debug a 32-bit process, the 64-bit version of the remote debugger starts a 32-bit version of the remote debugger on port 4025 (the main port number incremented by 1). When the 64-bit version of the remote debugger is started, it uses the main port (4024) by default.
0 kommentar(er)
