I'm in no way experienced with C#, however I did some looking at the documentation online and did some research on cryptography in said language.
As far as I can tell, it looks like you've taken the correct procedures to secure your code! Your use of RNGCryptoServiceProvider looks well structured and without holes. The length of your salt (32 bytes, correct?) seems good. 16 should be your minimum (that's not a rule, just a suggestion), but you could go higher than 32 if you wanted. The mindset should not be: the longest salt is the strongest, rather: the longer the salt, the less likely it will be to guess it. You can find more detail on that over at Sec.SE over at Sec.SE.
Overall, it appears good. I'm no expert, so if I've got something wrong I hope someone comments or chimes in here!
I'm in no way experienced with C#, however I did some looking at the documentation online and did some research on cryptography in said language.
As far as I can tell, it looks like you've taken the correct procedures to secure your code! Your use of RNGCryptoServiceProvider looks well structured and without holes. The length of your salt (32 bytes, correct?) seems good. 16 should be your minimum (that's not a rule, just a suggestion), but you could go higher than 32 if you wanted. The mindset should not be: the longest salt is the strongest, rather: the longer the salt, the less likely it will be to guess it. You can find more detail on that over at Sec.SE.
Overall, it appears good. I'm no expert, so if I've got something wrong I hope someone comments or chimes in here!
I'm in no way experienced with C#, however I did some looking at the documentation online and did some research on cryptography in said language.
As far as I can tell, it looks like you've taken the correct procedures to secure your code! Your use of RNGCryptoServiceProvider looks well structured and without holes. The length of your salt (32 bytes, correct?) seems good. 16 should be your minimum (that's not a rule, just a suggestion), but you could go higher than 32 if you wanted. The mindset should not be: the longest salt is the strongest, rather: the longer the salt, the less likely it will be to guess it. You can find more detail on that over at Sec.SE.
Overall, it appears good. I'm no expert, so if I've got something wrong I hope someone comments or chimes in here!
I'm in no way experienced with C#, however I did some looking at the documentation online and did some research on cryptography in said language.
As far as I can tell, it looks like you've taken the correct procedures to secure your code! Your use of RNGCryptoServiceProvider looks well structured and without holes. The length of your salt (32 bytes, correct?) seems good. 16 should be your minimum (that's not a rule, just a suggestion), but you could go higher than 32 if you wanted. The mindset should not be: the longest salt is the strongest, rather: the longer the salt, the less likely it will be to guess it. You can find more detail on that over at Sec.SE.
Overall, it appears good. I'm no expert, so if I've got something wrong I hope someone comments or chimes in here!