Skip to main content

CWS转FWS的C代码

原来的代码不能正常编译运行,我做了多处修改
应该是编译和运行环境不同造成的吧。我的环境是VC++2005


/*
* cws2fws by Alex Beregszaszi <alex@fsn.hu>
* Public domain.
*
* This utility converts compressed Macromedia Flash files to uncompressed ones.
*
*/

/*
* Modified by Wang Lu Feb. 6th, 2007
*/

#include <sys/stat.h>
#include <fcntl.h>
//#include <unistd.h> //WL: no this header file in VC++ 2005
#include "zlib.h"

#ifdef DEBUG
#define dbgprintf printf
#else
#define dbgprintf
#endif

#define NULL ((void*)0) //WL: Dummy

main(int argc, char *argv[])
{
int fd_in, fd_out, comp_len, uncomp_len, tag, i, last_out;
char buf_in[1024], buf_out[65536];
z_stream zstream;
struct stat statbuf;

if (argc < 3)
{
printf("Usage: %s <infile.swf> <outfile.swf>\n", argv[0]);
exit(1);
}

fd_in = open(argv[1], O_RDONLY|O_BINARY); //WL: there wasn't O_BINARY originally, and didn't work correctly under VC++
if (fd_in < 0)
{
perror("Error while opening: ");
exit(1);
}

fd_out = open(argv[2], O_WRONLY|O_CREAT|O_BINARY, 00644); //WL: there wasn't O_BINARY originally, and didn't work correctly under VC++
if (fd_out < 0)
{
perror("Error while opening: ");
close(fd_in);
exit(1);
}

if (read(fd_in, buf_in, 8) != 8)
{
printf("Header error\n");
close(fd_in);
close(fd_out);
exit(1);
}

if (buf_in[0] != 'C' || buf_in[1] != 'W' || buf_in[2] != 'S')
{
printf("Not a compressed flash file\n");
exit(1);
}

fstat(fd_in, &statbuf);
comp_len = statbuf.st_size;

//WL: old code is: (which didn't work correctly)
//may because of the convertion from char to unsigned int, VC++ makes 0x83 into 0xffffff83
// uncomp_len = buf_in[4] | (buf_in[5] << 8) | (buf_in[6] << 16) | (buf_in[7] << 24);
uncomp_len = (buf_in[4]&0xff) | ((buf_in[5]&0xff) << 8) | ((buf_in[6]&0xff) << 16) | ((buf_in[7]&0xff) << 24);

printf("Compressed size: %d Uncompressed size: %u\n", comp_len-4, uncomp_len-4);

// write out modified header
buf_in[0] = 'F';
write(fd_out, buf_in, 8);

zstream.zalloc = NULL;
zstream.zfree = NULL;
zstream.opaque = NULL;
inflateInit(&zstream);

for (i = 0; i < comp_len-8;)
{
int ret, len = read(fd_in, buf_in, 1024);

dbgprintf("read %d bytes\n", len);

last_out = zstream.total_out;

zstream.next_in = &buf_in[0];
zstream.avail_in = len;
zstream.next_out = &buf_out[0];
zstream.avail_out = 65536;

ret = inflate(&zstream, Z_SYNC_FLUSH);
if (ret != Z_STREAM_END && ret != Z_OK)
{
printf("Error while decompressing: %d\n", ret);
inflateEnd(&zstream);
exit(1);
}

dbgprintf("a_in: %d t_in: %d a_out: %d t_out: %d -- %d out\n",
zstream.avail_in, zstream.total_in, zstream.avail_out, zstream.total_out,
zstream.total_out-last_out);

write(fd_out, &buf_out, zstream.total_out-last_out);

i += len;

if (ret == Z_STREAM_END || ret == Z_BUF_ERROR)
break;
}

if (zstream.total_out != uncomp_len-8)
{
printf("Size mismatch (%d != %d), updating header...\n",
zstream.total_out, uncomp_len-8);

buf_in[0] = (zstream.total_out+8) & 0xff;
buf_in[1] = (zstream.total_out+8 >> 8) & 0xff;
buf_in[2] = (zstream.total_out+8 >> 16) & 0xff;
buf_in[3] = (zstream.total_out+8 >> 24) & 0xff;

lseek(fd_out, 4, SEEK_SET);
write(fd_out, &buf_in, 4);
}

inflateEnd(&zstream);
close(fd_in);
close(fd_out);
}

Comments

Popular posts from this blog

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...

Hardware Password Manager

[Updates 2025-01-20] The original blog post assumes that all passwords are stored in one password manager, and the password manager either unlocks everything or nothing (e.g. Keepass). After discussing with friends, I realized that if I use something like pass , and I use a hardware GPG token, I can actually store and sync all encrypted passwords to all devices, because I will only decrypt the passwords on demand, and the computer will not see the GPG private key. The compromise is that the computer will see the list of all password entries (e.g. accounts), as well as a few other issues . I've been using Keepass for many years. I don't use online password services because I cannot fully trust them. Besides, I may not always have Internet connection, which is why I also don't use a self-hosted service. Everything has been working fine, until I turn my paranoid knob to the max. Here's the thought experiment . The Imaginary Scenario Let's say I have 100 PCs for differe...

ESP32S3: Flash Encryption and Secure Boot

Flash encryption and secure boot are useful security features for ESP32S3 chip. While not perfect, they definitely make it harder to extract the secrets in the chip. However, it is tricky to enable both features at the same time. The topic is actually discussed in the official documentation: ESP32S3 Security Features Security Features Enablement Workflows Especially, the second one mentioned it is recommended to enable flash encryption before secure boot. But I still find the documentation confusing. In the end I was able to successfully enable both, here's my findings. My Understanding After my adventure, here's what I think could have worked. WARNING, this is untested. Follow  Security Features Enablement Workflows : Burn all the keys, as long as their purpose eFuses and read/write protections Burn other security eFuses, but DO NOT burn ENABLE_SECURITY_DOWNLOAD in the middle, which is mentined at the end of the instruction for both flash encryption and secure boot. Burn...