Linqpad connection password NO after imaging the instance on server

vickyrathee

I was trying to use linqpad on our windows server for basic DB queries, but the connection string doesn't work after we create an Image(AMI) on AWS > And relaunch the instance using that AMI.

I think that Linqpad store the connection/password decryption key somewhere in local system cache, which is not migrated to AMI and then to new machines while imaging. This causes all the connection lost and automation scripts not to work.

Any workaround?

nescafe

This is because the password is encrypted and the user/machine encryption key is somehow changed after the imaging process.

https://www.linqpad.net/FAQ.aspx#security

If I save a connection that uses SQL Authentication, does LINQPad store the password in plain text?
Of course not! LINQPad encrypts the password securely using the Windows Data Protection API.

There is a workaround. In the connection screen, go to "Advanced" and enter the password in the Additional connection string parameters area:

Password=<password>

vickyrathee

@nescafe But that breaks all the reason of Linqpad portable deployment, as copying the deployment folder to other machine won't work. I will try the workaround, but I also submitted a suggestion to give option to disable encryption to make the portable app work when needed.

https://linqpad.uservoice.com/forums/18302-linqpad-feature-suggestions/suggestions/36422497-give-option-to-disable-encryption-of-the-connectio