Bug 324557 - sending a file with 0 bytes gives always "Failed"as status
Summary: sending a file with 0 bytes gives always "Failed"as status
Status: RESOLVED INTENTIONAL
Alias: None
Product: konversation
Classification: Applications
Component: dcc (show other bugs)
Version: 1.4
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Bernd Buschinski
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-05 17:43 UTC by Toralf Förster
Modified: 2013-09-05 18:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Förster 2013-09-05 17:43:17 UTC 
Well, I'm might be pedantic (file transfer itself works fine for file w/ bytes in it) but nevertheless ...


Reproducible: Always
Comment 1 Bernd Buschinski 2013-09-05 18:09:34 UTC 
Well, is there any good reason so send 0 byte files?
I would just consider it as spam, therefor the failed is intented.

If you have a VERY good reason for sending 0byte files, feel free to reopen the bug.
Comment 2 Toralf Förster 2013-09-05 18:26:33 UTC 
(In reply to comment #1)
> Well, is there any good reason so send 0 byte files?
> I would just consider it as spam, therefor the failed is intented.
> 
> If you have a VERY good reason for sending 0byte files, feel free to reopen
> the bug.

Probbaly you're right- otoh it could be only the file *name* which could be interesting enough.

Maybe either b/c it contains character/s which lets act software in an somehow interesting behaviour or b/c of (ok, much more obscure reason) steganographic goals.
 
Well - not strong enough, or ?