Wednesday, February 01, 2017
“I am sorry, we cannot allow you to view this innocuous text file. For reasons.”
I found a bug in “Project: Sippy-Cup”. The nature of the bug is not important, but QA and I were able to reproduce locally the issue seen in production. So I ask QA to send a copy of the SIPp script (an XML file) so I could fix the issue.
- QA <XXXXXXXXXXXXXXXXXXXXXXX>
- Sean Conner <XXXXXXXXXXXXXXXXXXX>
- Sipp command and xml for CP-209
- Wednesday, February 1, 2017 4:27 PM
Access to attachments has been blocked. Blocked attachments: sipptestCp209.xml.
Well then … okay. I have QA resend it, this time renamed to sipptestCp209.txt. This time it shows up. I save it. Then …
GenericUnixPrompt> more sipptestCp209.txt This attachment was removed because it contains data that could pose a security risk. GenericUnixPrmopt>
Seriously? Just to convince myself it wasn't Mac OS-X's version of more that was doing the conversion:
GenericUnixPrompt> cat sipptestCp209.txt This attachment was removed because it contains data that could pose a security risk. GenericUnixPrmopt>
So it's our overly paranoid email system's fault.