Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #17572 > unrolled thread

Encrypted field in form (HTTPS question)

Back to article view | Back to comp.lang.php

Contents

  Encrypted field in form (HTTPS question) bit-naughty@hotmail.com - 2017-08-20 20:43 -0700
    Re: Encrypted field in form (HTTPS question) Richard Damon <Richard@Damon-Family.org> - 2017-08-21 00:02 -0400
      Re: Encrypted field in form (HTTPS question) V <vvvvvvvvvvvvvvvvvvvv11111@mail.ee> - 2023-04-03 06:57 -0700
        Re: Encrypted field in form (HTTPS question) doctor@doctor.nl2k.ab.ca (The Doctor) - 2023-04-03 14:19 +0000

#17572 — Encrypted field in form (HTTPS question)

I'm trying to set up a simple blogging system, where I have a form which will have a textbox which will allow me to post stuff. Now I want a password field on the form, so that random people cannot post. I would like this password to be ENCRYPTED during transit. So - there'll be TWO textboxes, one for the password, and one for the post itself - what would the coding for the form look like? It's only the password that has to be encrypted, not the post. I realise this is more of an HTML question, but really, it concerns the whole thing, front end as well as back. I have no idea what HTTPS coding on the backend looks like. How would I extract the unencrypted password on the server side?


Thanks for your help.

[toc] | [next] | [standalone]

#17573

On 8/20/17 11:43 PM, bit-naughty@hotmail.com wrote:
> I'm trying to set up a simple blogging system, where I have a form which will have a textbox which will allow me to post stuff. Now I want a password field on the form, so that random people cannot post. I would like this password to be ENCRYPTED during transit. So - there'll be TWO textboxes, one for the password, and one for the post itself - what would the coding for the form look like? It's only the password that has to be encrypted, not the post. I realise this is more of an HTML question, but really, it concerns the whole thing, front end as well as back. I have no idea what HTTPS coding on the backend looks like. How would I extract the unencrypted password on the server side?
> 
> 
> Thanks for your help.
> 

A form post in pure HTML can not encrypt some data.

You could just submit the form via HTTPS, so the whole form is 
encrypted. HTTPS does the encryption in the communication layer, and you 
get the unencrypted results (so it is mostly transparent to your script)

A second option, that probably isn't really worth doing, is adding 
javascript to the form, and have that run on submit and have the 
javascript encrypt the data. You would need to create a new 
public/private key for each instance of the form sent out to do the 
encryption, and send the public key with the form. On reception, the 
page would need to look up the public key to find the matching private 
key, and use that to decode the password.

[toc] | [prev] | [next] | [standalone]

#19416

groups.google.com/g/sci.math/c/sFUlUZ47ZGs



On Monday, August 21, 2017 at 6:02:18 AM UTC+2, Richard Damon wrote:
> On 8/20/17 11:43 PM, bit-n...@hotmail.com wrote: 
> > I'm trying to set up a simple blogging system, where I have a form which will have a textbox which will allow me to post stuff. Now I want a password field on the form, so that random people cannot post. I would like this password to be ENCRYPTED during transit. So - there'll be TWO textboxes, one for the password, and one for the post itself - what would the coding for the form look like? It's only the password that has to be encrypted, not the post. I realise this is more of an HTML question, but really, it concerns the whole thing, front end as well as back. I have no idea what HTTPS coding on the backend looks like. How would I extract the unencrypted password on the server side? 
> > 
> > 
> > Thanks for your help. 
> >
> A form post in pure HTML can not encrypt some data. 
> 
> You could just submit the form via HTTPS, so the whole form is 
> encrypted. HTTPS does the encryption in the communication layer, and you 
> get the unencrypted results (so it is mostly transparent to your script) 
> 
> A second option, that probably isn't really worth doing, is adding 
> javascript to the form, and have that run on submit and have the 
> javascript encrypt the data. You would need to create a new 
> public/private key for each instance of the form sent out to do the 
> encryption, and send the public key with the form. On reception, the 
> page would need to look up the public key to find the matching private 
> key, and use that to decode the password.

[toc] | [prev] | [next] | [standalone]

#19418

In article <785e8f42-1ab5-4fef-9c96-ff06137e61f7n@googlegroups.com>,
V  <vvvvvvvvvvvvvvvvvvvv11111@mail.ee> wrote:
>groups.google.com/g/sci.math/c/sFUlUZ47ZGs
>
>
>
>On Monday, August 21, 2017 at 6:02:18=E2=80=AFAM UTC+2, Richard Damon wrote=
>:
>> On 8/20/17 11:43 PM, bit-n...@hotmail.com wrote:=20
>> > I'm trying to set up a simple blogging system, where I have a form whic=
>h will have a textbox which will allow me to post stuff. Now I want a passw=
>ord field on the form, so that random people cannot post. I would like this=
> password to be ENCRYPTED during transit. So - there'll be TWO textboxes, o=
>ne for the password, and one for the post itself - what would the coding fo=
>r the form look like? It's only the password that has to be encrypted, not =
>the post. I realise this is more of an HTML question, but really, it concer=
>ns the whole thing, front end as well as back. I have no idea what HTTPS co=
>ding on the backend looks like. How would I extract the unencrypted passwor=
>d on the server side?=20
>> >=20
>> >=20
>> > Thanks for your help.=20
>> >
>> A form post in pure HTML can not encrypt some data.=20
>>=20
>> You could just submit the form via HTTPS, so the whole form is=20
>> encrypted. HTTPS does the encryption in the communication layer, and you=
>=20
>> get the unencrypted results (so it is mostly transparent to your script)=
>=20
>>=20
>> A second option, that probably isn't really worth doing, is adding=20
>> javascript to the form, and have that run on submit and have the=20
>> javascript encrypt the data. You would need to create a new=20
>> public/private key for each instance of the form sent out to do the=20
>> encryption, and send the public key with the form. On reception, the=20
>> page would need to look up the public key to find the matching private=20
>> key, and use that to decode the password.

This abusive spamtroll came from

comp.lang.php #168007 (1 more)
X-Received: by 2002:a05:620a:2053:b0:746:88d4:820 with SMTP id d19-
+           20020a05620a205300b0074688d40820mr8365077qka.10.1680530278613;
+           Mon, 03 Apr 2023 06:57:58 -0700 (PDT)
X-Received: by 2002:a05:622a:199a:b0:3e3:7cec:ae42 with SMTP id
+           u26-20020a05622a199a00b003e37cecae42mr13793491qtc.6.1680530278277;
+           Mon, 03
+           Apr 2023 06:57:58 -0700 (PDT)
Path: news.nk.ca!news.uzoreto.com!peer03.ams4!peer.am4.highwinds-media.com!
+     peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-
+     out.google.com!nntp.google.com!postnews.google.com!google-groups.
+     googlegroups.com!not-for-mail
Newsgroups: comp.lang.php
Date: Mon, 3 Apr 2023 06:57:58 -0700 (PDT)
In-Reply-To: <5XsmB.32779$kJ2.25267@fx33.iad>
Injection-Info: google-groups.googlegroups.com; posting-host=85.253.121.82;
+               posting-account=HfIszAoAAAC8ch6q3uChpTWUALHCfEoF
NNTP-Posting-Host: 85.253.121.82
References: <d84489df-16bf-4856-a24f-c4e91d2ae2b4@googlegroups.com> <5XsmB.
+           32779$kJ2.25267@fx33.iad>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <785e8f42-1ab5-4fef-9c96-ff06137e61f7n@googlegroups.com>
Subject: Re: Encrypted field in form (HTTPS question)
From: V <vvvvvvvvvvvvvvvvvvvv11111@mail.ee>
Injection-Date: Mon, 03 Apr 2023 13:57:58 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3027
Xref: news.nk.ca comp.lang.php:168007


Spamtrollers are trolls posting useless spam thinking it is content
but are posting useless noise. Spamtrolls are newsgroup vandals!
Thoses trolls are as bad as Donald 
Trump on Twitter.

This makes
https://groups.google.com/search/conversations?q=Depeer%20Google%20Groups

Depeer Google groups Now!!

Spamtroller   , thou art rebuked in the Name of Yahweh the Father, 
Jesus the Son and the Holy Spirit for Jesus has all authority here
and Satan has no authority here!
-- 
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b 
The Church must example being a holy bride. -unknown Beware https://mindspring.com

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.php

csiph-web