... continuing the previous post.
Quote:
Originally Posted by refj
* The "Info: Wifi is enabled!" message when returning to KSM is useful, but you still need to go into the wifi settings to switch it off. If it was a dialog with options "Switch it off"/"Leave it on" it would be even more useful.
|
I thought of this, but was too lazy to implement it. I set it on my list for the next update.
Quote:
Originally Posted by refj
* I use usbnet a lot and it would be heavenly if there was another way to change the desired IP address from the default 192.168.2.101 to something else from a configuration file / interactively instead of editing the script itself (I'm already on a 192.168.2.* network). This is probably a little too specific to developers.
|
Would it be sufficient if you could write a list of IP addresses to ksm_ini_options.txt, and select one of them with "configure"?
The other option I can think of now is to introduce a usbnet_toggle_2.sh that reads a list of addresses from a file and offers them for selection each time you try to enable usbnet. I think this might only be useful if you have to change repeatedly in a short time between different addresses.
Quote:
Originally Posted by refj
* When the bouncer is vertical the keyboard is huge on my Kobo Glo HD.
|
You could reduce the size of the application window and see whether this fits you better (-geometry <width>x<height>+<Xoffset>+<Yoffset>)
Spoiler:
For instance to make the application window cover the upper half of the screen in portrait mode on a Glo HD, you would replace in (the original) kbbouncer90.sh
Code:
echo $($ksmroot/kbbouncer/kbbouncer $* -qws)
by
Code:
echo $($ksmroot/kbbouncer/kbbouncer $* -qws -geometry 1072x724+0+0)
I am not sure whether all elements of the application will scale nicely. Therefore, I would rather run this first in test mode. Be aware that /adds/kbmenu/scripts_intern/tools/activate/bouncer/test_the_bouncer.msh calls kbbouncer.sh rather than kbbouncer90.sh. So you have to do something there. Or you start the script by telnet after killing all KSM processes.
Quote:
Originally Posted by refj
* The bouncer can be vastly improved for security, including file security when the device is stolen. Since there is an `openssl` binary we can use that to decrypt encrypted files on boot, while at the same time verifying the password. This would have to be tweakable by the user somehow but I haven't worked on it at all. (Keep in mind that decrypting large files on these readers is slow, but if you're carrying work with you this can be very useful.)
|
Nice idea. Maybe one could consider decrypting only on demand, in order not to increase boot time. And you will not necessarily need all your encrypted data at each session. Or do think of encrypting the nickel database and configuration file too because of email addresses and so on? In that case, one could still postpone decryption until one is actually going to start nickel the first time in a session. The weak point however is that the bouncer password is not encrypted. It can only protect against harmless, but nosy people.