Forum: Ruby net/ssh: corrupted mac detected

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Fe57662c550fb3cce44c398ddf2dd706?d=identicon&s=25 itsme213 (Guest)
on 2006-01-05 05:19
(Received via mailing list)
Never did quite get past this error when using net/ssh. Any suggestions?

[I did have the ISP upgrade their ssh some time ago, but they also
migrated
servers so I can't be sure].

Any ideas? Thanks!

(this is from within a Net::SSH.start, when executing an unzip on the
remote
machine ...)

unzip generated_site.zip -d generated_site...
rake aborted!
corrupted mac detected
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/transport/packet-stream.rb:182:in
`get'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/transport/packet-stream.rb:147:in
`synchron
ize'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/transport/packet-stream.rb:147:in
`get'
c:/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needle/lifecycle/proxy.rb:60:in
`__send__'
c:/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needle/lifecycle/proxy.rb:60:in
`method_missing'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/transport/session.rb:245:in
`wait_for_messa
ge'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/transport/session.rb:240:in
`loop'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/transport/session.rb:240:in
`wait_for_messa
ge'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/connection/driver.rb:148:in
`process'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/service/shell/shell.rb:124:in
`consume_conn
ection'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/service/shell/shell.rb:68:in
`stdout?'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/service/shell/sync.rb:65:in
`send_command'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/service/shell/sync.rb:63:in
`loop'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh/service/shell/sync.rb:63:in
`send_command'
C:/des/desktop/methods/cfr/source/rakefile.rb:192:in `ssh_cmd_echo'
C:/des/desktop/methods/cfr/source/rakefile.rb:206
C:/des/desktop/methods/cfr/source/rakefile.rb:202:in `initialize'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh.rb:47:in `new'
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.5/lib/net/ssh.rb:47:in
`start'
C:/des/desktop/methods/cfr/source/rakefile.rb:202
C:/des/desktop/methods/cfr/source/rakefile.rb:200:in `call'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.6.99.2/lib/rake.rb:227:in
`execute'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.6.99.2/lib/rake.rb:227:in `each'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.6.99.2/lib/rake.rb:227:in
`execute'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.6.99.2/lib/rake.rb:197:in `invoke'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.6.99.2/lib/rake.rb:190:in
`synchronize'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.6.99.2/lib/rake.rb:190:in `invoke'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.6.99.2/lib/rake.rb:1673:in `run'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.6.99.2/lib/rake.rb:1673:in `each'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.6.99.2/lib/rake.rb:1673:in `run'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.6.99.2/bin/rake:7
c:/ruby/bin/rake:18:in `load'
c:/ruby/bin/rake:18
992fe8c19bbbc27f2b562a9f96efc03d?d=identicon&s=25 Jamis Buck (Guest)
on 2006-01-05 05:31
(Received via mailing list)
A corrupted mac is very often caused by a bug in Net::SSH. Is this a
script you can send me, that I can use to try to duplicate the error?

- Jamis
82e62c756d89bc6fa0a0a2d7f2b1e617?d=identicon&s=25 Ross Bamford (Guest)
on 2006-01-05 10:05
(Received via mailing list)
On Thu, 05 Jan 2006 04:13:02 -0000, itsme213 <itsme213@hotmail.com>
wrote:

> machine ...)
>
> unzip generated_site.zip -d generated_site...
> rake aborted!
> corrupted mac detected

[... snip ...]

Either you've encountered a Bad Apple (sorry), or something else is
wrong.

This probably doesn't help, but I do recall something about a bug around
this, but I can't remember the specifics. I'd still do a bit of a
security
check to make sure no-one's sitting between and injecting stuff, but it
seems about right. The thing I'm referring to was 'Corrupted MAC on
input', and Google seems to have some hits.

Sorry if that doesn't help.
This topic is locked and can not be replied to.