bitm0de
-
Posts
13 -
Joined
-
Last visited
bitm0de's Achievements
-
Why use webrequests when you can use PostAsJsonAsync() with HttpClient extensions?
-
I know, I didn't need the references, I already wrote code for this kind of project. You could pad it easily and still maintain the original byte sequence and length though. -
My idea was to write the raw file format itself directly instead of using built in functions or libraries. It's quite easy even with standard bitmaps to do this, and I wrote code to do it in C a few years ago but in color.
-
You'd need to know HTML in some cases for certain web attacks. Javascript just doesn't go anywhere and execute on a page within the HTML.
-
Example: 10 = original value 10 ^ 20 = 30 (encrypted) 30 ^ 20 = 10 (decrypted) 20 being the key in this case, but you can cycle through a bunch of values cyclically to have a little more randomization. Probably suitable for what you're trying to do for a beginner project.
-
I thought he was using Base64 as an attempt to hide the initial data as input.
-
If you're a beginner just use xor encryption with some cyclical key. Lots of examples on that. There's attacks that can reverse the data, but unless someone knows how to do this it's still more secure than Base64, and as long as you don't give out the key, it should be a bit more secure.
-
I already gave you a suggestion. Use an encryption algorithm... Base64 is an encoding, which is easily reversable. If they see a bunch of random bytes however in an image file, even if they know it is encrypted data it won't be as easy to reverse is my point. Text to Base64 to Binary btw if you are worried about the size of the output data, is going to be massive compared to what I'm telling you to do if you read what I'm saying.
-
" get some binary code, and turn it in a black and white image " - This doesn't align with what you were previously saying. You never mentioned text, and even if you want the binary value of text, base64 is not the answer. You can look at the individual bytes of each character and use them directly to represent the image if that's what you're looking for. Base64 is still highly unnecessary. Encryption would be a better way to go if that's your goal anyways. It's easy to spot Base64 encoded data.
-
Why do you even need base64? Base64 is so that you can represent binary data as a string (most often), but if you're writing to a bitmap the string representation is an unnecessary step and is rather silly. Look at the 24-bit BMP file format, this is very easy to do as the actual image data is basically just the (A)RGB colors of each pixel. The header specifies things like the size and image dimensions. I did this a long time ago to encode data into images. The only catch here is that if you want pure grayscale, you'll have to encode the data as such and thus you won't be able to have each byte of data in its own color component AFAIK. Can't remember if there's some kind of grayscale option for bitmaps, but I doubt it.
-
If you learn C++ first, you'll not only have to learn the language (which is vast compared to most), but you'll have to learn how the preprocessor, compiler, and linker all work as well. Additionally you're managing memory on your own, you don't have garbage collection or any of that stuff. For that reason I'd choose python, sometimes it is harder to debug javascript as well even though it's just as easy to write and test with. Once you learn control flows and logical statements and code structure you'll be able to easily grasp other concepts and progress from there. And Java, ugh... I'm biased but I'd probably substitute that with C# if you wanted to learn the equivalent.
-
bitm0de changed their profile photo
-
It works fine with ANSI C (C89), and most C99 features. The Visual C++ team doesn't plan on supporting modern C standards to the fullest though is the thing since C++ is their main focus. There definitely is a reason to make a distinction between C/C++ with Visual Studio because it has options to compile C or C++ code or determine how to compile the files based on the file extension (cpp vs c). Also, if you're compiling some C code, C isn't as strict with the requirement to case void pointers and in C this is actually discouraged for several reasons, sizeof char literals is 1 in C++ and 4 in C, among many other things. There's also other differences at the heart of both languages so you'd best know what you're actually trying to write - C or C++, there is no in between.
