search

wolpi / prim-ftpd

FTP server app for android
Other
580 stars 78 forks source link

keepass error #19

Open Techwolf opened 9 years ago

Techwolf commented 9 years ago

Took me a while, but I managed to trace down why I could not get keepass (http://keepass.info/) to sync to my tablet via ftp. This ftpd, https://f-droid.org/repository/browse/?fdfilter=ftp&fdid=be.ppareit.swiftp_free , works ok. But not this one, using ngrep, it halts just after getting data from issuing a MDTM comamnd. Keepass throws up a very UN-helpful error message, "Operation not valid due to the current state of the object". Googling show many causes of that error.

wolpi commented 9 years ago

That is a weird issue. For my tests I gave keepass a ftp url with a file name that does not exist yet. Keepass issues a MDTM command for that. As the file does not exist the response in this case is "550 requested action not taken" and keepass shows that error.

I tried to give a "213" response with a date value for 1st january 1970 (to lowest possible date) and with a date value for the current date. In any case I get that weird error from keepass.

Do you know what keepass expects? Or what the other server responses?

Techwolf commented 8 years ago

Sorry for the delay in responding, got buzy with RL. ;-) I'me planning on doing more logging with ngrep to see what is the difference. When I created this issue, it was late and I was short on time.

wolpi commented 8 years ago

the usual problems :) will be interesting to see what comes out here

Techwolf commented 7 years ago

Ok. Sorry for the super long delay, but I had a chance to wireshark the wire to see what was different. Turn out is the response of this server is "213 20170221145203.000" while the response of the working server is "213 20170221145203" As you can see, its the ".000" that is causing the error.

Update: Blah, forgot to say MDTM command.

wolpi commented 7 years ago

Wow, thanks. Let's see how long it takes me to figure out where that .000 comes from 😆