Re: Link to crosh.html?

[ksz...@gmail.com]

I second that! Running into the same problems!

Kszys.

[Nicholas Evans]

The stable channel was updated to M31 on Friday, so "Crosh Window" is broken for everyone now.  It took me a couple of hours this morning before I found a hacky solution: enter document.location = "crosh.html" in the JS console.  My search was frustrated by out of date recommendations in the official docs [0], which really ought to be updated.  Obviously, a link or a button or a server entry or an icon in the app launcher would be preferable to that hack.

[0] http://git.chromium.org/gitweb/?p=chromiumos/platform/assets.git;a=blob;f=chromeapps/nassh/doc/chromeos-crosh.txt

-- 

Nick

[Robert Ginda]

I've added a special ">crosh" hostname to Secure Shell.  I'll also be adding crosh.html to the web_accessible_resources, which will probably fix crosh window.

I'll release to secure shell dev later today with these fixes and a few others that have built up recently.

Rob.

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/6db746b1-b272-4620-acc7-4c0344ed547b%40chromium.org.

[Michael Orr]

Thanks for your work on this Robert. I grabbed the new dev version of Secure Shell from the webstore but I'm seeing no change in crosh-window and am unable to get Secure Shell to connect to the ">crosh" hostname. It's more likely that its a case of user error, I'm just wondering if there's something that I'm missing.

[Robert Ginda]

Are you sure you're on 0.8.22.2?  Sometimes the webstore takes a little while to update everywhere.

If you are, I'll need some details.  Maybe a screenshot of when it fails, an error message, or something useful from the JS Console?

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/8eca9eff-ee7a-413b-bc61-e94b45301a52%40chromium.org.

[Robert Ginda]

I just noticed that you have to enter a username to get >crosh to work.  I forgot to point that out.  Whatever you use will be ignored, but the connect dialog won't let you try to connect without a username.

[Michael Orr]

Yes, I'm on 0.8.22.2. Adding a username fixed the issue for "logging in" to >crosh, thank you very much. Like I said, user error.

This is a good enough solution for my use case, but Crosh Window still goes to about:blank. I wasn't sure if that was expected to be fixed with your change to web_accessible_resources or if Crosh Window won't see that change until your change hits Secure Shell stable. If you want more debug output I'd be happy to provide. Thanks again. 

[Robert Ginda]

+adlr

Ah yeah, it's likely that crosh window is hardcoded to open secure shell stable.  Andrew would know.

Rob.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/b1adc339-fdec-40cf-9b66-13e6d5341507%40chromium.org.

[Andrew de los Reyes]

Yeah, Crosh Window is hard-coded to use stable. The source code is pretty clear (all 1 line of it)

https://github.com/adlr/croshwindow/blob/master/main.js

-andrew

[Michael Orr]

FWIW, I manually changed my local copy of the Crosh Window extension to point to the Secure Shell beta extension hash and it works as expected. Perhaps the behavior could default to using beta if it exists, stable otherwise?

[andyt...@gmail.com]

Can you explain or point me to the exact steps to get a crosh shell in a separate window again?  I can't connect to chronos or localhost using the secure shell app.  And obviously, running crosh in a tab prevents CTRL+w usage which I need for dev work.

thanks in advance

[William Wraith IV]

I just started using the latest fix (the "Secure Shell (dev)" app) to get easy access to a crosh window via crosh.html in the secure shell app, and I am just summarizing here my understanding hoping to be helpful to those who are just users of the crosh/secure shell apps and want to get around the broken crosh window. 

I am using "Secure Shell (dev)" located here. This is not "Secure Shell" but a separately released modified version of the normal "Secure Shell" app for users needing the crosh window functionality. Note you must be subscribed to the chromium-hterm mailing list to access the link. Also, the release notes say this is a temporary fix before moving to a v2 app. As I understand it, the Crosh Window app and Secure Shell apps (permissions problems) have been fixed so that the "Crosh Window" app should work again. However, the new versions of the apps don't seem to be updated in the stores yet, at least not to everyone, as my versions haven't updated.

If you visit the link, you can install it normally. It will have a different icon in your apps pop-up menu window. As far as I can tell, it co-exists with the regular Secure Shell app, which I still use for a lot of presets I have there. Once the "Secure Shell (dev)" app is installed, you can launch it. If you put ">crosh" in the hostname field (without the quotes), and enter any username (doesn't matter what username), and hit enter, (you don't click on the connect button), you should be able to launch the usual crosh window. You still have to change the font size and all that, as mentioned in the manual you can read by visiting the link in the app window at the top. Note the manual discussion about launching a crosh window was out of date and incorrect, the last time I read it.

For the time being, you have to use the "Java Console" to make changes to preferences, and you can also use it to launch "crosh.html" (the crosh shell part of the Secure Shell app). To get there, you focus on the window of the app you want to change and type ctrl-shift-j. This will bring up the "Java Console". You can type in some programming lines as mentioned in the manual to change preferences, for example typing term_.prefs_.set('font-size',10) followed by enter key will change the font size to 10.

Finally, if all else fails, you can use the Java Console (reached by ctrl-shift-j after focusing on the app window) to change the document location to the crosh shell within the Secure Shell app by typing in the Java Console, the line: document.location='crosh.html' followed by the enter key. The app window should switch to a crosh shell. This works fine, but it is just cumbersome.

My apologies in advance for any errors in what I've summarized here. I hope this somewhat lengthy post is not annoying to the developers or moderators. It is not at all my intention to cause any problems or propagate any incorrect information. However, having spent a lot of time playing with the alternatives when the Crosh Window app stopped working, I thought it could be helpful to have this summary of all the snippets gathered from various places. 

[Robert Ginda]

Step 1: Join the chromium-hterm mailing list to gain access to the dev version of Secure Shell: https://groups.google.com/a/chromium.org/forum/#!forum/chromium-hterm

Step 2: Install "Secure Shell (dev)" from https://chrome.google.com/webstore/detail/secure-shell-dev/okddffdblfhhnmhodogpojmfkjmhinfp

tep 3: Launch "Secure Shell (dev)"

Step 4: Add a connection for username "crosh" and hostname ">crosh".  (Actually, the username can be anything).

Step 5: Connect to that host.  (Press enter, or click Connect, both should work.)

Later this evening (Pacific Time) I'll update the "Secure Shell" app to match "Secure Shell (dev)", so you'll be able to skip the mailing list and dev install.  The "crosh window" extension should start working again once "Secure Shell" has been updated.

Rob.

[Christopher]

want link to crosh pls

On Monday, November 4, 2013 at 10:02:58 PM UTC-8, sombrad...@gmail.com wrote:

The beta and dev channels of Chrome are disallowing apps navigating to or opening windows with another app's chrome-extension:// URL, probably for security reasons. As a result, the Crosh Window app no longer works, because it's not allowed to open a panel with Secure Shell's crosh.html. I spend a lot of time in a local shell on ChromeOS, so this has been bugging me for a little while. I ended up editing the manifest to open CroSH directly, but clearly that's a scalable solution.

Would it make sense to add a link in the initial nassh.html dialog so that users could just jump directly to the local shell from the Secure Shell extension, or having it as a pre-existing server entry? This way, people like me could get to the local shell, but it would still fulfill its main function of accessing remote servers.

Thanks,

Thomas

[metno...@mischools.org]

[metno...@mischools.org]

take me to crosh thing looks like wer kackes

[Robert Ginda]

It's not there by default, but you can specify a host of ">crosh" in Secure Shell to launch crosh.

--

You received this message because you are subscribed to the Google Groups "chromium-hterm" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/509dce13-f62f-4ee5-8b77-fa92f386cbc2%40chromium.org.

[bryce...@gmail.com]

If youare wondering how to access rosh on a device just hit ctrl alt T

[montejo...@my.putnamschools.org]

[montejo...@my.putnamschools.org]

hello kids

[montejo...@my.putnamschools.org]

[eathan...@gmail.com]

um i can't search croch for some reason

[wcu...@student.psasb.us]

[bbar...@norwood63.org]

hofdj

[sea...@waipahihi.school.nz]

you very gay arses

[Mike Frysinger]

i wonder what it is that encourages random people to locate this specific thread and then spam it.  we've had at least 4 or 5 punters thus far.  curious.

-mike

--

You received this message because you are subscribed to the Google Groups "chromium-hterm" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/10cdd48c-1400-4ea4-ad62-e9287e834512%40chromium.org.

[michael...@taylor.k12.in.us]

[firefis...@gmail.com]

chrome-extension://nkoccljplnhpfnfiajclkommnmllphnl/html/crosh.html

[zabina...@gmail.com]

Have sex with my

[lauren...@ousd.us]

bitch

[pk06...@gmail.com]

[princ...@tis.edu.mo]

chrome-extension://nkoccljplnhpfnfiajclkommnmllphnl/html/crosh.html

[317...@nhesd.net]

Luis