Please don't hate me for this too much...
First let me say that I really, really want to do this. However, that part of me that has been through all the various forms of IT security training, etc. is having a difficult time accepting that files from an unofficial source are going to be completely safe. Am I crazy to think that way? Can anyone help me overcome my doubts? I really would love to stick my proverbial thumb in AT&T's proverbial eye.
I CAN ANSWER THIS!!!
I worked IT and Network support for almost a decade at a large Police Dept (south east cost is all I am willing to say as to where) , so I understand your concerns. Random roms can sneak random crap onto your stuff. It's a HUGE issue with Android Devices.
Now, here are some positives.
No other "roms" are available for the AT&T 830. If that wasn't the case, we would have had the issues fixed months ago! All other 830 variant roms don't work, and well, I haven't bothered with custom roms on windows phone since Windows Mobile 6.5! How many Lumia "rom" files are out there (any lumia) that are NOT 100% authentic from MS/Nokia? Things that barely or didn't work at all now work. Bluetooth, wifi, netflix, etc.
This is sourced from MS own servers from the time it was available. This has happened before, where an update gets pushed and then pulled within hours, but I've never seen it happen for a Windows Phone. Now, unfortunately, you have to take this on our word only. It appeared for less than 12 hours via windows phone repair tool, and that is where the files are pulled from. From the previous thread, there were a few of us that tried every which way to find a way to get all this working and pfranceschi just got lucky when he went to restore his phone and was awesome enough to let us know. Like I said, no other 830 rom works for the AT&T 830, so why not try it? if you still feel paranoid about it, you can just use WPRT to take it back to the craptastic at&T shipping firmware.
Pretty sure you and I aren't the only IT professionals in this thread, so if there was an issue, it would have popped up by now.