2017-04-01 at 2:35 PM UTC
xwEFNFAeTJMGRLw2ozlKnQ/gLIjerAJ+PPBgcws/Kg/6G7ipG66oi8cBBTRQHkyTBkS8NqM5Sp0P4CyI3qwCfjzwYHMLPyoPewnH0sijUg0=
Last part looks like base64, but it decodes into nothing intelligible, hash identifier can't tell either nor can any online solution. Looks like some type of user/salt/pass/whatever scheme. It originates from an MSSQL DB.
2017-04-01 at 3:37 PM UTC
What are you asking me for, you know I didn't take computer science III
2017-04-01 at 5:29 PM UTC
aldra
JIDF Controlled Opposition
probably base64, you can tell because base64 uses = for padding and it's padded to a multiple of 3.
base64 is used to be able to store and transfer non-printable symbols to save them being lost or having to be escaped in transmission, the implication being that the original text contains nonstandard characters - it's likely a hash or encoded data that's been converted to base64 for ease of transmission
2017-04-01 at 5:30 PM UTC
aldra
JIDF Controlled Opposition
any more detail on what it is? field header, code that uses it etc.
2017-04-01 at 5:50 PM UTC
MY FRIEN GIVE ME HASH I SMOKED ALL LOL
The following users say it would be alright if the author of this
post didn't die in a fire!
2017-04-01 at 5:52 PM UTC
Please keep off topic posts to the general forums. Next nigger to make a hash joke or otherwise bring nothing to the thread gets a ban.
Originally posted by aldra
probably base64, you can tell because base64 uses = for padding and it's padded to a multiple of 3.
base64 is used to be able to store and transfer non-printable symbols to save them being lost or having to be escaped in transmission, the implication being that the original text contains nonstandard characters - it's likely a hash or encoded data that's been converted to base64 for ease of transmission
This seems reasonable, it doesn't decode to anything obvious. If it's salted then the salt needs to be stored separately, either concatenated with the hash with some delimiter between or in a different field.
Also the use of + and / give you a little information, since the output character set of B64 encoding is not fixed not all encoders will produce output with those characters in it. See here:
https://en.wikipedia.org/wiki/Base64#Variants_summary_table
The following users say it would be alright if the author of this
post didn't die in a fire!
2017-04-01 at 6:03 PM UTC
y do u keep makeing many threads wot is this shsh wot is this hshs but u never even put a pic i fink u are agent
2017-04-01 at 6:10 PM UTC
Apparently if you Convert.ToBase64String(Byte[]) you get back a plain string. If you want to convert that to a Byte array you can via a number of strategies using the System.Text.Encoding class.
Someone do this, IDK how. ASP.NET functions, i don't have that shit installed.
Post last edited by Sophie at 2017-04-01T18:12:56.683223+00:00
2017-04-01 at 7:06 PM UTC
Make it permanent. Like your father's death.
LOL.
Wasn't hash related but I think it was a zinger.
2017-04-01 at 7:33 PM UTC
The Lan Man does not make idle threats.
2017-04-01 at 9:13 PM UTC
Posts deleted. Next off topic is a 24h ban. Make a thread in PEEO or something if you want to be publicly butthurt.
The following users say it would be alright if the author of this
post didn't die in a fire!
2017-04-04 at 6:44 AM UTC
The following users say it would be alright if the author of this
post didn't die in a fire!
2017-04-05 at 12:55 AM UTC
If MSSQL database was hosting ASP.NET website, it is possibly SHA-1 salted with Base64.
2017-06-09 at 7:49 PM UTC
whats it smell liek dus it smell tuff g
The following users say it would be alright if the author of this
post didn't die in a fire!
