[00:06:01] Actually that makes it use sqlite [00:06:04] So that doesn't work [00:17:35] you should be able to pass --dbtype=postgres or something should work for install.php [00:19:11] but if the installer is broken, best file a bug in phab [10:58:08] hello all [10:58:55] I do have perhaps a very stupid question: I code a bor, and at some time the bot needs to login to do something. For that it reads username/password from a file. [10:59:41] If the thing runs on toolserver, it will have a file like: username=mycoolbot and passwords=mysecretpassword. [11:00:12] Ideally thething isn't stored in clear text, so what do you suggest I use for enncryption of the password? [11:00:55] note that sha1/md5/sha256... are hashing (one-way functions), not encrption? [11:06:07] eptalon: I don't think encrypting the password in this case would help, since it'd just move the same problem to the encryption keys. just make sure to set the file permissions properly so that others can't read the file and ideally use a bot password or an owner-only oauth consumer that only has access to the needed rights, and you should be good [11:06:18] sigh [11:56:16] How do I edit someone else's patch ? (I don't seem to be able to do it :( ) [11:59:48] you need to be in the trusted-contributors gerrit group [11:59:50] added you [12:00:12] so you should now be capable of amending other's patches like your own ones [12:03:07] Ah okay thanks :) [13:53:45] I've found the reason why I can't install postgres. It's T167924. No idea how to fix it though. Removing the key from the updatelog table manually and re-running install.php does not fix anything [13:53:45] T167924: WebInstaller and DatabasePostgres throws Error: 23505 ERROR: duplicate key value violates unique constraint "updatelog_pkey" - https://phabricator.wikimedia.org/T167924 [17:43:40] hello all. If I run a bot, I need to store its credentials in some way, lukely a file. Problem there, I need to encrypt the password of the user. [17:43:54] What is the suggested algorithm for it? [17:44:02] eptalon: I don't think encrypting the password in this case would help, since it'd just move the same problem to the encryption keys. just make sure to set the file permissions properly so that others can't read the file and ideally use a bot password or an owner-only oauth consumer that only has access to the needed rights, and you should be good [17:45:07] so even if the file reads user=mycoolusername, and password=mxysecretPassword? [17:45:49] I thought about RSA, but this means you'll have two keys, in files. [17:46:05] before you even start encrypting [17:48:28] oversimplifying things, there isn't a major difference between 'my password is "123456"' and 'my password is "654321" backwards' [17:50:07] taavi: but if I encrypt that and end up with  AB CD EF 12 34 56.... thats at lrast no longer human-readable. [17:50:14] you need to store the encryption keys somewhere, and if those aren't stored securely they don't add any extra security to the password. and if they can be stored securely you can just store the password securely and avoid the hassle of encrypting in the first place [17:50:34] what is your risk model here? [17:50:50] i.e. what kind of attack are you trying to protect the password from? [17:51:13] taavi: tthat abot account gets compromised. [17:51:49] taavi: cat bot.proterties -> human readable password. [17:52:18] I would have used hashing, but as you know hash functions are one way. [17:53:01] assuming this is on toolforge since that's what you talked about earlier, modify the file permissions so that only the tool account can read the password file [17:54:11] taavi: it would be. [17:54:23] does the toolforge server support a java bot? [17:54:51] yes [17:55:24] jwiki, plus -12 other libs, maven build. [18:12:08] As a rule of thumb, cryptography is never the answer :) [21:21:23] hi [21:21:33] I once sent out an email confirmation for phabricator [21:21:59] but the email never arrives even when I click send again. I checked all folders so I decided to switch to another email. [21:22:19] But the phabricator verification still tries to send to the old email address [21:22:26] and when I click send another email [21:22:38] the "Error Our servers are currently under maintenance or experiencing a technical problem. Please try again in a few minutes." happens [21:22:46] I tried yesterday and today [21:22:56] via cp1081 cp1081, Varnish XID 53824880 Upstream caches: cp1081 int Error: 405, method not allowed at Sun, 29 Jan 2023 21:22:28 GMT [21:23:51] the wikimedia sysadmin page says to try help via phab (non-accessible to me) or irc [21:23:58] people can hear me right? [21:24:12] yes [21:24:22] phew