Commit 4806cc102655f1a829d656f6deb83e5953c5eab2 fixed only part of the problem.
Since it removed the filename either the magic filename has to be resurrected
or all checks against priv_key_file need to take to check for MF_EXTERNAL_KEY
as well. This patch implements the extra checks
Signed-off-
Dear Developers,
I developed a patch for implementing 1:1 NAT (something similar to the iptables
NETMAP target).
This is useful in situations when you have the same (private) network address
behind clients.
For example, consider the following scenario:
-lan1--192.168.0.0/24-- -lan2--192.16
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/09/12 15:38, Andrea Bonomi wrote:
> Dear Developers, I developed a patch for implementing 1:1 NAT
> (something similar to the iptables NETMAP target). This is useful
> in situations when you have the same (private) network address
> behind client
There no difference, it's exactly the same feature.
The next time I promise to check better before implementing something that
already exist.
Sorry,
Andrea Bonomi
:: e n d i a n
:: security with passion
:: andrea bonomi
:: http://www.endian.com :: a.bon...@endian.com
On 10/set/2012, at 16:49, D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/09/12 17:24, Andrea Bonomi wrote:
> There no difference, it's exactly the same feature. The next time I
> promise to check better before implementing something that already
> exist. Sorry,
No worries, I'm just sorry for you spending time on impl
From: Heiko Hund
With this option, users can basically undo the changes of the UTF-8
support commit 5e86fd93779482b90a191f929edebe414cd78a4f. It's here for
short term compatibility and should be removed again as soon as possible.
When OpenSSL is used, the subject strings will be in the proprieta
