forked from mestery/strongswan
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathNEWS
3461 lines (2506 loc) · 147 KB
/
NEWS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
strongswan-5.7.2
----------------
- Private key implementations may optionally provide a list of supported
signature schemes, which is used by the tpm plugin because for each key on a
TPM 2.0 the hash algorithm and for RSA also the padding scheme is predefined.
- For RSA with PSS padding, the TPM 2.0 specification mandates the maximum salt
length (as defined by the length of the key and hash). However, if the TPM is
FIPS-168-4 compliant, the salt length equals the hash length. This is assumed
for FIPS-140-2 compliant TPMs, but if that's not the case, it might be
necessary to manually enable charon.plugins.tpm.fips_186_4 if the TPM doesn't
use the maximum salt length.
- Added support for RSA signatures with SHA-256 and SHA-512 to the agent plugin.
For older versions of ssh/gpg-agent that only support SHA-1, IKEv2 signature
authentication has to be disabled via charon.signature_authentication.
- The sshkey and agent plugins support Ed25519/Ed448 SSH keys and signatures.
- Ed25519, ChaCha20/Poly1305, SHA-3 and AES-CCM were added to the botan plugin.
- The mysql plugin now properly handles database connections with transactions
under heavy load.
strongswan-5.7.1
----------------
- Fixes a vulnerability in the gmp plugin triggered by crafted certificates with
RSA keys with very small moduli. When verifying signatures with such keys,
the code patched with the fix for CVE-2018-16151/2 caused an integer underflow
and subsequent heap buffer overflow that results in a crash of the daemon.
The vulnerability has been registered as CVE-2018-17540.
strongswan-5.7.0
----------------
- Fixes a potential authorization bypass vulnerability in the gmp plugin that
was caused by a too lenient verification of PKCS#1 v1.5 signatures. Several
flaws could be exploited by a Bleichenbacher-style attack to forge signatures
for low-exponent keys (i.e. with e=3). CVE-2018-16151 has been assigned to
the problem of accepting random bytes after the OID of the hash function in
such signatures, and CVE-2018-16152 has been assigned to the issue of not
verifying that the parameters in the ASN.1 algorithmIdentitifer structure is
empty. Other flaws that don't lead to a vulnerability directly (e.g. not
checking for at least 8 bytes of padding) have no separate CVE assigned.
- Dots are not allowed anymore in section names in swanctl.conf and
strongswan.conf. This mainly affects the configuration of file loggers. If the
path for such a log file contains dots it now has to be configured in the new
`path` setting within the arbitrarily renamed subsection in the `filelog`
section.
- Sections in swanctl.conf and strongswan.conf may now reference other sections.
All settings and subsections from such a section are inherited. This allows
to simplify configs as redundant information has only to be specified once
and may then be included in other sections (refer to the example in the man
page for strongswan.conf).
- The originally selected IKE config (based on the IPs and IKE version) can now
change if no matching algorithm proposal is found. This way the order
of the configs doesn't matter that much anymore and it's easily possible to
specify separate configs for clients that require weak algorithms (instead
of having to also add them in other configs that might be selected).
- Support for Postquantum Preshared Keys for IKEv2 (draft-ietf-ipsecme-qr-ikev2)
has been added.
- The new botan plugin is a wrapper around the Botan C++ crypto library. It
requires a fairly recent build from Botan's master branch (or the upcoming
2.8.0 release). Thanks to René Korthaus and his team from Rohde & Schwarz
Cybersecurity for the initial patch.
- The pki tool accepts a xmppAddr otherName as a subjectAlternativeName using
the syntax --san xmppaddr:<jid>.
- Implementation of RFC 8412 "Software Inventory Message and Attributes (SWIMA)
for PA-TNC". SWIMA subscription option sets CLOSE_WRITE trigger on apt
history.log file resulting in a ClientRetry PB-TNC batch to initialize
a new measurement cycle.
- Added support for fuzzing the PA-TNC (RFC 5792) and PB-TNC (RFC 5793) NEA
protocols on Google's OSS-Fuzz infrastructure.
- Support for version 2 of Intel's TPM2-TSS TGC Software Stack. The presence of
the in-kernel /dev/tpmrm0 resource manager is automatically detected.
- Marks the in- and/or outbound SA should apply to packets after processing may
be configured in swanctl.conf on Linux. For outbound SAs this requires at
least a 4.14 kernel. Setting a mask and configuring a mark/mask for inbound
SAs will be added with the upcoming 4.19 kernel.
- New options in swanctl.conf allow configuring how/whether DF, ECN and DS
fields in the IP headers are copied during IPsec processing. Controlling this
is currently only possible on Linux.
- To avoid conflicts, the dhcp plugin now only uses the DHCP server port if
explicitly configured.
strongswan-5.6.3
----------------
- Fixed a DoS vulnerability in the IKEv2 key derivation if the openssl plugin is
used in FIPS mode and HMAC-MD5 is negotiated as PRF.
This vulnerability has been registered as CVE-2018-10811.
- Fixed a vulnerability in the stroke plugin, which did not check the received
length before reading a message from the socket. Unless a group is configured,
root privileges are required to access that socket, so in the default
configuration this shouldn't be an issue.
This vulnerability has been registered as CVE-2018-5388.
⁻ CRLs that are not yet valid are now ignored to avoid problems in scenarios
where expired certificates are removed from CRLs and the clock on the host
doing the revocation check is trailing behind that of the host issuing CRLs.
- The issuer of fetched CRLs is now compared to the issuer of the checked
certificate.
- CRL validation results other than revocation (e.g. a skipped check because
the CRL couldn't be fetched) are now stored also for intermediate CA
certificates and not only for end-entity certificates, so a strict CRL policy
can be enforced in such cases.
- In compliance with RFC 4945, section 5.1.3.2, certificates used for IKE must
now either not contain a keyUsage extension (like the ones generated by pki)
or have at least one of the digitalSignature or nonRepudiation bits set.
- New options for vici/swanctl allow forcing the local termination of an IKE_SA.
This might be useful in situations where it's known the other end is not
reachable anymore, or that it already removed the IKE_SA, so retransmitting a
DELETE and waiting for a response would be pointless. Waiting only a certain
amount of time for a response before destroying the IKE_SA is also possible
by additionally specifying a timeout.
- When removing routes, the kernel-netlink plugin now checks if it tracks other
routes for the same destination and replaces the installed route instead of
just removing it. Same during installation, where existing routes previously
weren't replaced. This should allow using traps with virtual IPs on Linux.
- The dhcp plugin only sends the client identifier option if identity_lease is
enabled. It can also send identities of up to 255 bytes length, instead of
the previous 64 bytes. If a server address is configured, DHCP requests are
now sent from port 67 instead of 68 to avoid ICMP port unreachables.
- Roam events are now completely ignored for IKEv1 SAs.
- ChaCha20/Poly1305 is now correctly proposed without key length. For
compatibility with older releases the chacha20poly1305compat keyword may be
included in proposals to also propose the algorithm with a key length.
- Configuration of hardware offload of IPsec SAs is now more flexible and allows
a new mode, which automatically uses it if the kernel and device support it.
- SHA-2 based PRFs are supported in PKCS#8 files as generated by OpenSSL 1.1.
- The pki --verify tool may load CA certificates and CRLs from directories.
- Fixed an issue with DNS servers passed to NetworkManager in charon-nm.
strongswan-5.6.2
----------------
- Fixed a DoS vulnerability in the parser for PKCS#1 RSASSA-PSS signatures that
was caused by insufficient input validation. One of the configurable
parameters in algorithm identifier structures for RSASSA-PSS signatures is the
mask generation function (MGF). Only MGF1 is currently specified for this
purpose. However, this in turn takes itself a parameter that specifies the
underlying hash function. strongSwan's parser did not correctly handle the
case of this parameter being absent, causing an undefined data read.
This vulnerability has been registered as CVE-2018-6459.
- The previously negotiated DH group is reused when rekeying an SA, instead of
using the first group in the configured proposals, which avoids an additional
exchange if the peer selected a different group via INVALID_KE_PAYLOAD when
the SA was created initially.
The selected DH group is also moved to the front of all sent proposals that
contain it and all proposals that don't are moved to the back in order to
convey the preference for this group to the peer.
- Handling of MOBIKE task queuing has been improved. In particular, the response
to an address update is not ignored anymore if only an address list update or
DPD is queued.
- The fallback drop policies installed to avoid traffic leaks when replacing
addresses in installed policies are now replaced by temporary drop policies,
which also prevent acquires because we currently delete and reinstall IPsec
SAs to update their addresses.
- Access X.509 certificates held in non-volatile storage of a TPM 2.0
referenced via the NV index.
- Adding the --keyid parameter to pki --print allows to print private keys
or certificates stored in a smartcard or a TPM 2.0.
- Fixed proposal selection if a peer incorrectly sends DH groups in the ESP
proposals during IKE_AUTH and also if a DH group is configured in the local
ESP proposal and charon.prefer_configured_proposals is disabled.
- MSKs received via RADIUS are now padded to 64 bytes to avoid compatibility
issues with EAP-MSCHAPv2 and PRFs that have a block size < 64 bytes (e.g.
AES-XCBC-PRF-128).
- The tpm_extendpcr command line tool extends a digest into a TPM PCR.
- Ported the NetworkManager backend from the deprecated libnm-glib to libnm.
- The save-keys debugging/development plugin saves IKE and/or ESP keys to files
compatible with Wireshark.
strongswan-5.6.1
----------------
- In compliance with RFCs 8221 and 8247 several algorithms were removed from the
default ESP/AH and IKEv2 proposals, respectively (3DES, Blowfish and MD5 from
ESP/AH, MD5 and MODP-1024 from IKEv2). These algorithms may still be used in
custom proposals.
- Added support for RSASSA-PSS signatures. For backwards compatibility they are
not used automatically by default, enable charon.rsa_pss to change that. To
explicitly use or require such signatures with IKEv2 signature authentication
(RFC 7427), regardless of whether that option is enabled, use ike:rsa/pss...
authentication constraints.
- The pki tool can optionally sign certificates/CRLs with RSASSA-PSS via the
`--rsa-padding pss` option.
- The sec-updater tool checks for security updates in dpkg-based repositories
(e.g. Debian/Ubuntu) and sets the security flags in the IMV policy database
accordingly. Additionally for each new package version a SWID tag for the
given OS and HW architecture is created and stored in the database.
Using the sec-updater.sh script template the lookup can be automated
(e.g. via an hourly cron job).
- The introduction of file versions in the IMV database scheme broke file
reference hash measurements. This has been fixed by creating generic product
versions having an empty package name.
- A new timeout option for the systime-fix plugin stops periodic system time
checks after a while and enforces a certificate verification, closing or
reauthenticating all SAs with invalid certificates.
- The IKE event counters, previously only available via ipsec listcounters, may
now be queried/reset via vici and the new swanctl --counters command. They are
provided by the new optional counters plugin.
- Class attributes received in RADIUS Access-Accept messages may optionally be
added to RADIUS accounting messages.
- Inbound marks may optionally be installed on the SA again (was removed with
5.5.2) by enabling the mark_in_sa option in swanctl.conf.
strongswan-5.6.0
----------------
- Fixed a DoS vulnerability in the gmp plugin that was caused by insufficient
input validation when verifying RSA signatures, which requires decryption
with the operation m^e mod n, where m is the signature, and e and n are the
exponent and modulus of the public key. The value m is an integer between
0 and n-1, however, the gmp plugin did not verify this. So if m equals n the
calculation results in 0, in which case mpz_export() returns NULL. This
result wasn't handled properly causing a null-pointer dereference.
This vulnerability has been registered as CVE-2017-11185.
- New SWIMA IMC/IMV pair implements the "draft-ietf-sacm-nea-swima-patnc"
Internet Draft and has been demonstrated at the IETF 99 Prague Hackathon.
- The IMV database template has been adapted to achieve full compliance
with the ISO 19770-2:2015 SWID tag standard.
- The sw-collector tool extracts software events from apt history logs
and stores them in an SQLite database to be used by the SWIMA IMC.
The tool can also generate SWID tags both for installed and removed
package versions.
- The pt-tls-client can attach and use TPM 2.0 protected private keys
via the --keyid parameter.
- libtpmtss supports Intel's TSS2 Architecture Broker and Resource
Manager interface (tcti-tabrmd).
- The new eap-aka-3gpp plugin implements the 3GPP MILENAGE algorithms
in software. K (optionally concatenated with OPc) may be configured as
binary EAP secret.
- CHILD_SA rekeying was fixed in charon-tkm and was slightly changed: The
switch to the new outbound IPsec SA now happens via SPI on the outbound
policy on Linux, and in case of lost rekey collisions no outbound SA/policy
is temporarily installed for the redundant CHILD_SA.
- The new %unique-dir value for mark* settings allocates separate unique marks
for each CHILD_SA direction (in/out).
strongswan-5.5.3
----------------
- Fixed a DoS vulnerability in the gmp plugin that was caused by insufficient
input validation when verifying RSA signatures. More specifically,
mpz_powm_sec() has two requirements regarding the passed exponent and modulus
that the plugin did not enforce, if these are not met the calculation will
result in a floating point exception that crashes the whole process.
This vulnerability has been registered as CVE-2017-9022.
- Fixed a DoS vulnerability in the x509 plugin that was caused because the ASN.1
parser didn't handle ASN.1 CHOICE types properly, which could result in an
infinite loop when parsing X.509 extensions that use such types.
This vulnerability has been registered as CVE-2017-9023.
- The behavior during IKEv2 CHILD_SA rekeying has been changed in order to avoid
traffic loss. The responder now only installs the new inbound SA and delays
installing the outbound SA until it receives the DELETE for the replaced
CHILD_SA. Similarly, the inbound SA of the replaced CHILD_SA is not removed
for a configurable amount of seconds (charon.delete_rekeyed_delay) after the
DELETE has been processed to reduce the chance of dropping delayed packets.
- The code base has been ported to Apple's ARM64 iOS platform, whose calling
conventions for variadic and regular functions are different. This means
assigning non-variadic functions to variadic function pointers does not work.
To avoid this issue the enumerator_t interface has been changed and the
signatures of the callback functions for enumerator_create_filter(), and the
invoke_function() and find_first() methods on linked_list_t have been changed.
The return type of find_first() also changed from status_t to bool.
- Added support for fuzzing the certificate parser provided by the default
plugins (x509, pem, gmp etc.) on Google's OSS-Fuzz infrastructure. Several
issues found while fuzzing these plugins were fixed.
- Two new options have been added to charon's retransmission settings:
retransmit_limit and retransmit_jitter. The former adds an upper limit to the
calculated retransmission timeout, the latter randomly reduces it.
- A bug in swanctl's --load-creds command was fixed that caused unencrypted
private keys to get unloaded if the command was called multiple times. The
load-key VICI command now returns the key ID of the loaded key on success.
- The credential manager now enumerates local credential sets before global
ones. This means certificates supplied by the peer will now be preferred over
certificates with the same identity that may be locally stored (e.g. in the
certificate cache).
- Added support for hardware offload of IPsec SAs as introduced by Linux 4.11
for hardware that supports this.
- When building the libraries monolithically and statically the plugin
constructors are now hard-coded in each library so the plugin code is not
removed by the linker because it thinks none of their symbols are ever
referenced.
- The pki tool loads the curve25519 plugin by default.
strongswan-5.5.2
----------------
- Support of Diffie-Hellman group 31 using Curve25519 for IKE as defined
by RFC 8031.
- Support of Ed25519 digital signature algorithm for IKEv2 as defined by
draft-ietf-ipsecme-eddsa. Ed25519-based public key pairs, X.509 certificates
and CRLs can be generated and printed by the pki tool.
- The new "tpm" libtpmtss plugin allows to use persistent private RSA and ECDSA
keys bound to a TPM 2.0 for both IKE and TLS authentication. Using the
TPM 2.0 object handle as keyid parameter, the pki --pub tool can extract
the public key from the TPM thereby replacing the aikpub2 tool. In a similar
fashion pki --req can generate a PKCS#10 certificate request signed with
the TPM private key.
- The pki tool gained support for generating certificates with the RFC 3779
addrblock extension. The charon addrblock plugin now dynamically narrows
traffic selectors based on the certificate addrblocks instead of rejecting
non-matching selectors completely. This allows generic connections, where
the allowed selectors are defined by the used certificates only.
- In-place update of cached base and delta CRLs does not leave dozens
of stale copies in cache memory.
- Several new features for the VICI interface and the swanctl utility: Querying
specific pools, enumerating and unloading keys and shared secrets, loading
keys and certificates from PKCS#11 tokens, the ability to initiate, install
and uninstall connections and policies by their exact name (if multiple child
sections in different connections share the same name), a command to initiate
the rekeying of IKE and IPsec SAs, support for settings previously only
supported by the old config files (plain pubkeys, dscp, certificate policies,
IPv6 Transport Proxy Mode, NT Hash secrets, mediation extension).
Important: Due to issues with VICI bindings that map sub-sections to
dictionaries the CHILD_SA sections returned via list-sas now have a unique
name, the original name of a CHILD_SA is returned in the "name" key of its
section.
strongswan-5.5.1
----------------
- The newhope plugin implements the post-quantum NewHope key exchange algorithm
proposed in their 2015 paper by Erdem Alkim, Léo Ducas, Thomas Pöppelmann and
Peter Schwabe.
- The libstrongswan crypto factory now offers the registration of Extended
Output Functions (XOFs). Currently supported XOFs are SHAKE128 and SHAKE256
implemented by the sha3 plugin, ChaCHa20 implemented by the chapoly plugin
and the more traditional MGF1 Mask Generation Functions based on the SHA-1,
SHA-256 and SHA-512 hash algorithms implemented by the new mgf1 plugin.
- The pki tool, with help of the pkcs1 or openssl plugins, can parse private
keys in any of the supported formats without having to know the exact type.
So instead of having to specify rsa or ecdsa explicitly the keyword priv may
be used to indicate a private key of any type. Similarly, swanctl can load
any type of private key from the swanctl/private directory.
- The pki tool can handle RSASSA-PKCS1v1.5-with-SHA-3 signatures using the
sha3 and gmp plugins.
- The VICI flush-certs command flushes certificates from the volatile
certificate cache. Optionally the type of the certificates to be
flushed (e.g. type = x509_crl) can be specified.
- Setting cache_crls = yes in strongswan.conf the vici plugin saves regular,
base and delta CRLs to disk.
- IKE fragmentation is now enabled by default with the default fragment size
set to 1280 bytes for both IP address families.
- libtpmtss: In the TSS2 API the function TeardownSocketTcti() was replaced by
tss2_tcti_finalize().
strongswan-5.5.0
----------------
- The new libtpmtss library offers support for both TPM 1.2 and TPM 2.0
Trusted Platform Modules. This allows the Attestation IMC/IMV pair to
do TPM 2.0 based attestation.
- The behavior during IKEv2 exchange collisions has been improved/fixed in
several corner cases and support for TEMPORARY_FAILURE and CHILD_SA_NOT_FOUND
notifies, as defined by RFC 7296, has been added.
- IPsec policy priorities can be set manually (e.g. for high-priority drop
policies) and outbound policies may be restricted to a network interface.
- The scheme for the automatically calculated default priorities has been
changed and now also considers port masks, which were added with 5.4.0.
- FWD policies are now installed in both directions in regards to the traffic
selectors. Because such "outbound" FWD policies could conflict with "inbound"
FWD policies of other SAs they are installed with a lower priority and don't
have a reqid set, which allows kernel plugins to distinguish between the two
and prefer those with a reqid.
- For outbound IPsec SAs no replay window is configured anymore.
- Enhanced the functionality of the swanctl --list-conns command by listing
IKE_SA and CHILD_SA reauthentication and rekeying settings, and EAP/XAuth
identities and EAP types.
- DNS servers installed by the resolve plugin are now refcounted, which should
fix its use with make-before-break reauthentication. Any output written to
stderr/stdout by resolvconf is now logged.
- The methods in the kernel interfaces have been changed to take structs instead
of long lists of arguments. Similarly the constructors for peer_cfg_t and
child_cfg_t now take structs.
strongswan-5.4.0
----------------
- Support for IKEv2 redirection (RFC 5685) has been added. Plugins may
implement the redirect_provider_t interface to decide if and when to redirect
connecting clients. It is also possible to redirect established IKE_SAs based
on different selectors via VICI/swanctl. Unless disabled in strongswan.conf
the charon daemon will follow redirect requests received from servers.
- The ike: prefix enables the explicit configuration of signature scheme
constraints against IKEv2 authentication in rightauth, which allows the use
of different signature schemes for trustchain verification and authentication.
- The initiator of an IKEv2 make-before-break reauthentication now suspends
online certificate revocation checks (OCSP, CRLs) until the new IKE_SA and all
CHILD_SAs are established. This is required if the checks are done over the
CHILD_SA established with the new IKE_SA. This is not possible until the
initiator installs this SA and that only happens after the authentication is
completed successfully. So we suspend the checks during the reauthentication
and do them afterwards, if they fail the IKE_SA is closed. This change has no
effect on the behavior during the authentication of the initial IKE_SA.
- For the vici plugin a Vici:Session Perl CPAN module has been added to allow
Perl applications to control and/or monitor the IKE daemon using the VICI
interface, similar to the existing Python egg or Ruby gem.
- Traffic selectors with port ranges can now be configured in the Linux kernel:
e.g. remote_ts = 10.1.0.0/16[tcp/20-23] local_ts = dynamic[tcp/32768-65535].
The port range must map to a port mask, though since the kernel does not
support arbitrary ranges.
- The vici plugin allows the configuration of IPv4 and IPv6 address ranges
in local and remote traffic selectors. Since both the Linux kernel and
iptables cannot handle arbitrary ranges, address ranges are mapped to the next
larger CIDR subnet by the kernel-netlink and updown plugins, respectively.
- Implemented IKEv1 IPv4/IPv6 address subnet and range identities that can be
used as owners of shared secrets.
strongswan-5.3.5
----------------
- Properly handle potential EINTR errors in sigwaitinfo(2) calls that replaced
sigwait(3) calls with 5.3.4.
- RADIUS retransmission timeouts are now configurable, courtesy of Thom Troy.
strongswan-5.3.4
----------------
- Fixed an authentication bypass vulnerability in the eap-mschapv2 plugin that
was caused by insufficient verification of the internal state when handling
MSCHAPv2 Success messages received by the client.
This vulnerability has been registered as CVE-2015-8023.
- The sha3 plugin implements the SHA3 Keccak-F1600 hash algorithm family.
Within the strongSwan framework SHA3 is currently used for BLISS signatures
only because the OIDs for other signature algorithms haven't been defined
yet. Also the use of SHA3 for IKEv2 has not been standardized yet.
strongswan-5.3.3
----------------
- Added support for the ChaCha20/Poly1305 AEAD cipher specified in RFC 7539 and
RFC 7634 using the chacha20poly1305 ike/esp proposal keyword. The new chapoly
plugin implements the cipher, if possible SSE-accelerated on x86/x64
architectures. It is usable both in IKEv2 and the strongSwan libipsec ESP
backend. On Linux 4.2 or newer the kernel-netlink plugin can configure the
cipher for ESP SAs.
- The vici interface now supports the configuration of auxiliary certification
authority information as CRL and OCSP URIs.
- In the bliss plugin the c_indices derivation using a SHA-512 based random
oracle has been fixed, generalized and standardized by employing the MGF1 mask
generation function with SHA-512. As a consequence BLISS signatures unsing the
improved oracle are not compatible with the earlier implementation.
- Support for auto=route with right=%any for transport mode connections has
been added (the ikev2/trap-any scenario provides examples).
- The starter daemon does not flush IPsec policies and SAs anymore when it is
stopped. Already existing duplicate policies are now overwritten by the IKE
daemon when it installs its policies.
- Init limits (like charon.init_limit_half_open) can now optionally be enforced
when initiating SAs via VICI. For this, IKE_SAs initiated by the daemon are
now also counted as half-open SAs, which, as a side-effect, fixes the status
output while connecting (e.g. in ipsec status).
- Symmetric configuration of EAP methods in left|rightauth is now possible when
mutual EAP-only authentication is used (previously, the client had to
configure rightauth=eap or rightauth=any, which prevented it from using this
same config as responder).
- The initiator flag in the IKEv2 header is compared again (wasn't the case
since 5.0.0) and packets that have the flag set incorrectly are again ignored.
- Implemented a demo Hardcopy Device IMC/IMV pair based on the "Hardcopy
Device Health Assessment Trusted Network Connect Binding" (HCD-TNC)
document drafted by the IEEE Printer Working Group (PWG).
- Fixed IF-M segmentation which failed in the presence of multiple small
attributes in front of a huge attribute to be segmented.
strongswan-5.3.2
----------------
- Fixed a vulnerability that allowed rogue servers with a valid certificate
accepted by the client to trick it into disclosing its username and even
password (if the client accepts EAP-GTC). This was caused because constraints
against the responder's authentication were enforced too late.
This vulnerability has been registered as CVE-2015-4171.
strongswan-5.3.1
----------------
- Fixed a denial-of-service and potential remote code execution vulnerability
triggered by IKEv1/IKEv2 messages that contain payloads for the respective
other IKE version. Such payload are treated specially since 5.2.2 but because
they were still identified by their original payload type they were used as
such in some places causing invalid function pointer dereferences.
The vulnerability has been registered as CVE-2015-3991.
- The new aesni plugin provides CBC, CTR, XCBC, CMAC, CCM and GCM crypto
primitives for AES-128/192/256. The plugin requires AES-NI and PCLMULQDQ
instructions and works on both x86 and x64 architectures. It provides
superior crypto performance in userland without any external libraries.
strongswan-5.3.0
----------------
- Added support for IKEv2 make-before-break reauthentication. By using a global
CHILD_SA reqid allocation mechanism, charon supports overlapping CHILD_SAs.
This allows the use of make-before-break instead of the previously supported
break-before-make reauthentication, avoiding connectivity gaps during that
procedure. As the new mechanism may fail with peers not supporting it (such
as any previous strongSwan release) it must be explicitly enabled using
the charon.make_before_break strongswan.conf option.
- Support for "Signature Authentication in IKEv2" (RFC 7427) has been added.
This allows the use of stronger hash algorithms for public key authentication.
By default, signature schemes are chosen based on the strength of the
signature key, but specific hash algorithms may be configured in leftauth.
- Key types and hash algorithms specified in rightauth are now also checked
against IKEv2 signature schemes. If such constraints are used for certificate
chain validation in existing configurations, in particular with peers that
don't support RFC 7427, it may be necessary to disable this feature with the
charon.signature_authentication_constraints setting, because the signature
scheme used in classic IKEv2 public key authentication may not be strong
enough.
- The new connmark plugin allows a host to bind conntrack flows to a specific
CHILD_SA by applying and restoring the SA mark to conntrack entries. This
allows a peer to handle multiple transport mode connections coming over the
same NAT device for client-initiated flows. A common use case is to protect
L2TP/IPsec, as supported by some systems.
- The forecast plugin can forward broadcast and multicast messages between
connected clients and a LAN. For CHILD_SA using unique marks, it sets up
the required Netfilter rules and uses a multicast/broadcast listener that
forwards such messages to all connected clients. This plugin is designed for
Windows 7 IKEv2 clients, which announces its services over the tunnel if the
negotiated IPsec policy allows it.
- For the vici plugin a Python Egg has been added to allow Python applications
to control or monitor the IKE daemon using the VICI interface, similar to the
existing ruby gem. The Python library has been contributed by Björn Schuberg.
- EAP server methods now can fulfill public key constraints, such as rightcert
or rightca. Additionally, public key and signature constraints can be
specified for EAP methods in the rightauth keyword. Currently the EAP-TLS and
EAP-TTLS methods provide verification details to constraints checking.
- Upgrade of the BLISS post-quantum signature algorithm to the improved BLISS-B
variant. Can be used in conjunction with the SHA256, SHA384 and SHA512 hash
algorithms with SHA512 being the default.
- The IF-IMV 1.4 interface now makes the IP address of the TNC access requestor
as seen by the TNC server available to all IMVs. This information can be
forwarded to policy enforcement points (e.g. firewalls or routers).
- The new mutual tnccs-20 plugin parameter activates mutual TNC measurements
in PB-TNC half-duplex mode between two endpoints over either a PT-EAP or
PT-TLS transport medium.
strongswan-5.2.2
----------------
- Fixed a denial-of-service vulnerability triggered by an IKEv2 Key Exchange
payload that contains the Diffie-Hellman group 1025. This identifier was
used internally for DH groups with custom generator and prime. Because
these arguments are missing when creating DH objects based on the KE payload
an invalid pointer dereference occurred. This allowed an attacker to crash
the IKE daemon with a single IKE_SA_INIT message containing such a KE
payload. The vulnerability has been registered as CVE-2014-9221.
- The left/rightid options in ipsec.conf, or any other identity in strongSwan,
now accept prefixes to enforce an explicit type, such as email: or fqdn:.
Note that no conversion is done for the remaining string, refer to
ipsec.conf(5) for details.
- The post-quantum Bimodal Lattice Signature Scheme (BLISS) can be used as
an IKEv2 public key authentication method. The pki tool offers full support
for the generation of BLISS key pairs and certificates.
- Fixed mapping of integrity algorithms negotiated for AH via IKEv1. This could
cause interoperability issues when connecting to older versions of charon.
strongswan-5.2.1
----------------
- The new charon-systemd IKE daemon implements an IKE daemon tailored for use
with systemd. It avoids the dependency on ipsec starter and uses swanctl
as configuration backend, building a simple and lightweight solution. It
supports native systemd journal logging.
- Support for IKEv2 fragmentation as per RFC 7383 has been added. Like IKEv1
fragmentation it can be enabled by setting fragmentation=yes in ipsec.conf.
- Support of the TCG TNC IF-M Attribute Segmentation specification proposal.
All attributes can be segmented. Additionally TCG/SWID Tag, TCG/SWID Tag ID
and IETF/Installed Packages attributes can be processed incrementally on a
per segment basis.
- The new ext-auth plugin calls an external script to implement custom IKE_SA
authorization logic, courtesy of Vyronas Tsingaras.
- For the vici plugin a ruby gem has been added to allow ruby applications
to control or monitor the IKE daemon. The vici documentation has been updated
to include a description of the available operations and some simple examples
using both the libvici C interface and the ruby gem.
strongswan-5.2.0
----------------
- strongSwan has been ported to the Windows platform. Using a MinGW toolchain,
many parts of the strongSwan codebase run natively on Windows 7 / 2008 R2
and newer releases. charon-svc implements a Windows IKE service based on
libcharon, the kernel-iph and kernel-wfp plugins act as networking and IPsec
backend on the Windows platform. socket-win provides a native IKE socket
implementation, while winhttp fetches CRL and OCSP information using the
WinHTTP API.
- The new vici plugin provides a Versatile IKE Configuration Interface for
charon. Using the stable IPC interface, external applications can configure,
control and monitor the IKE daemon. Instead of scripting the ipsec tool
and generating ipsec.conf, third party applications can use the new interface
for more control and better reliability.
- Built upon the libvici client library, swanctl implements the first user of
the VICI interface. Together with a swanctl.conf configuration file,
connections can be defined, loaded and managed. swanctl provides a portable,
complete IKE configuration and control interface for the command line.
The first six swanctl example scenarios have been added.
- The SWID IMV implements a JSON-based REST API which allows the exchange
of SWID tags and Software IDs with the strongTNC policy manager.
- The SWID IMC can extract all installed packages from the dpkg (Debian,
Ubuntu, Linux Mint etc.), rpm (Fedora, RedHat, OpenSUSE, etc.), or
pacman (Arch Linux, Manjaro, etc.) package managers, respectively, using the
swidGenerator (https://github.com/strongswan/swidGenerator) which generates
SWID tags according to the new ISO/IEC 19770-2:2014 standard.
- All IMVs now share the access requestor ID, device ID and product info
of an access requestor via a common imv_session object.
- The Attestation IMC/IMV pair supports the IMA-NG measurement format
introduced with the Linux 3.13 kernel.
- The aikgen tool generates an Attestation Identity Key bound to a TPM.
- Implemented the PT-EAP transport protocol (RFC 7171) for Trusted Network
Connect.
- The ipsec.conf replay_window option defines connection specific IPsec replay
windows. Original patch courtesy of Zheng Zhong and Christophe Gouault from
6Wind.
strongswan-5.1.3
----------------
- Fixed an authentication bypass vulnerability triggered by rekeying an
unestablished IKEv2 SA while it gets actively initiated. This allowed an
attacker to trick a peer's IKE_SA state to established, without the need to
provide any valid authentication credentials. The vulnerability has been
registered as CVE-2014-2338.
- The acert plugin evaluates X.509 Attribute Certificates. Group membership
information encoded as strings can be used to fulfill authorization checks
defined with the rightgroups option. Attribute Certificates can be loaded
locally or get exchanged in IKEv2 certificate payloads.
- The pki command gained support to generate X.509 Attribute Certificates
using the --acert subcommand, while the --print command supports the ac type.
The openac utility has been removed in favor of the new pki functionality.
- The libtls TLS 1.2 implementation as used by EAP-(T)TLS and other protocols
has been extended by AEAD mode support, currently limited to AES-GCM.
strongswan-5.1.2
----------------
- A new default configuration file layout is introduced. The new default
strongswan.conf file mainly includes config snippets from the strongswan.d
and strongswan.d/charon directories (the latter containing snippets for all
plugins). The snippets, with commented defaults, are automatically
generated and installed, if they don't exist yet. They are also installed
in $prefix/share/strongswan/templates so existing files can be compared to
the current defaults.
- As an alternative to the non-extensible charon.load setting, the plugins
to load in charon (and optionally other applications) can now be determined
via the charon.plugins.<name>.load setting for each plugin (enabled in the
new default strongswan.conf file via the charon.load_modular option).
The load setting optionally takes a numeric priority value that allows
reordering the plugins (otherwise the default plugin order is preserved).
- All strongswan.conf settings that were formerly defined in library specific
"global" sections are now application specific (e.g. settings for plugins in
libstrongswan.plugins can now be set only for charon in charon.plugins).
The old options are still supported, which now allows to define defaults for
all applications in the libstrongswan section.
- The ntru libstrongswan plugin supports NTRUEncrypt as a post-quantum
computer IKE key exchange mechanism. The implementation is based on the
ntru-crypto library from the NTRUOpenSourceProject. The supported security
strengths are ntru112, ntru128, ntru192, and ntru256. Since the private DH
group IDs 1030..1033 have been assigned, the strongSwan Vendor ID must be
sent (charon.send_vendor_id = yes) in order to use NTRU.
- Defined a TPMRA remote attestation workitem and added support for it to the
Attestation IMV.
- Compatibility issues between IPComp (compress=yes) and leftfirewall=yes as
well as multiple subnets in left|rightsubnet have been fixed.
- When enabling its "session" strongswan.conf option, the xauth-pam plugin opens
and closes a PAM session for each established IKE_SA. Patch courtesy of
Andrea Bonomi.
- The strongSwan unit testing framework has been rewritten without the "check"
dependency for improved flexibility and portability. It now properly supports
multi-threaded and memory leak testing and brings a bunch of new test cases.
strongswan-5.1.1
----------------
- Fixed a denial-of-service vulnerability and potential authorization bypass
triggered by a crafted ID_DER_ASN1_DN ID payload. The cause is an insufficient
length check when comparing such identities. The vulnerability has been
registered as CVE-2013-6075.
- Fixed a denial-of-service vulnerability triggered by a crafted IKEv1
fragmentation payload. The cause is a NULL pointer dereference. The
vulnerability has been registered as CVE-2013-6076.
- The lean stand-alone pt-tls-client can set up a RFC 6876 PT-TLS session
with a strongSwan policy enforcement point which uses the tnc-pdp charon
plugin.
- The new TCG TNC SWID IMC/IMV pair supports targeted SWID requests for either
full SWID Tag or concise SWID Tag ID inventories.
- The XAuth backend in eap-radius now supports multiple XAuth exchanges for
different credential types and display messages. All user input gets
concatenated and verified with a single User-Password RADIUS attribute on
the AAA. With an AAA supporting it, one for example can implement
Password+Token authentication with proper dialogs on iOS and OS X clients.
- charon supports IKEv1 Mode Config exchange in push mode. The ipsec.conf
modeconfig=push option enables it for both client and server, the same way
as pluto used it.
- Using the "ah" ipsec.conf keyword on both IKEv1 and IKEv2 connections,
charon can negotiate and install Security Associations integrity-protected by
the Authentication Header protocol. Supported are plain AH(+IPComp) SAs only,
but not the deprecated RFC2401 style ESP+AH bundles.
- The generation of initialization vectors for IKE and ESP (when using libipsec)
is now modularized and IVs for e.g. AES-GCM are now correctly allocated
sequentially, while other algorithms like AES-CBC still use random IVs.
- The left and right options in ipsec.conf can take multiple address ranges
and subnets. This allows connection matching against a larger set of
addresses, for example to use a different connection for clients connecting
from a internal network.
- For all those who have a queasy feeling about the NIST elliptic curve set,
the Brainpool curves introduced for use with IKE by RFC 6932 might be a
more trustworthy alternative.
- The kernel-libipsec userland IPsec backend now supports usage statistics,
volume based rekeying and accepts ESPv3 style TFC padded packets.
- With two new strongswan.conf options fwmarks can be used to implement
host-to-host tunnels with kernel-libipsec.
- load-tester supports transport mode connections and more complex traffic
selectors, including such using unique ports for each tunnel.
- The new dnscert plugin provides support for authentication via CERT RRs that
are protected via DNSSEC. The plugin was created by Ruslan N. Marchenko.
- The eap-radius plugin supports forwarding of several Cisco Unity specific
RADIUS attributes in corresponding configuration payloads.
- Database transactions are now abstracted and implemented by the two backends.
If you use MySQL make sure all tables use the InnoDB engine.
- libstrongswan now can provide an experimental custom implementation of the
printf family functions based on klibc if neither Vstr nor glibc style printf
hooks are available. This can avoid the Vstr dependency on some systems at
the cost of slower and less complete printf functions.
strongswan-5.1.0
----------------
- Fixed a denial-of-service vulnerability triggered by specific XAuth usernames
and EAP identities (since 5.0.3), and PEM files (since 4.1.11). The crash
was caused by insufficient error handling in the is_asn1() function.
The vulnerability has been registered as CVE-2013-5018.
- The new charon-cmd command line IKE client can establish road warrior
connections using IKEv1 or IKEv2 with different authentication profiles.
It does not depend on any configuration files and can be configured using a
few simple command line options.
- The kernel-pfroute networking backend has been greatly improved. It now
can install virtual IPs on TUN devices on OS X and FreeBSD, allowing these
systems to act as a client in common road warrior scenarios.
- The new kernel-libipsec plugin uses TUN devices and libipsec to provide IPsec
processing in userland on Linux, FreeBSD and Mac OS X.
- The eap-radius plugin can now serve as an XAuth backend called xauth-radius,
directly verifying XAuth credentials using RADIUS User-Name/User-Password
attributes. This is more efficient than the existing xauth-eap+eap-radius
combination, and allows RADIUS servers without EAP support to act as AAA
backend for IKEv1.
- The new osx-attr plugin installs configuration attributes (currently DNS
servers) via SystemConfiguration on Mac OS X. The keychain plugin provides
certificates from the OS X keychain service.
- The sshkey plugin parses SSH public keys, which, together with the --agent
option for charon-cmd, allows the use of ssh-agent for authentication.
To configure SSH keys in ipsec.conf the left|rightrsasigkey options are
replaced with left|rightsigkey, which now take public keys in one of three
formats: SSH (RFC 4253, ssh: prefix), DNSKEY (RFC 3110, dns: prefix), and
PKCS#1 (the default, no prefix).
- Extraction of certificates and private keys from PKCS#12 files is now provided
by the new pkcs12 plugin or the openssl plugin. charon-cmd (--p12) as well
as charon (via P12 token in ipsec.secrets) can make use of this.
- IKEv2 can now negotiate transport mode and IPComp in NAT situations.
- IKEv2 exchange initiators now properly close an established IKE or CHILD_SA
on error conditions using an additional exchange, keeping state in sync
between peers.
- Using a SQL database interface a Trusted Network Connect (TNC) Policy Manager
can generate specific measurement workitems for an arbitrary number of
Integrity Measurement Verifiers (IMVs) based on the history of the VPN user
and/or device.
- Several core classes in libstrongswan are now tested with unit tests. These
can be enabled with --enable-unit-tests and run with 'make check'. Coverage
reports can be generated with --enable-coverage and 'make coverage' (this
disables any optimization, so it should not be enabled when building
production releases).
- The leak-detective developer tool has been greatly improved. It works much
faster/stabler with multiple threads, does not use deprecated malloc hooks
anymore and has been ported to OS X.
- chunk_hash() is now based on SipHash-2-4 with a random key. This provides
better distribution and prevents hash flooding attacks when used with
hashtables.
- All default plugins implement the get_features() method to define features
and their dependencies. The plugin loader has been improved, so that plugins
in a custom load statement can be ordered freely or to express preferences
without being affected by dependencies between plugin features.
- A centralized thread can take care for watching multiple file descriptors
concurrently. This removes the need for a dedicated listener threads in
various plugins. The number of "reserved" threads for such tasks has been
reduced to about five, depending on the plugin configuration.
- Plugins that can be controlled by a UNIX socket IPC mechanism gained network
transparency. Third party applications querying these plugins now can use
TCP connections from a different host.
- libipsec now supports AES-GCM.
strongswan-5.0.4
----------------
- Fixed a security vulnerability in the openssl plugin which was reported by
Kevin Wojtysiak. The vulnerability has been registered as CVE-2013-2944.
Before the fix, if the openssl plugin's ECDSA signature verification was used,
due to a misinterpretation of the error code returned by the OpenSSL
ECDSA_verify() function, an empty or zeroed signature was accepted as a
legitimate one.
- The handling of a couple of other non-security relevant openssl return codes
was fixed as well.
- The tnc_ifmap plugin now publishes virtual IPv4 and IPv6 addresses via its