<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EpostStil17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=NO-BOK link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>At the moment I have only succesfully integrated strongswan with gingerbread, and patched the VPN frontend, I have not actually used it, but I will shortly, so I will let you know whether I can generate valid certificates or not as soon as I try it.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Federico<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Fra:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Richard Pickett [mailto:richard.pickett@csrtechnologies.com] <br><b>Sendt:</b> 7. oktober 2011 21:32<br><b>Til:</b> Mancini, Federico<br><b>Emne:</b> Re: [strongSwan] Strongswan on android gingerbread<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Federico,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I've had problems generating certs that android will take, sometimes it takes them, sometimes from the same ca and settings it won't take them.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Do you mind sharing how you're generating your certs for your android setup?<br clear=all><o:p></o:p></p><div><p class=MsoNormal>On Fri, Oct 7, 2011 at 1:54 AM, <<a href="mailto:Federico.Mancini@ffi.no">Federico.Mancini@ffi.no</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Thanks,<br>the problem was indeed the file strings.xml.origin. Once that was removed, everything went fine!<br>So I can confirm that the patches work smoothly also with gingerbread (there was no .rej file and no -b option was used, it was enough to cancel the .origin file).<br><br>Federico<br><br>-----Opprinnelig melding-----<br>Fra: Tobias Brunner [mailto:<a href="mailto:tobias@strongswan.org">tobias@strongswan.org</a>]<br>Sendt: 6. oktober 2011 15:19<br>Til: Mancini, Federico<br>Kopi: <a href="mailto:users@lists.strongswan.org">users@lists.strongswan.org</a><br>Emne: Re: [strongSwan] Strongswan on android gingerbread<o:p></o:p></p><div><div><p class=MsoNormal><br>Hi Federico,<br><br>> The problem comes when I try to patch the VPN frontend as written here:<br>> <a href="http://wiki.strongswan.org/projects/strongswan/wiki/AndroidFrontend" target="_blank">http://wiki.strongswan.org/projects/strongswan/wiki/AndroidFrontend</a>.<br><br>Did the patches apply cleanly? Look for .rej files.<br><br>> The android source doesn’t compile anymore. I suspect it is because I am<br>> using Gingerbread instead of Froyo maybe?<br><br>Probably, the patch was initially created for 1.6 and then ported to<br>Froyo which also needed some tweaking. So it's reasonable to assume<br>that there will be stuff that does not work properly on Gingerbread.<br><br>> I get the following errors that have to do with this strings.xml file<br>> (the actual list of errors is much longer, but they are all of the same<br>> type of these):<br>><br>> frameworks/base/core/res/res/values/strings.xml:2458: Originally defined<br>> here.<br>><br>> frameworks/base/core/res/res/values/strings.xml.orig:2461: error:<br><br>You get these errors because patch created a copy of the original<br>unpatched file as strings.xml.orig. Since both files define the same<br>strings and the build system seems to include all files in res/values<br>(not just *.xml) you get the observed errors. Patch will do this if<br>called with the -b option or if a patch did not apply cleanly. In the<br>latter case you should also see a strings.xml.rej file containing the<br>failed hunk. If so, you should be able to easily fix it as the patch<br>for strings.xml contains just one added line (be sure to delete the<br>files created by patch).<br><br>> Also, in practice, is the frontend patch only for usability? In other<br>> words, if there is no fix to my problem, is it actually possible to use<br>> strongswan without the frontend patch? And if so, how?<br><br>That depends on what you intend to do. Currently only charon (the IKEv2<br>daemon) and the newer libraries are built with the provided Android.mk<br>files, so there is no pluto (IKEv1 daemon) or starter. Without starter<br>you won't be able to use ipsec.conf to configure the daemon. Also, the<br>ipsec script and stroke are not built so interaction with the daemon is<br>not directly possible (the frontend uses charon's android plugin for<br>this). What you could do is build your own plugin with your own config<br>backend (e.g. using an sqlite database, although the sql plugin could<br>probably also be used for that) and your own frontend to control the<br>daemon. You could also try to build the stroke plugin and then use the<br>stroke socket to control the daemon. We also know that there are<br>currently some people working on getting starter and pluto running on<br>Android, but they are not yet there.<br><br>Anyway, the frontend patch should be considered as a proof of concept.<br>It simply adds an additional type of VPN to the default Android VPN<br>applet, which allows to easily setup IKEv2 connections but is fairly<br>limited at that. For instance, the only authentication methods<br>currently supported are EAP methods with username/password<br>authentication (e.g. eap-mschapv2 or eap-md5). Also, there are<br>basically only two configuration options, the IP/hostname of the gateway<br>and the CA certificate (read from the Android KeyStore). Other options<br>are predefined for usage in road-warrrior scenarios (e.g. a virtual IP<br>is requested from the gateway and the the proposed traffic selector is<br>simply <VirtualIP>/32 === <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a>).<br><br>Regards,<br>Tobias<br>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.strongswan.org">Users@lists.strongswan.org</a><br><a href="https://lists.strongswan.org/mailman/listinfo/users" target="_blank">https://lists.strongswan.org/mailman/listinfo/users</a><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>