wxHexEditor | wxHexEditor official GIT repo | Editor library
kandi X-RAY | wxHexEditor Summary
kandi X-RAY | wxHexEditor Summary
wxHexEditor official GIT repo For info :
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of wxHexEditor
wxHexEditor Key Features
wxHexEditor Examples and Code Snippets
Community Discussions
Trending Discussions on wxHexEditor
QUESTION
I am currently coding a simple c socket HTTP server that support gzip and chunked transfer.
The snippet for gzip and chunked write to socket is as follows:
...ANSWER
Answered 2020-Sep-17 at 16:24deflate reads some uncompressed bytes from the in buffer and writes some compressed bytes to the out buffer. Your code is careful to send all the compressed bytes down the socket, even if the socket doesn't send them all at once. But your code is not careful with the uncompressed bytes!
If deflate fills up the output buffer first, then there are still input bytes left over when it returns. Your code ignores those leftover input bytes and instead of trying to compress them again, it overwrites them with the next bytes from the file.
The reason you see this with JPEG files but not with text files is that JPEG files are already compressed, so they can't be compressed any more. That means the gzipped JPEG output is bigger than the original JPEG, so the output buffer fills up before the input buffer is empty. With the text file, it compresses well and there is plenty of room in the output buffer.
QUESTION
xchg [ebp-0xA], esp
mov eax, [0x57C49B84]
mov ch, 0xB9
xchg [eax-0x13], dl
push ebp
jle 0x00000035
mov esp, 0xA6BC800F
pop ebx
inc esi
fcmovb st(0), st(5)
pop
ANSWER
Answered 2018-Sep-06 at 02:09I think the comments above pretty much give the answer, but let's consolidate.
To answer the actual question, it is not normal for a PNG file to contain executable code that someone put there intentionally.
But any sequence of bytes (like a PNG file) could be interpreted or viewed in many different ways: for example as a sound, as an image, as human-readable text, or even as executable code. In just about all cases, it does not make sense to interpret the bytes as something other than what they were created to be. You could play the PNG data as a waveform, but it would sound awful. You can read the PNG data as text (which you're actually doing with your hex editor), but it does not contain any readable words. Similarly you can treat the PNG data as executable code (which your hex editor is also doing in the Disassembleranzeige pane), but again, the code is meaningless and wouldn't do anything useful except crash the program that was trying to execute it.
But when you read the PNG data with a PNG viewer, you see a picture. Because that is how the human or device who created the PNG file intended for it to be used.
As Dan said, there is a very small chance that a PNG file might contain executable code that someone put there intentionally. That someone may have known about a specific PNG viewing program that had a bug, which caused the program to try to execute part of the PNG data. That someone could then create a PNG file which, when opened with that program, would infect someone else's computer with a virus or trojan. But any other correctly-functioning program would not execute the code.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install wxHexEditor
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
