~ WTV SECURITY INDEX ~
client:showser Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Fri, Sep 29, 2000 From: ulTRAX@webtv.net I was looking for the second IP list... thinking it could be accessed in the same way the original is. My first try was client:showservice.... it worked.... but then so did showser and services23. Odd. Why the need for SHOWservices when cleint:services would suffice? Is client:show a generic command that can be appended? showusers? showsetup? showcookies? No luck so far...
Re: client commands that cause poweroffs Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sat, Sep 30, 2000 From: ulTRAX@webtv.net Most of us know there are some client commands that cause the box to poweroff. I'm not referring to commmands intended to do so but seem to do so accidently. Such a reaction from the box is interesting and must mean the command is similar to a valid command... I think we should make a list of these commands and look for similarities. I'll need to go back to the main client list but two I found today client:showromindex client:showromdata Probably client:showrom might do the same
Re: client commands that cause poweroffs Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sat, Sep 30, 2000 From: ulTRAX@webtv.net Seems client:showrom or client:showromXXXXX will cause a poweroff. Why would the browser give any response unless there's something here. The ones below do not. But there must be client codes we haven't found... for example that take us to the Retail Demo. Are there codes that might show us ROM indexs? Who knows. client:showfile client:showfiles client:showfilerom client:showBYOISP client:showcodes client:showclient client:showpoweroff client:showposeroffcodes client:showsource client:showurl client:showindex client:showdirectory client:showcolors client:gotominibrowser client:gotomini-browser client:gotodemo client:gotoretaildemo client:gotoattractloop client:gotopoweroff client:gotopoweroffcodes
Re: client commands that cause poweroffs Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sat, Sep 30, 2000 From: efficient2@webtv.net (examine) As I was told by a wni worker ..... "From the inside their is not such thing as a complete list of client cmds" so their is no telling what might and is out their by exploring the client url/cmds list
Re: client commands that cause poweroffs Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sat, Sep 30, 2000 From: glitchx@webtv.net (- g l i t c h -) you also have to think about what goes after the client codes like client:confirmblah?blah=blah&blah2=blah2 there are a few codes that wont do shit (well a few will power you off lol) unless you add that stuff to the end...
Re: client commands that cause poweroffs Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sat, Sep 30, 2000 From: BASICII@webtv.net one in particular that powers me off for 30 minutes is Client:ShowSecurityInfo go figure...
Re: client commands that cause poweroffs Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sat, Sep 30, 2000 From: ulTRAX@webtv.net glitchx wrote "you also have to think about what goes after the client codes like client:confirmblah?blah=blah&blah2=blah2 there are a few codes that wont do shit (well a few will power you off lol) unless you add that stuff to the end..." Ya... I just figure that maybe there's some generic client commands like show and goto that we may be able to deduce... and mabye the fact that we're being powered off is a sign we're on the right track. Then we can look at making a string.
Re: [efficient] commands that cause poweroffs Help Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sat, Sep 30, 2000 From: ulTRAX@webtv.net efficient2 wrote: As I was told by a wni worker ..... "From the inside their is not such thing as a complete list of client cmds" so their is no telling what might and is out their by exploring the client url/cmds list" I have a problem with the idea that there's no list of specific client commands. The may vary from build to build but what is the alternative? One possibility is there's some formula based on syntax... for instance client:gotoXXXXX or client:showXXXX. The latter might allow the display of all sorts of internal client/rom info. But even this has to have a limited list of items it can display.
Re: [BASIC] client commands abbreviated? Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sat, Sep 30, 2000 From: ulTRAX@webtv.net BASICII wrote: "one in particular that powers me off for 30 minutes is Client:ShowSecurityInfo" Ya, that's one I remember. But I just noticed that it powers the box off just using "client:showsec". Since "showservices" works using only "showser" it's almost as if these client commands will work with just enough info to decided which ones they're supposed to be. If true it explains why three letters are needed. In this case just to use "showse" would not any differentiation between "showsec" and "showser".
Re: client command mystery deepens. Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sat, Sep 30, 2000 From: ulTRAX@webtv.net Hmmmm.... actually it's not "showrom" that causes the poweroff it's just plain "showr" I went though the entire alpahabet from "showa" to"showz" and only "showr" has this effect. As for ""showser" I went though the entire alpahabet and between "showsea" and "showsez" only "showsec" causes a power off. The mystery deepens.
Re: client command mystery deepens. Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sat, Sep 30, 2000 From: JO5H@webtv.net (J05H) ulTRAX you really seem to be on the right track with the three letters... client:reload can be shortened to client:rel Hmmmmmm.......
Re: client command mystery deepens. Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sat, Sep 30, 2000 From: efficient2@webtv.net (examine) We need to think big...... I'm not sure what other people wanna find exploring the client urls but.... Hopefully you what to find something that has not been discovered. Me and a few others ('flashrom-,Jo5h and hackerreamer)have been exploring the upgrade path with the new classic and old plus. client:updateflash?ipaddr=? allows the old classic to use IP#s to access client builds When Nap found the personal service we found a new client url called UpgradePath Matt was the first to use java to grab the full url then I did the same thing. client:poweroff?minibrowser&autoPOWERON&upgradepath=content/etc etc what is even funnier is that this url is very old but new to our eyes.The server that the code came from was last updated feb99. Don't think small unless thats were you wanna start to build big I know ,no matter who says different that their is a client url thats works for the plus and new classic that will allow us to use IP#s to access flash builds. And if you know the webtv system as many in here do you know what can be done with that url and method
Re: client command mystery deepens even deeper Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sun, Oct 1, 2000 From: glitchx@webtv.net (- g l i t c h -) i just noticed when you access client:showrom while offline you don't get powered off it just shows the little box in the corner but it never moves, i think thats really weird... showsec still powers you off though... so showrom must be something dealing with offline/poweroff codes, but i think thats already been said heh
Re: client command mystery deepens even deeper Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sun, Oct 1, 2000 From: limdog@webtv.net (limdog) A very large # of client urls were abreviated this year. i first noticed it in april. client:opense client:openp client;gototsec etc.(perhaps this byte shaving is to free up a little memory?) and the client urls are stil active with search criteria added after the shortened version. client:sendp?address=your_email_here@webtv.net works just as the longer client:sendpage?address= does. As far as "generic" client: urls to explore let's not forget client:open. with that base generic url i found client:openl which leads to a .htpasswd directory. Is it passport? vega? who knows.... unfortunately we can not code read client "urls."
Re: client command mystery deepens.(Ultrax&JO5H) Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sun, Oct 1, 2000 From: WbWzrd@webtv.net (WbWzrd JJ) It can't be reduced to three for everything, or how would it diferentiate between client:relogin and client:reload if just limited to client:rel ?!? Have a Great Day! WebWizard Jerry
Re: client command mystery deepens even deeper Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sun, Oct 1, 2000 From: ulTRAX@webtv.net limdog wrote: "A very large # of client urls were abreviated this year." Since client commands are client based... they probably could not have been abreviated without a client change. I'm still running 2.2.6.1 from last fall so any abbreviation must have been introduced then or maybe has always been the case.
Re: [WW]client command mystery deepens. Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sun, Oct 1, 2000 From: ulTRAX@webtv.net WbWzrd wrote: "It can't be reduced to three for everything, or how would it diferentiate between client:relogin and client:reload if just limited to client:rel ?!?" Since the abbreviation is real then it may be limited to the mimimum number of letters needed to diffirentiate one command from another. In the case of SECurity and SERvices three letters is all that is needed. But who knows what's going on.
Re: predicting client commands Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sun, Oct 1, 2000 From: ulTRAX@webtv.net If we can find the "rule" WNI uses to abbreviate these commands then this opens up a whole new area for predicting new commands. Maybe we already have that "rule. "showSER" and "showSEC" seem to indicate the minimum number of letters needed to differentiate one command from another. "openF", "openG", "openL", "openP", also bare this out. If this was the general rule then we could build up from these base commands. It'd take some time to go through the variables showaa, ab, ac, then aaa, aab, aac..., then doing the same with other "generic" client commands like "goto" and "open". If we get no response, say from "openA"... then we can try "openAA" etc. But I suspect the "show" commands might be more interesting. (that is unless we finally find the Japanese Keyboards LOL "openJAPK"?) This is much more manageable a project then trying to do the same with a few billion PO codes. The only fly in the ointment is whether there are gaps.... Is "openL" the ONLY "openL......" available?
Re: client command mystery [lim] Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sun, Oct 1, 2000 From: ulTRAX@webtv.net Limdog wrote: "let's not forget client:open. with that base generic url i found client:openl which leads to a .htpasswd directory. Is it passport? vega? who knows...." All I get from these client:open commands are panels. "openF" = FIND panel, "openG" = GoTo, "openL" = LOGIN (PW), "openP" = PRINT. Can you C&P the info you're finding or give up a screen shot? What box and build you running?
Re: anyone any good at JS? Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sun, Oct 1, 2000 From: ulTRAX@webtv.net Predicting client commands would be methodical and limited enough that it might lend itself to a JS script crack... basically blending a PW cracker with an accessor.... It could start with the "client:show" commands... maybe going 4-5 letters in depth. Then be reprogrammed for "client:goto" and any other generic client command. The session might be best being videotaped since you never know what might power of the box... If that was the case the commands used would have to be displayed as they are executed. Just a thought... maybe not a very good one.... but....
Re: client command mystery [lim] Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sun, Oct 1, 2000 From: limdog@webtv.net (limdog) Ya it's just the panel. 2.5 something or the other. Nice mystery tho. Here's one prob with theory of minimum characters to differentiate: client:logontopage and client:logoshown. now only yields logoshown and may be abbreviated down to client:logo
Re:[glitch] client command mystery Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Sun, Oct 1, 2000 From: ulTRAX@webtv.net glitchx wrote: "i just noticed when you access client:showrom while offline you don't get powered off it just shows the little box in the corner but it never moves," The funny thing is... now that we know the client commands can be abreviated.... we may never know what "showr" really stands for. I was just toying with commands when I tried "showrom" which I shortened to "showr". But it might not be "rom" at all. It could be "showreset" or "showredrover". This differs from "showsecurityinfo" becuase that command was first found in the viewer. So, that being said... it doesn't mean it can't be "showrom" either. Now we just have to find out what other commands yield Glitch's white box. "i think thats really weird... showsec still powers you off though... so showrom must be something dealing with offline/poweroff codes, but i think thats already been said heh"
Re: client:showser [examine ultrax] Group: alt.discuss.clubs.public.webtv.technical.ultrax Date: Wed, Oct 25, 2000 From: JGreely-@webtv.net (J Greely) examine: I never knew where that url came from , Does anyone know if client:poweroff?minibrowser&autopoweron&upgradepath= . Works on a classic or not? i have been wondering if it did for awhile now , thanks ,~~JeFF ulTRAX u might consider the idea , that client commands are just that _commands_ it might not be just simple urls , but look @ the url above It seems like after each &sign is a diffrent command telling the box what to do , So in all actuallity there might not be a definative amount of urls because they can be interchanged to accomplish what a user/tech might need , hard to explain what i mean , but i hope u get the drift ~~JeFF