View Single Post
  #59  
Old 07.01.2014, 03:58
Sistason
Guest
 
Posts: n/a
Default

Just clicked my.jdownloader to replace JD0.9-Webinterface and plan to use it as platform of access for multiple people to remotely fill my DL-Queue.

Everything works just fine (grats and ty!)

I use the jd2 in a Xvfb virtual screen on my server and therefore edited the configs by hand, when I saw that the settings (org.jdownloader.api.myjdownloader.MyJDownloaderSettings.json) store the password for my.jdownloder in plain text.
That's not very nice and according to sources in the forum, the rest (premium logins, ...) is saved in java internals. Why not here? For still-beta-reasons?
I would like a solution like wpa_supplicant for example uses in the configs:
"password": "String - Clear Text Password" or
"password": 1235123151235123
(somehow-hashed pw, but json cannot differentiate between hex and strings, so differentiation could become a problem... :/)

This is, of course, just obfuscation, but allow to at least view the configfile "in public", so no one gets the passwort only by casually looking

Or could you maybe just md5 the password (even if it's just for the config)?


I haven't checked out every feature yet, but those I did worked flawless, especially captchas via browser. A big Plus!
Finally no more desktop-environment on the server just for JDownloader

Weiter so!
Reply With Quote