User talk:Renamed user rn4igoj5itl,j

Compromised account blocked

Sorry to have to do this, but we cannot risk the disruption that happens when accounts are compromised, as you indicated in this edit from your non-public account.

Your account has been blocked indefinitely because it is suspected that it has been compromised. If you are able to confirm that you are the user who created this account, please read the guide to appealing blocks (specifically this section), then add the following text below the block notice on your talk page: {{unblock|reason=Your reason here ~~~~}}.~Anachronist (talk) 07:12, 27 January 2018 (UTC)[reply]

This is a "soft" block, meaning that your IP address is not blocked, and your ability to create a new account is also not blocked. ~Anachronist (talk) 07:12, 27 January 2018 (UTC)[reply]

Unblock Request

This user's unblock request has been reviewed by an administrator, who accepted the request.

Renamed user rn4igoj5itl,j (block log • active blocks • global blocks • contribs • deleted contribs • filter log • creation log • change block settings • unblock • checkuser (log))

Request reason:

I have a committed intentity on the account that you have just mentioned. Decode that (if you can) and you will get my email. If you email me, I'll get back to you as soon as I can.
I have also learned my lesson, and I will logout of any public computer I use this account on, and tell other people to not use my account and instead make their own to prevent a second block from being issued.

CryfryDG Public (talk) 16:46, 30 January 2018 (UTC)[reply]

Accept reason:

I'm satisfied with CryfryDG's confirmation. Committed identity is irrelevant in this case as it was not placed by this account. Vanjagenije (talk) 14:23, 31 January 2018 (UTC)[reply]

CryfryDG, There is no 'decoding' an SHA hash, as it's a 1-way function. If it's OK with Anachronist, I would be OK unblocking you provided that you contact me via Special:EmailUser/SQL from your main account so that I can verify your committed identity. SQL ^{Query me!} 17:27, 30 January 2018 (UTC)[reply]

Retracted - committed identity was only added today SQL ^{Query me!} 20:10, 30 January 2018 (UTC)[reply]

We could unblock this account if CryfryDG confirms (here) that they are in full control of this account. @Anachronist: Do you agree? Vanjagenije (talk) 23:06, 30 January 2018 (UTC)[reply]

@Vanjagenije: I'm fine with that. My block was mostly procedural; if an account is compromised, we block it, understanding that each situation is different. If this isn't a case of someone else stealing the password, and merely a case of a stranger playing with a logged-in account and there is no possibility that anyone else could log in, then yes, we can unblock. ~Anachronist (talk) 01:20, 31 January 2018 (UTC)[reply]

@Vanjagenije: I think that I can fairly well show that I am now in control of my account. Is there any specific way for me to do it? I already sent an email to SQL. Cheers from CryfryDG. (talk) 23:12, 30 January 2018 (UTC)[reply]

For what it's worth - the email you contacted me by does not hash out to match what your committed identity should be. SQL ^{Query me!} 00:24, 31 January 2018 (UTC)[reply]