Active Topics
-
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 4 hrs, 29 mins ago -
List of well performing apps on Leste (34)
to Maemo 7 / Leste by biketool - 1 day, 4 hrs ago -
Maemo repository (5)
to Community by dredlok706 - 2 days, 23 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 3 days, 2 hrs ago -
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 3 days, 19 hrs ago -
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 5 days, 8 hrs ago - more...
|
2008-04-10
, 11:15
|
|
Posts: 3,841 |
Thanked: 1,079 times |
Joined on Nov 2006
|
#13
|
This is a WPA-only problem I take it? I use a 64-char code in one of my configured WEP settings.
__________________
N800/OS2007|N900/Maemo5
-- Metalayer-crawler delenda est.
-- Current state: Fed up with everything MeeGo.
N800/OS2007|N900/Maemo5
-- Metalayer-crawler delenda est.
-- Current state: Fed up with everything MeeGo.
|
|
2008-04-10
, 11:18
|
|
Posts: 10 |
Thanked: 0 times |
Joined on Sep 2007
|
#14
|
I found something on wikipedia 
Security in pre-shared key mode
Pre-shared key mode (PSK, also known as personal mode) is designed for home and small office networks that don't require the complexity of an 802.1X authentication server. Each user must enter a passphrase to access the network. The passphrase may be from 8 to 63 printable ASCII characters or 64 hexadecimal digits (256 bits).[2] If you choose to use the ASCII characters, a hash function reduces it from 504 bits (63 characters * 8 bits/character) to 256 bits (using also the SSID). The passphrase may be stored on the user's computer at their discretion under most operating systems to avoid re-entry. The passphrase must remain stored in the Wi-Fi access point.
http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access
Security in pre-shared key mode
Pre-shared key mode (PSK, also known as personal mode) is designed for home and small office networks that don't require the complexity of an 802.1X authentication server. Each user must enter a passphrase to access the network. The passphrase may be from 8 to 63 printable ASCII characters or 64 hexadecimal digits (256 bits).[2] If you choose to use the ASCII characters, a hash function reduces it from 504 bits (63 characters * 8 bits/character) to 256 bits (using also the SSID). The passphrase may be stored on the user's computer at their discretion under most operating systems to avoid re-entry. The passphrase must remain stored in the Wi-Fi access point.
http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access
 |
|
2008-04-10
, 16:48
|
|
Posts: 4,930 |
Thanked: 2,272 times |
Joined on Oct 2007
|
#15
|
So... the solution is to brute-force reverse it to some <=63 char string which hashes to the hex string they gave you, and enter that... 
It shouldn't be to hard to whip something up with gxmessage and gconftool, but I don't have a WPA net to try it on, so someone else do it.
It shouldn't be to hard to whip something up with gxmessage and gconftool, but I don't have a WPA net to try it on, so someone else do it.
|
|
2008-04-11
, 08:55
|
|
Posts: 3,841 |
Thanked: 1,079 times |
Joined on Nov 2006
|
#16
|
I vaguely remember an earlier thread about hex vs. ascii. In one of the final postings there was a link to a website (possibly made by one of the posters) which would convert from ascii to hex. And possibly more. sorry I don't have a link to the thread, but searching should do it.
__________________
N800/OS2007|N900/Maemo5
-- Metalayer-crawler delenda est.
-- Current state: Fed up with everything MeeGo.
N800/OS2007|N900/Maemo5
-- Metalayer-crawler delenda est.
-- Current state: Fed up with everything MeeGo.
 |
|
2008-04-11
, 12:52
|
|
Posts: 868 |
Thanked: 474 times |
Joined on Oct 2007
@ Capital District, NY, USA
|
#17
|
Originally Posted by TA-t3
Maybe that would work for WEP, but WPA-PSK uses a secure one way hash function. It should be impossible ( for non NSA folks ) to brute force the SHA1 hash used.
I vaguely remember an earlier thread about hex vs. ascii. In one of the final postings there was a link to a website (possibly made by one of the posters) which would convert from ascii to hex. And possibly more. sorry I don't have a link to the thread, but searching should do it.
| The Following User Says Thank You to brontide For This Useful Post: | ||
|
|
2008-04-11
, 13:26
|
|
Posts: 4,930 |
Thanked: 2,272 times |
Joined on Oct 2007
|
#18
|
Hah! people besides the NSA have botnets; it's just not economically sane for them to try cracking a single WAP.
 |
|
2008-04-11
, 16:58
|
|
Posts: 1,137 |
Thanked: 402 times |
Joined on Sep 2007
@ Catalunya
|
#19
|
Originally Posted by brontide
unless you're using a passphrase that can be broken with a dictionary attack, hence the recommendation to use a very long (possibly the maximum allowed, i.e. 63 chars) passphrase made up of random characters.
Maybe that would work for WEP, but WPA-PSK uses a secure one way hash function. It should be impossible ( for non NSA folks ) to brute force the SHA1 hash used.
|
|
2008-04-11
, 17:43
|
|
Posts: 868 |
Thanked: 474 times |
Joined on Oct 2007
@ Capital District, NY, USA
|
#20
|
Originally Posted by luca
http://www.renderlab.net/projects/WPA-tables/
unless you're using a passphrase that can be broken with a dictionary attack
| The Following User Says Thank You to brontide For This Useful Post: | ||
Anyway, thanks to brontide for digging in and providing helpful info.
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net