It's supposed to be a Telnet connection.
To enable SSH:
- Navigate to http://192.168.1.1
- Click the Administration Tab
- Enable SSH
To enable SSH:
- Navigate to http://192.168.1.1
- Click the Administration Tab
- Enable SSH
It's supposed to be a Telnet connection.
To enable SSH:
- Navigate to http://192.168.1.1
- Click the Administration Tab
- Enable SSH
I've found it ...i had to go into the services tab and enable it there ...now under the administration tab it is no longer greyed out ...I'll try again thank youIve just done that but the tab to enable or disable SSH Management is grey'd out ?
y'all need to look at this. Some potentially groundbreaking progress has been made on private servers for wii over at the Monster Hunter Tri Private server project site:
http://www.sufami.org/thread.php?board=8&thema=23&page=1
Any thoughts on this as to its utility for a private Nintendo WFC?
The MKW people were already working on injecting their own SSL certificate, so hopefully this will be helpful to them. Don't know what he means by it being easier to crack though. A common serial number isn't really a cryptographic weakness since the serial number isn't used in any cryptographic operations. It's just something the CA uses to identify certs and is used in certificate revocation lists to point out compromised certs. (Which I doubt the Wii checks. All the dumps so far don't show any traffic to any CRLs.)y'all need to look at this. Some potentially groundbreaking progress has been made on private servers for wii over at the Monster Hunter Tri Private server project site:
http://www.sufami.org/thread.php?board=8&thema=23&page=1
Any thoughts on this as to its utility for a private Nintendo WFC?
Fixed that for you; seeing "y'all" written out makes my skin crawl worse than when I hear it.Everyone needs to look at this. Some potentially groundbreaking progress has been made on private servers for wii over at the Monster Hunter Tri Private server project site:
http://www.sufami.org/thread.php?board=8&thema=23&page=1
Any thoughts on this as to its utility for a private Nintendo WFC?
Fixed that for you; seeing "y'all" written out makes my skin crawl worse than when I hear it.
Not to derail but just to answer your question - I think most people are bothered by y'all because it's grammatically embarrassing and makes the speaker sound ignorant. That's my reason anywaylol, it's amazing how many people are bothered by a simple y'all.
So anyway, did y'all look at it and what did y'all think?
Right now we already have a couple ways of getting unencrypted traffic (Dolphin, game-specific hacks) and the only encrypted part of most games is the authentication, which is common across games and we already have a good amount of dumps for. The only other encrypted servers I found were download servers that have an almost identical API as the authentication ones. IOS patching will help in getting actual custom servers up and running, but DNS spoofing will still be necessary for all the unencrypted servers used in games.I've already mentioned this to someone on IRC, your best bet is to replace the SSL module of IOS.
It only has a few functions to emulate ( http://wiibrew.org/wiki//dev/net/ssl ) and this way you wouldn't have to patch any game code or inject certificates, or even spoof DNS.
The socket functions are implemented in libogc so this would be mostly copy&paste.
This way you can also capture traffic unencrypted.
The MKWii leaderboards are also transmitted encrypted (SSL).