<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">When I run the file command on the file that is sitting in the drop-offs folder with the claim ID in question, it says:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">raw G3 data, byte-padded<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">When looking at the zendto.log file at the time the file was uploaded, it looks normal with no hint of anything wrong. Here’s what it says with the email addresses obfiscated:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">2018-10-10 21:13:19 108.85.190.41 [ZendTo]: Info: successfully delivered notification email to RECIPIENT@EMAIL.ADDRESS for claimID q3j8nGdByjV8MwSq<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">2018-10-10 21:13:19 108.85.190.41 [ZendTo]: Info: new encrypted dropoff q3j8nGdByjV8MwSq of 1 file created for external user SENDER
<a href="mailto:SENDER@EMAIL.ADDRESS">SENDER@EMAIL.ADDRESS</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">A command line utility would be fantastic!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-MIke<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> ZendTo <zendto-bounces@zend.to>
<b>On Behalf Of </b>Jules Field via ZendTo<br>
<b>Sent:</b> Thursday, October 18, 2018 9:32 AM<br>
<b>To:</b> MICHAEL R MASSE via ZendTo <zendto@zend.to><br>
<b>Cc:</b> Jules Field <Jules@Zend.To><br>
<b>Subject:</b> Re: [ZendTo] manually retrieve an encrypted file?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Mike,<br>
<br>
I have seen 1 other instance of this. It appears to be caused by the encryption process failing. Take a look in the Apache logs and let me know what error message you see in the error_log. I need to improve the checking of values read from the header I add
to the encrypted file, to ensure that things like the hashing and encryption algorithm names are valid before I try to use them.<br>
<br>
I haven't managed to reproduce this problem myself, but I'm pretty sure this is what is happening. By the time I come to decrypt the data, if it's damaged by that point then I can't retrieve it, but I can flag the error a lot better than currently!<br>
<br>
One thing to try: given the ClaimID look in the /var/zendto/dropoffs directory for the files that belong to that ClaimID. The filenames will be random, and each file should be a bit longer than the original version uploaded. See if you can work out which one
is the problem file. Is that file actually encrypted *at all*? The "file" command will help you here. Do a "file *" in the relevant dropoff directory, and it *should* say something like they are all just "data". If it identifies one as a Word document, zip
file, PDF file anything like that, then the file didn't get encrypted for some reason.<br>
<br>
If that is the case, please can you look back through your zendto.log file (either in /var/zendto or /var/log/zendto) to see if anything odd happened when the drop-off was originally uploaded.<br>
<br>
Please can you let me know what you find?<br>
<br>
Also, I am going to write you a command-line utility so retrieve the files from a drop-off given the claim ID and the passphrase. It will probably just write all the files with their original names into the current directory. Even for unencrypted drop-offs,
it would still be a useful tool. I'll make it prompt for the passphrase if one is needed (i.e. if the drop-off is encrypted).<br>
<br>
Cheers,<br>
Jules.<span style="font-size:12.0pt"><o:p></o:p></span></p>
<div>
<p class="MsoNormal">On 12/10/2018 15:28, MICHAEL R MASSE via ZendTo wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Is there a way as the administrator of the system hosting my Zendto service that I can decrypt a file that’s been uploaded if I have the passphrase? I have direct access to the sqlite database to get the key as well, but I’m not sure what
to do with either.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I’m running 5.15-1 and the system works fine except one single user is trying to receive a file from someone outside of the system and when they try to download this specific file after typing in the passphrase they just get a http 500
error. The sender does not receive any errors when uploading. It actually doesn’t matter if the recipient types a correct passphrase or not, they always get an http 500 error on this particular file. As an administrator if I try to download the file
and regardless of the passphrase I enter (correct or not) I get an http 500 error as well. This does not happen for anyone else for any other files in the system sent before or after. Also, for every other file on the system, if an incorrect passphrase
is used, the system says it’s incorrect like it should instead of giving an http 500 error. I told the person to have their sender send the file again, and it again throws an http 500 error. It’s only a 2mb file so there’s nothing weird about it. After
telling them to upload the file twice and having it fail I’d like to just decrypt the file that’s there and manually give it to the recipient since he’s local, and then worry about troubleshooting the problem later.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">-Mike<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>ZendTo mailing list<o:p></o:p></pre>
<pre><a href="mailto:ZendTo@zend.to">ZendTo@zend.to</a><o:p></o:p></pre>
<pre><a href="http://jul.es/mailman/listinfo/zendto">http://jul.es/mailman/listinfo/zendto</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
<br>
<o:p></o:p></span></p>
<pre>Jules<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-- <o:p></o:p></pre>
<pre>Julian Field MEng CEng CITP MBCS MIEEE MACM<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>'What happened in the past that was painful, has a great deal to<o:p></o:p></pre>
<pre> do with what we are today.' - William Glasser<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><a href="http://www.Zend.To">www.Zend.To</a><o:p></o:p></pre>
<pre>Twitter: @JulesFM<o:p></o:p></pre>
</div>
</body>
</html>