Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
madscientist e5fc208746 Fixed a bug in scanMessageFile where the XHDRInjectOn flag was being interpreted before it had been set by the configuration This caused large messages to be rewritten shorter than they needed to be when header injection was turned on because the flag would appear to be off and the MessageFileSize would be recalculated downward. Later, after the flag was set, the headers would be injected into the shortened file. vor 12 Jahren
ChangeLog Include Makefile and ChangeLog in the distribution. vor 15 Jahren
FilterChain.cpp Fixed bug in FilterChainBase64 where an extra character would be returned if the module ran out of data in SCANNING mode. Now if this occurs a flag is set and "No More Data" is thrown instead of returning the extra byte. vor 14 Jahren
FilterChain.hpp Fixed bug in FilterChainBase64 where an extra character would be returned if the module ran out of data in SCANNING mode. Now if this occurs a flag is set and "No More Data" is thrown instead of returning the extra byte. vor 14 Jahren
GBUdb.cpp Fixed bug in GBUdbIgnoreList reader to prevent reading outside of the line buffer. vor 14 Jahren
GBUdb.hpp Modified to build with 64-bit MinGW. vor 15 Jahren
GBUdb.inline.hpp setup vor 16 Jahren
Makefile.am Include Makefile and ChangeLog in the distribution. vor 15 Jahren
SNFMulti.cpp Fixed a bug in scanMessageFile where the XHDRInjectOn flag was being interpreted before it had been set by the configuration This caused large messages to be rewritten shorter than they needed to be when header injection was turned on because the flag would appear to be off and the MessageFileSize would be recalculated downward. Later, after the flag was set, the headers would be injected into the shortened file. vor 12 Jahren
SNFMulti.hpp Fixed a bug in scanMessageFile where the XHDRInjectOn flag was being interpreted before it had been set by the configuration This caused large messages to be rewritten shorter than they needed to be when header injection was turned on because the flag would appear to be off and the MessageFileSize would be recalculated downward. Later, after the flag was set, the headers would be injected into the shortened file. vor 12 Jahren
gccVersion.txt setup vor 16 Jahren
scanner.cpp setup vor 16 Jahren
scanner.hpp setup vor 16 Jahren
snfCFGmgr.cpp Fixed bug in snfCFGmgr where OEM provided license ID was not always captured in the configuration data causing SYNC authentication problems. vor 15 Jahren
snfCFGmgr.hpp Minor tweaks to eliminate compiler warnings. vor 15 Jahren
snfCFGmgr.inline.hpp setup vor 16 Jahren
snfGBUdbmgr.cpp Fixed initialization of time trigger (typo) was 846... now 864... Supposed to be "once per day". vor 15 Jahren
snfGBUdbmgr.hpp Re-factored for CodeDweller separation vor 16 Jahren
snfLOGmgr.cpp Moved persistent state aux store() operations to RecordSyncEvent vor 15 Jahren
snfLOGmgr.hpp Minor tweaks to eliminate compiler warnings in SNFMulti.*. vor 15 Jahren
snfLOGmgr.inline.hpp Minor tweaks to snfLOGmgr.* to eliminate compiler warnings. vor 15 Jahren
snfNETmgr.cpp Fixed valgrind complaint about using uninitialized data when generating a OneTimePad. The algorithm uses unsigned char x as a register. Each next random byte in the pad is based on encrypting the last-- so a first byte is needed. Original code used an uninitialized x on purpose in order to get a supposedly unpredictable byte out of RAM. To make valgrind happy (and truly to make the algorithm better) x is now initialized by encrypting a 0 with the pad generator. This value is not directly exposed in the generated pad. The first byte in the one time pad is not the result of encrypting 0 but instead the result of encrypting the result of that operation. So, the first byte is based on the state of the pad generator just prior to making the OneTimePad. This is probably harder to predict than the state of the stack (where x would have come from) anyway. vor 15 Jahren
snfNETmgr.hpp Minor tweaks to eliminate compiler warnings in snfNETmgr.* vor 15 Jahren
snfXCImgr.cpp Fixed subtle bug where normal XCI responses did not end with \n. vor 12 Jahren
snfXCImgr.hpp snf_EngineHandler::scanMessageFile updated to read only up to the scan horizon of large files if possible (when header injection is turned off) vor 12 Jahren
snf_HeaderFinder.cpp Fixed bug where only one of multiple source header directives with the same source header definition would be recognized. The fix was to improve the comparator function for HeaderFinderPattern so that it included context. Prior to that only one source header definition would be recognized because the ordinal is always 0 for source headers. As a result, only the first context could be registered. vor 14 Jahren
snf_HeaderFinder.hpp Minor tweaks to eliminate compiler warnings in snf_HeaderFinder.* vor 15 Jahren
snf_HeaderFinder.inline.hpp Fixed bug where only one of multiple source header directives with the same source header definition would be recognized. The fix was to improve the comparator function for HeaderFinderPattern so that it included context. Prior to that only one source header definition would be recognized because the ordinal is always 0 for source headers. As a result, only the first context could be registered. vor 14 Jahren
snf_engine.cpp Replaced all assert() with appropriate Checks and Faults in SNFMulti and it's components. Also added some minor tweaks to improve code safety and eliminate compiler warnings. vor 15 Jahren
snf_engine.hpp Replaced all assert() with appropriate Checks and Faults in SNFMulti and it's components. Also added some minor tweaks to improve code safety and eliminate compiler warnings. vor 15 Jahren
snf_match.h setup vor 16 Jahren
snf_sync.cpp setup vor 16 Jahren
snf_sync.hpp Re-factored for CodeDweller separation vor 16 Jahren
snf_xci.cpp setup vor 16 Jahren
snf_xci.hpp Re-factored for CodeDweller separation vor 16 Jahren