[trunk] password to news server rewritten to ********* by SAB ...

[sander]

A very strange thing in trunk (downloaded yesterday): the news server password in the ini file is rewritten to ********* (literally!) by SAB itself, by just starting it up. This is not caused by my webbrowser, as it also happens when I don't let SAB startup a webbrowser.

See logging below.

I tried a workaround by making the ini read-only (chmod a-r), but SAB refuses to work with a read-only ini (!)

Code: Select all

sander@flappie:~/svn-sabnzbd/trunk/main$ grep -i pass hier-is-mijn-config.ini
password = ""
password = ""
password = ""
password = ""
password = "hallodaar"
sander@flappie:~/svn-sabnzbd/trunk/main$ 
sander@flappie:~/svn-sabnzbd/trunk/main$ ./SABnzbd.py -f hier-is-mijn-config.ini -b 0  > blablabla.txt

<SNIP>

2009-01-20 21:44:54,285::INFO::[_cplogging:55] [20/Jan/2009:21:44:54] ENGINE Serving on 0.0.0.0:8080
[20/Jan/2009:21:44:54] ENGINE Bus STARTED
2009-01-20 21:44:54,286::INFO::[_cplogging:55] [20/Jan/2009:21:44:54] ENGINE Bus STARTED
2009-01-20 21:44:54,286::DEBUG::[misc:525] Unsupported release number (trunk), will not check
2009-01-20 21:45:02,663::WARNING::[__init__:116] Signal 2 caught, saving and exiting...
2009-01-20 21:45:02,663::INFO::[nzbqueue:93] Saving queue
2009-01-20 21:45:02,664::INFO::[__init__:579] Saving data for queue9.sab in /home/sander/svn-sabnzbd/trunk/main/cache/queue9.sab
2009-01-20 21:45:02,669::INFO::[__init__:579] Saving data for bytes9.sab in /home/sander/svn-sabnzbd/trunk/main/cache/bytes9.sab
2009-01-20 21:45:02,670::INFO::[__init__:579] Saving data for rss_data.sab in /home/sander/svn-sabnzbd/trunk/main/cache/rss_data.sab
2009-01-20 21:45:02,671::INFO::[__init__:579] Saving data for bookmarks.sab in /home/sander/svn-sabnzbd/trunk/main/cache/bookmarks.sab
2009-01-20 21:45:02,673::INFO::[__init__:579] Saving data for watched_data.sab in /home/sander/svn-sabnzbd/trunk/main/cache/watched_data.sab
2009-01-20 21:45:02,677::INFO::[postproc:126] Saving postproc queue
2009-01-20 21:45:02,678::INFO::[__init__:579] Saving data for postproc1.sab in /home/sander/svn-sabnzbd/trunk/main/cache/postproc1.sab
sander@flappie:~/svn-sabnzbd/trunk/main$ 
sander@flappie:~/svn-sabnzbd/trunk/main$ 
sander@flappie:~/svn-sabnzbd/trunk/main$ grep -i pass hier-is-mijn-config.ini
password = ""
password = ""
password = ""
password = ""
password = *********
sander@flappie:~/svn-sabnzbd/trunk/main$

SAB refusing read-only ini:

Code: Select all

sander@flappie:~/svn-sabnzbd/trunk/main$ chmod a-r hier-is-mijn-config.ini
sander@flappie:~/svn-sabnzbd/trunk/main$ 
sander@flappie:~/svn-sabnzbd/trunk/main$ 
sander@flappie:~/svn-sabnzbd/trunk/main$ ./SABnzbd.py -f hier-is-mijn-config.ini -b 0  > blablabla.txt
Traceback (most recent call last):
  File "./SABnzbd.py", line 908, in <module>
    main()
  File "./SABnzbd.py", line 622, in main
    if not config.read_config(inifile):
  File "/home/sander/svn-sabnzbd/trunk/main/sabnzbd/decorators.py", line 31, in newFunction
    return f(*args, **kw)
  File "/home/sander/svn-sabnzbd/trunk/main/sabnzbd/config.py", line 610, in read_config
    CFG = configobj.ConfigObj(path)
  File "/home/sander/svn-sabnzbd/trunk/main/sabnzbd/utils/configobj.py", line 1272, in __init__
    self._load(infile, configspec)
  File "/home/sander/svn-sabnzbd/trunk/main/sabnzbd/utils/configobj.py", line 1279, in _load
    h = open(infile, 'rb')
IOError: [Errno 13] Permission denied: '/home/sander/svn-sabnzbd/trunk/main/hier-is-mijn-config.ini'
sander@flappie:~/svn-sabnzbd/trunk/main$

[shypike]

Yeah, stupid error on my part. Rev 2083 sucks.
I'll fix it tonight.

[sander]

Ok. Thanks.

How can I see the Rev number of the trunk version on my computer?

[shypike]

Ask subversion (or TortoiseSVN).
Tell it to go back to Rev  2082.

[sander]

@myself:

Oops, "chmod a-r ... " does NOT mean read-only. It means "non-readable". :-(

With "a-w" it's non-writable, SABnzbd seems to work.

[sander]

Ask subversion (or TortoiseSVN).
Tell it to go back to Rev  2082.

I use RapidSVN and found it under Query -> Info: "2085"

Now I have to find out how to go back ...

[switch]

Was this fixed yet, it got me too 

Yes, svn update and re-enter your passwords.

[shypike]