HTTPS is enough. Despite that, how would you handle the **client** doing decryption and encryption? I don't think this is an idea you should pursue, especially if your expertise is not in security.
On Tuesday, 16 January 2018 10:03:00 UTC+11, Vishwas Mittal wrote: > > Hello everyone, > > I am a new contributor to django, and would like to propose a new > middleware to django that can provide some degree of security for HTTP > connections by encrypting the data to be sent in response. > > This middleware will work on the principles of HTTPS but the main > difference is there will no certification authority involved. > > This will include the middleware inplementation and also a user side code/ > implementaion which can be used to complete the encryption-decryption > couple. > > Please present your thoughts and make necessary suggestions regarding this. > > > Regards > Vishwas > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/184bbb3a-b7b8-4ef0-bc02-b5e888ffa549%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
