this post was submitted on 19 Jan 2024
10 points (72.7% liked)

Web Development

3413 readers
3 users here now

Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development

What is web development?

Web development is the process of creating websites or web applications

Rules/Guidelines

Related Communities

Wormhole

Some webdev blogsNot sure what to post in here? Want some web development related things to read?

Heres a couple blogs that have web development related content

CreditsIcon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
 

Is there a way to develop and website using JS (and perhaps PHP) to create an E2EE website. Were all packets sent between the server and the userw device are E2EE, wrapped in a layer of encryption?

I know there is HTTPS but I am looking for something stronger than HTTPS.

By using some JS or PHP E2EE package, would I have to write or structure the website code very differently than you normally would?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 7 months ago (2 children)

I may not have a domain name, and therefore no HTTPS, just HTTP only and can only connect by knowing the IP address and port number.

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago)

I feel like you should just use a reverse proxy tbh.

Is it internal? Because otherwise this is a super bad plan

[–] [email protected] 1 points 7 months ago

And you cant use self signed certificates because?
They provide the same level of encryption. The benefit of a domain and a trusted CA issued cert is that browsers/os will automatically trust that the server is who its said it is (ie you dont get a warning).

But if you import your servers root CA to your OS, then your OS (and browser) will automatically trust any cert issued using that root cert, thus you dont get a warning.

With or without a warning, it will still encrypt at TLS1.3