Uh...  if it can't do more than rc4, and it can't verify anything, then it'=
s just barely better than no encryption.  It will stop causal browsing.

I would stick to a RESTful posting model, and avoid SOAP at all costs.  Ask=
 them if you could just post JSON or simple XML to some web server, and hav=
e the far more powerful web server do the heavy lifting, for instance.  I h=
ave some simple Arduino boards posting JSON back to a central site, where t=
he data is then re-published (sometimes immediately) over any number of pro=
tocols.

--Michael



On Aug 7, 2013, at 12:22 PM, Ruben J=F6nsson <ruben@rjjournal.net> wrote:

>> ALSO: Does the Microchip stack really support HTTPS? It would be a bit
>> surprising if it did since it requires quite a bit of supporting stuff
>> (encryption, etc.)
>>=20
>> -- Bob Ammerman
>> RAm Systems
>>=20
>=20
> The stack does support both SSL server and client using ARCFOUR encryptio=
n.=20
> There are some limitations - Client can not validate or verify certificat=
es and=20
> client and server can not completely verify MACs before processing data.=
=20
>=20
> Haven't used it myself though. =20
>=20
> /Ruben
>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Ruben J=F6nsson
> AB Liros Electronic
> Box 9124
> 200 39 Malm=F6 Sweden
> Tel +46 40142078
> ruben@rjjournal.net
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> --=20
> http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>=20


--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.