Fred @codeBA01

Software Engineer | I love building efficient solutions😁 | Gaming helps me chill out. linktr.ee/codeBA Remote Joined August 2011

Tweets

4K
Followers

377
Following

379
Likes

12K

Fred @codeBA01

3 weeks ago

@elite_developer “Backend is easier” Just say you have been writing structural and technical debts. No field is easy if you really know what you’re doing.

1 0 1 11 0

View Details

@Dokeezy @LMDiddy14 Dude, CR7 draw the defenders to himself, if you watch from the other angle you will know that there are at least 2 Portugal players in the box and 1 is on the other wing with only one opponent defender. Bruno could have make a cross to the other wing to use the advantage.

0 0 4 233 0

View Details

Fred @codeBA01

a month ago

@CFC_Janty And that’s the advantage they don’t know they have. Cristiano Ronaldo being on the pitch will always be a threat to the opponents either he score or not, they can’t count him out so they will always have like 3 players marking only him, and that is a big advantage.

1 2 15 2K 1

View Details

Fred @codeBA01

a month ago

System design is a game of trade offs.

0 0 0 4 0

View Details

Fred @codeBA01

2 months ago

@SahilExec 2. For the security issue, it will be the password being plain text only if the password hashing was not implemented in the createUser function. but since we are not shown the content of the function, we will just assume that the password is being stored as plain text. 2/2

0 0 0 43 0

View Details

Fred @codeBA01

2 months ago

@SahilExec 1. Honestly, the race condition in the sign up will only occur if the database unique constraint is not enforced on the email field in the database. No in-code handling will fix it. 1/2

2 0 0 727 0

View Details

Fred @codeBA01

2 months ago

@ashoKumar89 If the 2 actions are not possible, I will pull the last card which switching the JWT secret key, this action will force every user to login again due to invalid JWT token.

0 0 1 29 0

View Details

Fred @codeBA01

2 months ago

@ashoKumar89 JWT expire 30day is already a security risk. I will assume blacklist token system is not implemented. With a leak like this, I will quickly implement force logout for user’s stolen device. If the device is unknown, I will do a force logout for users in the geolocation.

1 0 1 323 0

View Details

Fred @codeBA01

2 months ago

@ashoKumar89 1. User input is not sanitised. 2. Raw data are passed to SQL query 3. No error handling. Number 1 & 2 gives room for dangerous attacks like SQL injection and data corruption too. Number 3 can cause a serious problem like a system crash in production.

0 0 4 2K 0

View Details

Fred @codeBA01

2 months ago

@TheCleanCarClub Turn your steering wheels to the right completely, then reverse

0 0 0 3 0

View Details

Fred @codeBA01

2 months ago

@EOEboh Index works just like the table of contents at the first page of a book. It gives you an easy link to anything you are looking in the book, but if any update is made to the content of the book, the table of contents will need to be updated too.

0 0 3 393 0

View Details

Fred @codeBA01

3 months ago

@monokichangf @bartonovopolis Always.

0 0 0 1K 0

View Details

Fred @codeBA01

3 months ago

@osemagnum Not bad

0 0 0 47 0

View Details

Fred @codeBA01

3 months ago

@EOEboh MVP, forward will need assistance.

0 0 0 37 0

View Details

Fred @codeBA01

3 months ago

@javarevisited Check the metric and monitoring to get the endpoints under heavy load. Stop the bleeding by increasing rate limiting on the endpoints. Add cache for the most frequent requested data to ease the hit rate on database. Check the metric and monitoring again to see if is under control

0 0 0 957 0

View Details

Fred @codeBA01

3 months ago

@PenguinCabinet

0 0 1 2K 0

View Details

Fred @codeBA01

3 months ago

@Gamingtronium Device + IP address rate limiting for public endpoint Device + IP address + user rate limiting for private endpoint

0 0 0 298 1

View Details

Fred @codeBA01

3 months ago

@EOEboh User input was not sanitised before being passed into the SQL query causing the input to alter the original Raw SQL query, returning user data. This is called SQL injection. Sanitising of user input and using options like prepared statements could have prevents this attack.

0 0 2 358 0

View Details

Fred @codeBA01

3 months ago

@ashoKumar89 Cause the trade off is worth it. ORM promote speed in development, maintainability and productivity. Though, it can hide inefficiencies, most ORM provide options to write raw queries which also help you ease the inefficiencies.

0 0 2 327 1

View Details

Fred @codeBA01

3 months ago

@ashoKumar89 No, let’s prioritize security first, we need to retain our current users while attracting more. To do that, we need to ensure their data are secure with us. Storing their passwords in plain text doesn’t align with that goal. We can’t afford any security breach.