443 serves too
Post by twetch#15875
https://twitter.com/tewkenaire?lang=en
it should be https with encryption as it accepts user logins
What the chain says
- Block
- 630 757
- Time
- 2020-04-15T20:47:49Z
- Signer
- 148sxacPXapQNhFBRnY9PPY5qcyoiacGeq
- App
- twetch
- Type
- post
- Content type
- text/plain
- Name in tx
- twetch#15875
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
Signed by
148sxacPXapQNhFBRnY9PPY5qcyoiacGeq VerifiedReplies (16)
You're right. btw are GET requests also encrypted? If some dev makes a form that passes credentials with query string parameters, dis safe?
https establishes an underlying SSL secure sockets layer connection before any http data is trans
https://stackoverflow.com/questions/4143196/is-get-data-also-encrypted-in-https
The entire request is encrypted, including the URL, and even the command (GET)
you have to understand.. iamsatan not CSW
btw... please tell that fool #3 to remove my trolltoll so i can write in my own threads again chur bro
what is unsafe with user information gathering is unsalted encryption
it is too easy for admin to take your non salted encryption and run it thru decryption, i know admin could already just take funds but people often use same passwords elsewhere (fools)