Quote:
Originally Posted by xxweekxx
PS the solutions didnt work..
1. I dont want a base64 encoder/decoder... #2 saving it as png/tiff is not an option, besides i tried just for the heck of it and no good... #3 good luck insert random crap to ur image when you are sending through webmail like gmail, basically impossible....
so you see how NONE of the solutions are viable...
anyway cheers all
|
Are you a fucking nonce or what?
Off the bat, you've dismissed all the options as 'unviable' - because
a) You can't explain yourself properly and
b) You don't have enough intelligence / patience / whatever to understand the solutions presented.
1) 'Inserting random crap' isn't going to be blocked. Listen closely: File formats, like images, movies, etc, have very specific structures, like header, information, data. Outside of these structures, you can place whatever fucking data you want - it won't affect the look of you image, it will change its base64 value, significantly.
There are multiple ways to do this, all of them simple:
1) Inject / change the exif data of the image.
2) Use a steganography program. Go on, google it.
3) Place data in the empty structure of the image.
None of these happen server side.
I don't even know why I'm wasting my time on this. It seems that if you've tried different formats and the same thing is happening, you're probably getting filtered by what's in your image optically. Stop spamming viagra.