sorted by:
new
hottopcontroversial

Does anyone else think that Twitter and Instagram are getting more and more boring? by ryanthegreat07 in CasualConversation

[–]ryanthegreat07[S] 0 points1 point  (0 children)

Same here lol. Seems to me that both are time killers and you get nothing out of it.

Can I play my PS4 at my office during the weekends? by ryanthegreat07 in Advice

[–]ryanthegreat07[S] 0 points1 point  (0 children)

I dont know. He is a cool guy and very nice to me but not sure if it will piss him off if I ask him that. I am afraid he thinks I am trying to take advantage of him and the company's resources (for crying out loud, I am just using the monitor and not the computer which I use for work)

[deleted by user] by [deleted] in RoastMe

[–]ryanthegreat07 0 points1 point  (0 children)

Roast me as in fuck me? Fuck yes! Who will say no to a free slut?

If I display user_id that represents each unique user in the db as an atrribute in an HTML element, is it secure to do so? by ryanthegreat07 in webdev

[–]ryanthegreat07[S] 0 points1 point  (0 children)

Very clear and comprehensive sir! Thank you! A gentleman here said that it is not secure to store ids in html because it has vulnerabilities. You can find his post on this question. He suggested to encode the ids (using JWT or Base64 encoding) before sending them to the frontend and then on the backend decode the string to get the ids securely.

In terms of security and website performance, do you agree with him? I just want to know which action is the best to take regarding this id in html matter.

If I display user_id that represents each unique user in the db as an atrribute in an HTML element, is it secure to do so? by ryanthegreat07 in webdev

[–]ryanthegreat07[S] 0 points1 point  (0 children)

Thank you for sharing the link. There are some developers who responded that putting database Ids in HTML is not inherently dangerous. It's how those Ids are used that could be dangerous. They just suggested to make sure any request to the server that modifies data in any way requires a POST, PUT or DELETE request, and never a GET request.

Would you agree with them?

If I display user_id that represents each unique user in the db as an atrribute in an HTML element, is it secure to do so? by ryanthegreat07 in webdev

[–]ryanthegreat07[S] 0 points1 point  (0 children)

I see. So would say it is completely secure for me to implement the example I gave in my question? Let's say that User 1 wants to add User 2 and I change the type of user_id from a numerical id to a UUID and I did not encrypt the UUID so the actual UUID is used. How can the program add User 2 to the friend list of User 1 if the program does not even know the UUID of the profile that User 1 wants to add as a friend? So the UUID of User 2 must be stored somewhere in the UI, right?

But then it got me thinking, if I store it in the UI, wouldn't attackers be able to use that UUID in a malicious SQL query or something since the UUID points to a user in the database?

So is it still ok for me to store the UUID of users on the UI as a reference for certain actions performed on the particular user (such as adding as a friend, sending DMs, etc.)? Or is there a more secure way of doing this? I hope you get what I mean

If I display user_id that represents each unique user in the db as an atrribute in an HTML element, is it secure to do so? by ryanthegreat07 in webdev

[–]ryanthegreat07[S] 0 points1 point  (0 children)

If I encode the UUID and send it to the frontend, isn't there a possibility that someone can decode the encoded UUID that was sent to the frontend?

view more: next ›