|
Ohhh 
Thanks men , I cannot browse all the information, its too much...
Thanks again and have a nice day!
Regards,
KZ
|
|
|
|
|
Sorry about that. Good luck.
|
|
|
|
|
Thanks for your help and if you need something let me know!
|
|
|
|
|
Pascal's Triangle in C program using loop
|
|
|
|
|
From what I can gather, it was Colonel Mustard in the Drawing Room with the Candlestick.
|
|
|
|
|
a free Google-fu search for you[^]
Next Google-fu search costs a pound 
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
|
|
|
|
|
Can I have a few of them please, I could use losing a few pounds!
If you send me a LMGTFY for weight loss I will be mightily displeased
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
|
somasaedi wrote: Pascal's Triangle in C program using loop
What about it? Also c != c#.
If you can't be bothered to read the site guidance about asking a question, I can't be bothered to tell you why I downvoted your question properly.
|
|
|
|
|
Would you like fries with that?
/ravi
|
|
|
|
|
Google is your best friend.
Google Search.[^]
Pascal's triangle in C#[^]
The first step in the acquisition of wisdom is SILENCE, the second is LISTENING, the third MEMORY, the forth, PRACTICE and the fifth is TEACHING others!
|
|
|
|
|
|
|
What bout it?
The first step in the acquisition of wisdom is SILENCE, the second is LISTENING, the third MEMORY, the forth, PRACTICE and the fifth is TEACHING others!
|
|
|
|
|
Hi I am looking for the best method and most secure method of connecting to a remote MySQL database from a c# application.
I have an application that allows users to login by verifying the credentials with a remote MySQL database. The whole application is dependant on the database.
So far I am just using the .net MySQL connector. but someone mentioned this is insecure especially since people decompile apps a lot and I have the database login details inside the app.
In your opinion what would be the best method of securely reading, updating and adding data to a remote MySQL database?
Thanks for any replies! 
modified 11-Mar-21 21:01pm.
|
|
|
|
|
If you are only worried about your connection string, you can just use an encrypted section in the .config file.
Anyways, connecting to a SQL server directly is not secure. Traffic is not encrypted and anybody with a sniffer can see everything. You should instead connect to a TCP/IP server (that you write, obviously) using SSL that proxys the database calls. That way, you don't have the connection string in your app, but you are still going to have the server info in your app, so... The DB proxy method has additional benefits since it also allows you to compress data. SQL does not. A bit more work though...
|
|
|
|
|
Do you use compression in your apps and if so does it make a reasonable difference?
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Depends what queries you're doing, but database data is usually highly repetitive so you should get massive improvements by compressing it.
|
|
|
|
|
Depends on the data & scenario. I.e. compressing small data will actually result in the "compressed" data being larger then the original. Then there is the overhead in compressing & decompressing on the fly, or storing the data in compressed format. Honestly, usually its not worth the hassle if your queries are optimized. Compressing 1MB down to 250KB isn't going to make a difference in the real world.
|
|
|
|
|
A more secure way would isolate the database, and only provide the interface over a webservice. A more secure way than that would be to use SSL.
..how much security do you need?
Bastard Programmer from Hell 
if you can't read my code, try converting it here[^]
|
|
|
|
|
It depends also on how "remote" that database is. If it is in a virtual private network, that VPN should actually be safe/secured enough.
|
|
|
|
|
What are you trying to secure against?
If you are using a single key for all instances of the application, and including it in the application distribution, then it is pretty straightforward for a hacker to get hold of the key (or login credentials) and contact the database with it.
To avoid interception or viewing of data as it's on the network, you should always use SSL or something similar (i.e. an encrypted channel using a public key encryption algorithm at some point) for the transfer. If you set up a web service or HTTP server it's straightforward to use SSL. This prevents someone from sniffing the packets of someone else's data, but it doesn't affect their ability to decompile and get the credentials.
The only real way to avoid that is to require people to log in, so the application doesn't have the credentials at all. That's obviously annoying and can often have a bigger cost than the security concern.
It's usually a good idea to proxy a database by having a service layer (either a web service or a TCP server application) in between. That insulates you from a particular database implementation, and it also allows you to restrict the actions a user can do, even with the credentials. If, for example, your concern is corruption of data as opposed to viewing it, this application can sanity check any requested updates to the database.
|
|
|
|
|
Thanks all for the great suggestions. So for example i have
Application(e.g login)
|
connect to remote database
|
application requests data
|
database sends data
|
application handles it.
---------------
from the suggestions a possible secure method to change to?:
Application
|
connect to webservice and initiate connection to db(ssl)
|
application sends query string for e.g to the web service(ssl)
|
application requests data encrypted from the webservice of which connects to the database retrieves the data and sends it to the app(ssl)
|
application handles it.
modified 11-Mar-21 21:01pm.
|
|
|
|
|
Your application should not know anything about the database including connection strings, queries, tables, etc. The web service should do all that and expose an API that your app will consume.
An TCP/IP socket server will vastly out-perform a web service. Also, 2-way communication is a PITA in a web service.
* you need to think how many simulataneous users will connect
* typical internet connection of your users
* if you will need 2 way communication
|
|
|
|
|
Thank you, I will take all this advice on-board and do some research into web services and such. I am knew to working with databases in a desktop application so I am learning a lot.
Thank you so much for advice. 
modified 11-Mar-21 21:01pm.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
