summaryrefslogtreecommitdiffstats
path: root/tools
Commit message (Collapse)AuthorAgeFilesLines
* rsgtutil: refactor 'verify' mode to use new tlv file read functionsRainer Gerhards2013-03-231-1/+3
|
* logsig: refactor 'dump' mode in rsgtutilRainer Gerhards2013-03-231-3/+4
| | | | | The way tlvrecords are processed is changed in order to provide better extensibility for further work.
* doc: add doc for rsgtutilRainer Gerhards2013-03-222-17/+54
|
* rsgtutil: add new file type to file type detectionRainer Gerhards2013-03-222-0/+121
|
* Merge branch 'master' into master-gtRainer Gerhards2013-03-223-26/+32
|\ | | | | | | | | | | Conflicts: configure.ac runtime/rsyslog.h
| * Merge branch 'v7-stable'Rainer Gerhards2013-03-201-1/+1
| |\
| | * cleanupRainer Gerhards2013-03-201-1/+1
| | |
| * | bugfix: stdout/stderr were not closed on forkingRainer Gerhards2013-03-201-1/+1
| | | | | | | | | | | | | | | but were closed when running in the forground - this was just reversed of what it should be. This is a regression of a recent change.
| * | fix merge problemv7.3.8Rainer Gerhards2013-03-181-4/+4
| | |
| * | Merge branch 'v7-stable'Rainer Gerhards2013-03-181-15/+22
| |\| | | | | | | | | | | | | | | | Conflicts: runtime/debug.h tools/syslogd.c
| | * debug system improvement & bug fix for init system status (see below)Rainer Gerhards2013-03-151-20/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - rsyslogd startup information is now properly conveyed back to init when privileges are beging dropped Actually, we have moved termination of the parent in front of the priv drop. So it shall work now in all cases. See code comments in commit for more details. - If forking, the parent now waits for a maximum of 60 seconds for termination by the child - improved debugging support in forked (auto-backgrounding) mode The rsyslog debug log file is now continued to be written across the fork.
| * | Merge branch 'v7-stable'Rainer Gerhards2013-03-131-1/+1
| |\| | | | | | | | | | | | | | | | Conflicts: configure.ac doc/manual.html
| | * doc bugfix: rsyslog.conf man page had invalid file format infoRainer Gerhards2013-03-111-1/+1
| | | | | | | | | | | | closes: http://bugzilla.adiscon.com/show_bug.cgi?id=418
| * | imuxsock: add capability to ignore messages from ourselfesRainer Gerhards2013-02-261-6/+5
| | | | | | | | | | | | | | | This helps prevent message routing loops, and is vital to have if omjournal is used together with traditional syslog.
* | | logsig: complete initial version of verifierRainer Gerhards2013-03-191-18/+43
| | |
* | | Merge branch 'master-gt' of git+ssh://git.adiscon.com/git/rsyslog into master-gtRainer Gerhards2013-03-181-0/+4
|\ \ \
| * | | logsig: implement timestamp verificationRainer Gerhards2013-03-181-0/+4
| | | | | | | | | | | | | | | | | | | | We now use a higher-level verification function as suggested by GuardTime.
* | | | logsig: fix abort if no signature provider was configuredRainer Gerhards2013-03-181-1/+3
|/ / /
* | | logsig: milestone/verfier: block timestamp verification almost completeRainer Gerhards2013-03-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | unfortunately, there seems to be a problem with the GuardTime API, so that I need their support before being able to carry on. Once I receive it, it should be fairly quick to complete the function. I am commiting this work as I do not know how long it will take to receive an answer.
* | | logsig: milestone/verfier: tree hashes are verified; ALSO a bugfixRainer Gerhards2013-03-171-1/+5
| | | | | | | | | | | | bugfix: the initial vector was used incorrectly during hash computation.
* | | logsig: milestone/verfier: record hashes are verifiedRainer Gerhards2013-03-171-1/+94
| | |
* | | rsgtutil: add --show-sigblock-params parameterRainer Gerhards2013-03-141-1/+47
| | |
* | | rsgtutil: begin to make rsgttlvdump a generic utilityRainer Gerhards2013-03-132-10/+95
| | | | | | | | | | | | | | | | | | It will support various maintenaince operations, including verification of signatures in the future. To match its new scope, it also has been renamed.
* | | cleanupRainer Gerhards2013-03-111-9/+0
| | |
* | | logsig: support dynafilesRainer Gerhards2013-03-111-23/+33
| | |
* | | logsig: write integers in most compact from to tlv fileRainer Gerhards2013-03-081-3/+4
| | |
* | | logsig: add config parameters (for omfile)Rainer Gerhards2013-03-072-6/+8
| | |
* | | logsig: preserve necessary state during file closed timeRainer Gerhards2013-03-071-3/+9
| | |
* | | logsig: add support to read signature filesRainer Gerhards2013-03-072-1/+80
| | | | | | | | | | | | ... still incomplete ...
* | | logsig: write block-sig recordRainer Gerhards2013-03-061-1/+1
| | | | | | | | | | | | | | | also some general improvements, e.g. random data is now gathered correctly
* | | logsig: first PoC of actually writing to signature fileRainer Gerhards2013-03-051-1/+1
| | |
* | | logsig: more interface plumbingRainer Gerhards2013-03-051-11/+35
| | |
* | | logsig: build base plumbing for signature multi-provider interfaceRainer Gerhards2013-03-052-4/+68
| | |
* | | logsigner: sign via merkle tree approach (still PoC, non production)Rainer Gerhards2013-02-212-34/+26
| | |
* | | add test/PoC logsigner toolRainer Gerhards2013-02-201-0/+173
|/ /
* | minor: set proper permissions for queue recovery helper scriptRainer Gerhards2013-02-181-0/+0
| |
* | optimze: reduce memory operations during dns resolution/hostname settingRainer Gerhards2013-01-221-6/+6
| | | | | | | | | | | | | | | | | | | | previously, hostname and ip strings were shuffled to the msg object, which created a property out of them. Now the cache holds the property, and it is resused (almost) everywhere, what saves a lot of memory operations. The only exception is imtcp session setup, where different handling of the hostname is done, which we need to sort out (but that's another story).
* | optimize: have dns cache pre-create rsyslog prop_t'sRainer Gerhards2013-01-241-4/+3
| |
* | optimize: reduce nbr of strcpy() in FROMHOST processingRainer Gerhards2013-01-181-3/+4
| |
* | fix compile problem with new stats countersRainer Gerhards2013-01-171-10/+10
| | | | | | | | mutexes on systems without atomic instructions were incorrect
* | omfile: finalize dynafile cache statsRainer Gerhards2013-01-171-13/+29
| |
* | omfile: add stats counters to track dynafile performanceRainer Gerhards2013-01-161-0/+38
| |
* | optimize memory layout for much better cache hitsRainer Gerhards2013-01-151-3/+3
| | | | | | | | | | | | | | | | Moave element status out of batch_obj_t because we get a *much* better cache hit ratio this way. Note that this is really a HUGE saving, even if it doesn't look so (both profiler data as well as practical tests indicate that!).
* | omfile: improved async writing, finally enabled full async writeRainer Gerhards2013-01-141-1/+6
| | | | | | | | also fixed a couple of smaller issues along that way
* | Merge branch 'v7-stable-libnet-frag'Rainer Gerhards2013-01-111-0/+1
|\ \ | | | | | | | | | | | | | | | | | | Conflicts: ChangeLog configure.ac tools/omfile.c
| * | add some more debug info to omfileRainer Gerhards2013-01-101-0/+1
| |/
* | minor cleanupRainer Gerhards2012-12-141-1/+0
| |
* | Merge branch 'v7-stable-newmsglock' into master-newmsglockRainer Gerhards2012-12-062-69/+71
|\| | | | | | | | | | | | | Conflicts: runtime/msg.c runtime/queue.c tools/syslogd.c
| * Merge branch 'v6-stable-newmsglock' into v7-stable-newmsglockRainer Gerhards2012-12-061-10/+0
| |\ | | | | | | | | | | | | Conflicts: tools/syslogd.c
| | * bugfix: some message properties could be garbled due to race conditionRainer Gerhards2012-12-061-10/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This happened only on very high volume systems, if the same message was being processed by two different actions. This was a regression caused by the new config processor, which did no longer properly enable msg locking in multithreaded cases. The bugfix is actually a refactoring of the msg locking code - we no longer do unlocked operations, as the use case for it has mostly gone away. It is potentially possible only at very low-end systems, and there the small additional overhead of doing the locking does not really hurt. Instead, the removal of that capability can actually slightly improve performance in common cases, as the code path is smaller and requires slightly less memory writes. That probably outperforms the extra locking overhead (which in the low-end case always happens in user space, without need for kernel support as we can always directly aquire the lock - there is no contention at all).