I just saw frech-keyboard github branch, congratulations :D. Now, I've finished the spanish-keyboard keyseed.py file. Here is Attachment 404, @binkybear.Thanks @aemaeth2501.
Printable View
I just saw frech-keyboard github branch, congratulations :D. Now, I've finished the spanish-keyboard keyseed.py file. Here is Attachment 404, @binkybear.Thanks @aemaeth2501.
Hi @binkybear,
Here is a quick example on how I was thinking about implementing new locales in the menu (Attachment 405) with the new keyseed.py (the one provided by @discipuloosho with french and spanish layout) . I saw a lead on the github dedicated branch that based the target locale on the default browser one, but I though providing directly a choice via a dropdown menu would make a more volatile solution.
I will look closer a it this weekend (****, got a job :/) since I need to setup an environment to build and test more easily. And to learn the basics of git...
Have a nice day.
@discipuloosho & @aemaeth2501 - Thank you for all the hard work. I will talk to muts about implementing this into the upcoming app.
Thank for you @binkybear :)
Hi !
Despite my absolute lack of knowledge on this subject (and on github usage), I worked on french keyboard for HIB on github and proposed the initial version of the "french keyboard branch".
Good to see more people involved with a more generic approach that helps to develop other languages "keyseeds" :)
aemaeth2501, would you please check my keyseed version and see how you think some of the french characters missing in your version could be integrated ? (e.g. 'é' aka latin small letter e with acute)
https://github.com/uzyfr/kali-nethun...les/keyseed.py
For some "special characters", I had to manage a two steps approach using a "global_last_char" variable.
(Just for the record, my approach was only to specify in the "french" dictionnary only the characters that differs from the english one (lots of characters are similar).)
Last point concerning the locale : I proposed to use the default browser locale because I guess french people would mostly use this attack on computers using french layout.
However, to extend aemaeth2501's proposal, a dropdown menu that select by default the browser locale and allows user to specify the one he wants to use may be a good solution ?
See you soon !
Hi !
I asked myself the 'é', 'è' and other french specificities questions. My conclusion was based on the fact that those characters would not be intergrated in any payload (powershell or raw Base64 encoded). But it is possible to integrate them in the dictionnary for completeness purposes.
I tried this approach with the use of python dictionnaries, and finally I prefered working fully on the charset than 'by delta' vs. US layout. This clarifies (imo) the new locale dictionnary creation.
That is a good idea at first, since indeed frenchs pops frenchs boxes ;) But for example, in my personnal case, I work for a company having multiple nationalities, hence layouts.
For now, I will wait for the android app. At least, the tedious scancode identification job is now done.
Hi, here is a Attachment 418 with a german layout. Umlauts won't work but are probably not needed. the rest should be fine, but isn't thoroughly tested. :o
Feel free to use and/or edit it.
Hi stinkybit,
I added the scancodes provided in the attached file as a new dictionnary in the actual keyseed file.
Just a question : on a windows machine (german OS), what is the confirmation keystroke you need to perform to confirm the "run as admin" (on english one, it is the alt+y for "yes", on french one it is the alt+o for "oui").
Hi aemaeth2501,
sorry, i didn't consider this part so far. It would be alt+j for "ja".
Thanks, it is integrated on my side.
I am working on the complete integration of the locale through the UI (as a dropdown near the platform one).
For the moment I am testing the overall and will issue a pull request of the entire locale management files (including FR, ES and DE locales).