Bingo
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 22 2017
Then I'm guessing they are ILB spam events.
Sorry, I've removed the one he did make which isn't necessary to be deleted.
NDKilla made none of them.
adding @NDKilla since he created them (or at least one of them)
Jul 18 2017
Jul 17 2017
ValueError: Wrote file to /var/www/challenges/_pOkqv7REDGM3_BcH66RKtDvGMsbDkzfg96_lbM5w3c, but couldn't download http://phab.miraheze.wiki/.well-known/acme-challenge/_pOkqv7REDGM3_BcH66RKtDvGMsbDkzfg96_lbM5w3c
Weird, I can't renew phab.miraheze.wiki, even though DNS was untouched since last time
In T2007#37440, @Reception123 wrote:Ah, then I guess I'll have to add a reminder for every three months and just do this one separately.
Ah, then I guess I'll have to add a reminder for every three months and just do this one separately.
In T2007#37433, @Reception123 wrote:Will do. There's was reallt no need for a task, as I would've seen the icinga alert anyway. I really wish LE would at least have 6 month certs, though.
Will do. There's was reallt no need for a task, as I would've seen the icinga alert anyway. I really wish LE would at least have 6 month certs, though.
Jul 16 2017
The solution has been decided on, @revi just needs to disable the projects enabled (except maybe Phame, if there's actually a valid reason). I haven't seen any spam per se from ILB, except the survey entry so I think the priority can be switched to "normal".
Jul 14 2017
An account is easy to make. However there's no real long term use in a bot here really as actions are either extremely rare or notification worthy.
Jul 6 2017
Jun 29 2017
I'm not sure why but Phame was originally in the disabled apps, but was re-enabled by John after so I'm guessing there must've been some reason for him to do so.
Jun 21 2017
Can Use Application: Public (No Login Required)
This application is required for Phabricator to operate, so all users must have access to it.
Jun 19 2017
In T1934#35933, @Reception123 wrote:In addition I think we should remove the form that allows users (such as ILB) to remove Security users from view.
I think that we can (for now) disable everything except Passphrase which should be restricted to Security only. If we need the other apps, we can easily re-enable them later, and restrict.
Fixed, nice catch.
Jun 18 2017
Jun 13 2017
Jun 12 2017
and changed in resp. to changes description - we have a security ACL. The WMF phab system is they just put acl* at the front.
The project listed is the ACL. It's tagged as a policy and not a project. Also it isn't vague and making another "security" project won't make it less vague than it already isn't imo.
May 21 2017
Verified not changed.
Desired email has been provided to staff@, reopening so this isn't forgotten
May 19 2017
Reception followed up on wiki
Users can change their email addresses.
May 8 2017
May 7 2017
May 3 2017
-----BEGIN CERTIFICATE-----
MIIFCDCCA/CgAwIBAgISA90R04gOJt/4aCWC4u7iKLiHMA0GCSqGSIb3DQEBCwUA
MEoxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MSMwIQYDVQQD
ExpMZXQncyBFbmNyeXB0IEF1dGhvcml0eSBYMzAeFw0xNzA1MDMxNTUzMDBaFw0x
NzA4MDExNTUzMDBaMB0xGzAZBgNVBAMTEnBoYWIubWlyYWhlemUud2lraTCCASIw
DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANNxHBTUVynAS37K6oywmgEFXeHU
m9gMWQpbC87ruqXJX8Jff0a7b/Cf1MFS1Saj051BkUEpnEXeP8RB4r00HFfxuJsR
N0gSfnk+Sc015jrroVH+8sz1BPjlT7oqU8d4wcibC/02b7zZ5RMDFUuUIbP3lj9x
XTvUTVYIRxIbGc9c/Jyy8WnfBgge6eZ+2aOrhx5iTxU6FQxou3LKrLJrQC32GJVU
pm3yE/0K7gt2LLRfbTYzGb3xZVBUimicNt6zOKRcrJ3+Kdm+9TcFqKIovYICgHN3
cpmBb+fEF0vhzRhowHEYFTmmTrqiTYC/EDMhpK7A7Sj7+LEuxnZtMEYEfEkCAwEA
AaOCAhMwggIPMA4GA1UdDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYI
KwYBBQUHAwIwDAYDVR0TAQH/BAIwADAdBgNVHQ4EFgQUUrcWpBbSnfdZJGprqKOM
hGDBl6QwHwYDVR0jBBgwFoAUqEpqYwR93brm0Tm3pkVl7/Oo7KEwcAYIKwYBBQUH
AQEEZDBiMC8GCCsGAQUFBzABhiNodHRwOi8vb2NzcC5pbnQteDMubGV0c2VuY3J5
cHQub3JnLzAvBggrBgEFBQcwAoYjaHR0cDovL2NlcnQuaW50LXgzLmxldHNlbmNy
eXB0Lm9yZy8wHQYDVR0RBBYwFIIScGhhYi5taXJhaGV6ZS53aWtpMIH+BgNVHSAE
gfYwgfMwCAYGZ4EMAQIBMIHmBgsrBgEEAYLfEwEBATCB1jAmBggrBgEFBQcCARYa
aHR0cDovL2Nwcy5sZXRzZW5jcnlwdC5vcmcwgasGCCsGAQUFBwICMIGeDIGbVGhp
cyBDZXJ0aWZpY2F0ZSBtYXkgb25seSBiZSByZWxpZWQgdXBvbiBieSBSZWx5aW5n
IFBhcnRpZXMgYW5kIG9ubHkgaW4gYWNjb3JkYW5jZSB3aXRoIHRoZSBDZXJ0aWZp
Y2F0ZSBQb2xpY3kgZm91bmQgYXQgaHR0cHM6Ly9sZXRzZW5jcnlwdC5vcmcvcmVw
b3NpdG9yeS8wDQYJKoZIhvcNAQELBQADggEBAIBKz2Va/Zc1a3Al7159QDQ4oF3y
zceHNnGeGOs7v9DF0cwJ9yUzMSkq/2JQhw6Y8qTG1UHZBkjn8GpUdnA6PhKkIg7b
vRfGOiHzpuWiqxvLpHbhoH9J29OKki9BXyPMeq+0yHDFZcE0eg0xE4kiH2Bwishn
gy5UKLJVPLSK0Q9uQ+jmR3iPQ8EtYRbJUKAJwEhbHQucq+LfaTkl+uGuVKRtu0En
do8FU24KbnX75ma9LiI2wIqraK/Y/I2AGel7rXpcyDpnQrSXQCxWwDr+AVAAm6q4
M7RWV1l9u5SL2XvthGXlCG4ooDq8VfeSalYZmbjmTabYuPJs5pzYegELDio=
-----END CERTIFICATE-----
If you need to use Phabricator for personal reasons or any reason unrelated to Miraheze, or something that cannot be shared to Security, use your own instance. We are not hosting Phabricator. If you're looking for one, use Phacility
Why can't project creation be open? What's the point of the restriction?
Blame Upstream. I'm not willing to loose the restriction.
You should not restrict project creation to admins, so that all users can create their personal timelines
Also, you should've file a phabricator task for such thing. We do not know you want it until you say it.
Amanda has been created, but remember you should not touch any ACL value or my last warning still stands.
If you do not want me to have private Maniphest tasks, create a project for me like you and NDK have
This is your final warning if you undo my re-open, I will immediately disable your account for two months. I'm being extra generous here.
Apr 30 2017
Apr 24 2017
Oh, I thought it would need opinions of other sysadmins
Done.
Apr 18 2017
Apr 17 2017
Back to "All Users", but I would like to remind that people should not touch the Visible to Value and Editable by value, unless security bug (in this case we have a task form, too, so you shouldn't be touching it anyway.)
Apr 16 2017
@Amanda You will just have to wait for the restriction to be removed. This restriction was mainly done because of the spam.
The other thing that I have noticed with this policy is that I can't claim or close tasks that I handle.
back to revi, since he made the change originally he can undo it more easily.
No it hasn't.
Changed back by John.
Good point. Though I'm not sure why non administrative users should edit tasks really, if they are not the creators. Generally it is either spam or the wrong option.
I don't think that this is necessary anymore now that the LP spam should've stopped.
Apr 7 2017
Thusly closing as invalid.
Apr 6 2017
Hmm, maybe S1 with custom read/edit policy? (But I'm not sure if this is possible with emails...)
The design of spaces was to be as restrictive as possible which is why you can't "allow per task". Spaces are checked before tasks so it will be impossible to decide who a task author is in a sense.
Just realized there's no 'task author' in space. Maybe something to submit feature request on upstream?
Apr 4 2017
Mar 31 2017
Mar 28 2017
Mar 18 2017
What I meant in
Yes, what I expected.
Feb 25 2017
Not an access request.
The config is auth.require-email-verification.