crosh: add DNS tools like nslookup or dig
Reported by
dscg...@gmail.com,
Jul 15 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9460.67.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.113 Safari/537.36 Platform: 9460.67.0 (Official Build) stable-channel kip Example URL: k Steps to reproduce the problem: 1. When opening crosh, nslookup not available. 2. Hit the keys Ctrl+Alt+t. After crosh prompt appears, typing nslookup returns "ERROR: unknown command: nslookup" 3. See item 1 and 2 above. What is the expected behavior? ...for nslookup, one of the most basic network/systems administration tools, to be available without entering developer mode. What went wrong? See above. Did this work before? No Chrome version: 59.0.3071.113 Channel: stable OS Version: 9460.67.0 Flash Version: Shockwave Flash 26.0 r0 I have no doubt the people developing ChromeOS/Chromium are all knowing/smart/wise(no sarcasum meant at all) but why is nslookup not apart of the suite of commands offered up at the crosh prompt. I suspect that there is some security implication that i'm not thinking of, however, would love to know why. Respectfully, Inquisitive Systems Engineer
,
Oct 24 2017
we don't ship nslookup or anything like that in CrOS today. so it isn't "just add the callback to crosh" and you're done. even if you switch to dev mode, the tools aren't available. nslookup is part of bind-tools and that package currently clocks in at ~24MiB. that's too big to add to the rootfs just to support a small number of devs. even if we cut out everything but the few actual useful tools (dig & host & nslookup), that's still ~6MiB because bind-tools ships its own resolver library. that's still too large at this point in time. if you are just trying to debug your local network settings, network_diag/ping/route/traceroute/etc... should cover that. also, Chrome Apps have access to raw UDP/TCP sockets, so you could in theory just write a JS program to run any DNS queries you want.
,
Oct 24
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 Deleted