On 14.01.2018 20:38, Tomas Vanek via OpenOCD-devel wrote: > On 14.01.2018 20:06, Tomas Vanek via OpenOCD-devel wrote: >> On 14.01.2018 18:01, Christopher Head wrote: >>> none of the above attacks would work if you had to, say, type a >>> password before OpenOCD would accept your Telnet (or GDB, or TCL, or >>> …) session. >> If OpenOCD would require a password it also needs a safe channel to >> transfer it. Drop telnet and use a ssh library instead? >> > And one more concern: gdb protocol has remote command so port 3333 is > as vulnerable as the telnet port. How do you want to secure it? How about a safe mode that disallows "dangerous" commands (eg. those that call external programs)? This would be a bit like "-dSAFER" on ghostscript, which disallows certain commands when processing untrusted input.
A new gdb remote command (eg. "login") might be used to transport the password - the user can put it in his gdb scripts, and the attacker will be blocked from doing bad things (at least to me, an attacker messing with my debug session is not a big problem as long as he can't get access to my machine or my data). cu Michael ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
