arcfour

arcfour-support (AKA RC4-MD5) in winscp would be nice, since this is the fastest cipher I'm aware of. Defintly not the most secure on, but in a private network or over IPsec definitly the fastest one.

Please ask authors of Putty SSH client to include this cipher to their software. I'm using source code of Putty as SSH library.

martin wrote:

Please ask authors of Putty SSH client to include this cipher to their software. I'm using source code of Putty as SSH library.

PuTTY's development version now has support for arcfour128 and arcfour256. There's a new RFC for these 2 rc4 algos and so OpenSSH 4.2 onwards does support arcfour128 and arcfour256. I tested it with my server.

PuTTY is not going to support the original arcfour, ever, from what I understand.

If WinSCP could support arcfour128 and arcfour256, that would be fabulous. :)

Thanks for an excellent program. Your work is very much appreciated. :)

Oil ho Akbar
- Dubya bin Laden :mrgreen:

I'll upgrade once new version of PuTTY is released.

Thanks!

Anonymous wrote:

arcfour-support (AKA RC4-MD5) in winscp would be nice, since this is the fastest cipher I'm aware of. Defintly not the most secure on, but in a private network or over IPsec definitly the fastest one.

afaik, putty already supports arcfour. at least... the version I have CLAIMS it can.

Development snapshot 2005-10-12:r6385

SSH/Encryption options
Arcfour (SSH-2 Only)

I'll admit, I only use it for stuff on my local network (aka trusted), and for everything else I use AES, but on WAN links I find that the bandwidth available is exceeded before the speed of the cipher comes into play. Only on LAN links do I see it become a problem, and thus often force usage of arcfour for rsync-over-ssh or scp.
I'd love to do that with WinSCP too.

afaik, putty already supports arcfour. at least... the version I have CLAIMS it can.

But not a final release, only development snapshot AFAIK.

I might grant that, but the claim that normal arcfour won't be supported has to concern you a little. OpenSSH 3.8 isn't going away anytime soon. Nor is 4.1.

It's not as if most of the users of WinSCP are in any form of control over the ssh servers they're using. And Debian Sarge is still on OpenSSH 3.8. We all know how likely sarge is to go away anytime soon, even if etch is supposed to go stable in 6 months.

Is it too much work to pull the current code, or is it just not available as a normal library? This one seems worth it. I admit I'm not the guy in charge here and as such am in little position to force the issue. Just seems quite worth it to me.

tabrisnet wrote:

Is it too much work to pull the current code, or is it just not available as a normal library?

There's no library. The reason is that PuTTY team makes major changes to code frequently and it takes time to adapt WinSCP code to the changes. I do not want to do that too often. Once per final release is enough for me. But of course, I can change my mind :-)

putty 0.59 is out!!!
Thus we might look forward to WinSCP supporting this in the next couple months?

tabrisnet wrote:

putty 0.59 is out!!!
Thus we might look forward to WinSCP supporting this in the next couple months?

What particular feature are you interested in?

Hello!

I think Tabrisnet means that the new putty version could not be started from WinSCP 3.8.2 - every time an error message `Putty.exe` could not be startet.`

Best regards

My interest is in arcfour support. I do believe that that was what this thread is about.

Hello!

I think Tabrisnet means that the new putty version could not be started from WinSCP 3.8.2 - every time an error message `Putty.exe` could not be startet.`

I have no idea what this person is talking about, but it wasn't what I was referring to.

I think Tabrisnet means that the new putty version could not be started from WinSCP 3.8.2 - every time an error message `Putty.exe` could not be startet.`

It must be some misconfiguration. WinSCP does not care what version of PuTTY you have.

tabrisnet wrote:

My interest is in arcfour support. I do believe that that was what this thread is about.

OK, sorry. I've missed that :(

https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/ssh2-ctr-modes.html
Could you please then add CTR Cipher support too?
Putty 0.59 supports them now[/url]

penna wrote:

https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/ssh2-ctr-modes.html
Could you please then add CTR Cipher support too?
Putty 0.59 supports them now[/url]

Sure, I will include PuTTY 0.59 eventually.

martin wrote:

afaik, putty already supports arcfour. at least... the version I have CLAIMS it can.

But not a final release, only development snapshot AFAIK.

Putty in final release supports arcfour. Would you be so kind and include it in WinSCP?
Thanks.

savec wrote:

martin wrote:

afaik, putty already supports arcfour. at least... the version I have CLAIMS it can.

But not a final release, only development snapshot AFAIK.

Putty in final release supports arcfour. Would you be so kind and include it in WinSCP?
Thanks.

Already done. Please wait for the next major release.

Could you release this change as next major release, please.
I think it's big and wanted enough for it.

I'm coping data over FTP and SSH (WinSCP) and the second has under 50% of the FTP speed, which I hope to improve with a faster encryption.

Thanks,
Martin

PS:
So far I know OpenSSH server support non-encrypted data-transfers (i.e. only encyption for login data) if compiled with the apropriate flag. Then the cipher=none can be selected. This is disabled (at compile time) for security reasons at most (all?) binary releases but could be enabled by compiling the OpenSSH server manually. WinSCP should support this too for the sake of completeness.

martin_s wrote:

Could you release this change as next major release, please.
I think it's big and wanted enough for it.

It will be released within few weeks.

So far I know OpenSSH server support non-encrypted data-transfers (i.e. only encyption for login data) if compiled with the apropriate flag. Then the cipher=none can be selected. This is disabled (at compile time) for security reasons at most (all?) binary releases but could be enabled by compiling the OpenSSH server manually. WinSCP should support this too for the sake of completeness.

It again depends on support in PuTTY.