search for: bytes_s

Hi, i'm using xmms-plugin from flac-0.9, i found following problems. Back-seeking cause, that .flac is not played all. It's caused by StreamDecoderPrivate variable samples_decoded and function stream_decoder_frame_sync_, which compare it against whole length of stream. I don't know what is meaning of this varible (samples decoded from last reset or for whole life of decoder). So i

...<time.h> +#include <util.h> #ifdef WITH_ZLIB #include <zlib.h> @@ -850,6 +851,7 @@ ssh_set_newkeys(struct ssh *ssh, int mode) const char *wmsg; int r, crypt_type; const char *dir = mode == MODE_OUT ? "out" : "in"; + char blocks_s[FMT_SCALED_STRSIZE], bytes_s[FMT_SCALED_STRSIZE]; debug2_f("mode %d", mode); @@ -917,20 +919,18 @@ ssh_set_newkeys(struct ssh *ssh, int mode) } comp->enabled = 1; } - /* - * The 2^(blocksize*2) limit is too expensive for 3DES, - * so enforce a 1GB limit for small blocksizes. - * See RFC4344 sectio...

...#include <time.h> +#include <util.h> #ifdef WITH_ZLIB #include <zlib.h> @@ -850,6 +851,7 @@ ssh_set_newkeys(struct ssh *ssh, int mode) const char *wmsg; int r, crypt_type; const char *dir = mode == MODE_OUT ? "out" : "in"; + char blocks_s[FMT_SCALED_STRSIZE], bytes_s[FMT_SCALED_STRSIZE]; debug2_f("mode %d", mode); @@ -917,20 +919,18 @@ ssh_set_newkeys(struct ssh *ssh, int mode) } comp->enabled = 1; } - /* - * The 2^(blocksize*2) limit is too expensive for 3DES, - * so enforce a 1GB limit for small blocksizes. - * See RFC4344 section 3.2. - */ - i...

...til.h> > > #ifdef WITH_ZLIB > #include <zlib.h> > @@ -850,6 +851,7 @@ ssh_set_newkeys(struct ssh *ssh, int mode) > const char *wmsg; > int r, crypt_type; > const char *dir = mode == MODE_OUT ? "out" : "in"; > + char blocks_s[FMT_SCALED_STRSIZE], bytes_s[FMT_SCALED_STRSIZE]; > > debug2_f("mode %d", mode); > > @@ -917,20 +919,18 @@ ssh_set_newkeys(struct ssh *ssh, int mode) > } > comp->enabled = 1; > } > - /* > - * The 2^(blocksize*2) limit is too expensive for 3DES, > - * so enforce a 1GB limit for small...

I was wondering if there was something specific to the internal chacha20 cipher as opposed to OpenSSL implementation. I can't just change the block size because it breaks compatibility. I can do something like as a hack (though it would probably be better to do it with the compat function): if (strstr(enc->name, "chacha")) *max_blocks = (u_int64_t)1 << (16*2);

...util.h> > > #ifdef WITH_ZLIB > #include <zlib.h> > @@ -850,6 +851,7 @@ ssh_set_newkeys(struct ssh *ssh, int mode) > const char *wmsg; > int r, crypt_type; > const char *dir = mode == MODE_OUT ? "out" : "in"; > + char blocks_s[FMT_SCALED_STRSIZE], bytes_s[FMT_SCALED_STRSIZE]; > > debug2_f("mode %d", mode); > > @@ -917,20 +919,18 @@ ssh_set_newkeys(struct ssh *ssh, int mode) > } > comp->enabled = 1; > } > - /* > - * The 2^(blocksize*2) limit is too expensive for 3DES, > - * so enforce a 1GB limit for small b...

Well, I see that my last email hasn''t generated any reaction from the Rails core team. It looks like all of them are the happy users of "plain text" (which, as we know by now, doesn''t exist, but still). I apologize in advance for the sore bitterness of this message but I see that the Rails-core STILL, despite all of the efforts, sees these issues as something