Michał Skalski

Changed `charon.plugins.vici.socket = tcp://0.0.0.0:4502` in `/usr/local/etc/strongswan.d/charon/vici.conf` and `swanctl.socket = tcp://127.0.0.1:4502` in `/usr/local/etc/strongswan.d/swanctl.conf`, attaching [charon_mem-tcp.log](https://github.com/strongswan/strongswan/files/8324167/charon_mem-tcp.log) and RSS memory is still increasing. In fact I think this behaviour is because frequent memory...

Yes, It's possible, that problem is due to wrong tuning of FreeBSD memory allocator. But on the other hand - there is no special malloc configuration for `charon` daemon AFAIK...

Thank you very much for your help. Yes, I've read these pages, unfortunately heap profiling and leak checking require profiling support which is not compiled into FreeBSD's `libc` by default....

Thank you again for all the help. > No change in this beaviour is observed when using different configure's --with-printf-hooks= -- according to issue in pfsense: https://redmine.pfsense.org/issues/5149 this could be...

> @mskalski Could you split the two changes into two separate commits, then I am happy to merge that one. Sure, done (rebased on current master). Could you also look...

I have the same behaviour If I call `gitstatus.sh` directly from inside git repository, it displays correct data When I modify `gitstatus.sh` to display (or write to some file) contents...

Found it - on Android there is no `/tmp` directory, so private git index was not created, but still variable GIT_INDEX_FILE was set pointing to non-existent file. This way `git...

I'm not sure if it is quite correct. According to *PKCS#1*1 standard , when buffer for signature is not large enough, *PKCS#11* library implementation **MUST** return `CKR_BUFFER_TOO_SMALL` **and update parameter...

Created PR #40.

I cannot see any references to fix this bug in `master`. Is #40 (or some other workaround) already incorporated in `master` branch?