Ticket #34 (new defect)

Opened 7 weeks ago

Last modified 7 weeks ago

obexftp -G kills file although transfer has failed

Reported by: hanno Owned by: zany
Priority: critical Milestone:
Component: obexftp Version:
Keywords: Cc:

Description

This killed a quite important file for me. See below.

Any ideas welcome how I could get my file back (it's on the internal memory of my mobile phone, probably no way to restore it). Marking this as critical.

hanno@noname ~/krisis $ obexftp -B 00:12:D2:2A:4E:19 -G Aufnahmen/Clip000.amr Scanning for (null) ... Found: 00:12:D2:2A:4E:19 Connecting...done Receiving "Aufnahmen/Clip000.amr"... Sending "Aufnahmen"... failed: Aufnahmen/ failed: Aufnahmen/ Sending "Aufnahmen/Clip000.amr"... Sending "Aufnahmen"... done done Disconnecting...done

Change History

Changed 7 weeks ago by zany

  • owner changed from somebody to zany

There are no block-level operations in OBEX. Depending on the brand of your phone there might be other options to read the memory, mostly cracker tools.

I agree that get&delete is not the most safe thing to do, I'll add some more checks. If you want a safety-net and advanced file opertions you should use ObexFS.

Note: See TracTickets for help on using tickets.