Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(61)

Issue 6404046: code review 6404046: go.crypto/ssh: avoid recover() when handling invalid channel ids (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
11 years, 9 months ago by dave
Modified:
11 years, 9 months ago
Reviewers:
CC:
agl1, gpaul, golang-dev
Visibility:
Public.

Description

go.crypto/ssh: avoid recover() when handling invalid channel ids This proposal removes the use of recover() to catch invalid channel ids sent from the remote side. The recover() unfortuntaly makes debugging harder as it obscures other panic causes. Another source of panic()s exists inside marshal.go, which will be handled with in a later CL.

Patch Set 1 #

Patch Set 2 : code review 6404046: go.crypto/ssh: check remote id is a valid channel #

Patch Set 3 : diff -r 671a975c2b5f https://code.google.com/p/go.crypto #

Patch Set 4 : diff -r 671a975c2b5f https://code.google.com/p/go.crypto #

Patch Set 5 : diff -r 671a975c2b5f https://code.google.com/p/go.crypto #

Patch Set 6 : diff -r 8738a06cfeef https://code.google.com/p/go.crypto #

Unified diffs Side-by-side diffs Delta from patch set Stats (+52 lines, -19 lines) Patch
M ssh/client.go View 1 2 3 4 5 chunks +52 lines, -19 lines 0 comments Download

Messages

Total messages: 4
dave_cheney.net
Hello agl@golang.org (cc: golang-dev@googlegroups.com), I'd like you to review this change to https://code.google.com/p/go.crypto
11 years, 9 months ago (2012-07-16 03:47:45 UTC) #1
gpaul
LGTM. This recover as has bitten me before.
11 years, 9 months ago (2012-07-16 07:32:26 UTC) #2
agl1
LGTM
11 years, 9 months ago (2012-07-16 13:30:13 UTC) #3
dave_cheney.net
11 years, 9 months ago (2012-07-17 00:59:28 UTC) #4
*** Submitted as
http://code.google.com/p/go/source/detail?r=b1b686ab459a&repo=crypto ***

go.crypto/ssh: avoid recover() when handling invalid channel ids

This proposal removes the use of recover() to catch
invalid channel ids sent from the remote side. The
recover() unfortuntaly makes debugging harder as it
obscures other panic causes.

Another source of panic()s exists inside marshal.go,
which will be handled with in a later CL.

R=agl, gustav.paul
CC=golang-dev
http://codereview.appspot.com/6404046
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b