vincenzopalazzo
/
arti
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove ErrorKind::OnionService{Intro,Rend}Failed 

These errors are orthogonal to our actual error kinds.  See
discussion on #736.
This commit is contained in:
Nick Mathewson 2023-06-22 10:37:26 -04:00
parent dd944bc787
commit 1a9e5b8463
2 changed files with 0 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
crates/arti/src/socks.rs
View File

@ -490,12 +490,6 @@ where
#[cfg(feature = "onion-service-client")]
EK::OnionServiceWrongClientAuth => S::HS_WRONG_CLIENT_AUTH,
// TODO HS: Nothing generates the following two errorkinds (yet).
#[cfg(feature = "onion-service-client")]
EK::OnionServiceIntroFailed => S::HS_INTRO_FAILED,
#[cfg(feature = "onion-service-client")]
EK::OnionServiceRendFailed => S::HS_REND_FAILED,
// TODO HS: This is not a perfect correspondence to the error we're
// returning here.
#[cfg(feature = "onion-service-client")]

19
crates/tor-error/src/lib.rs
View File

@ -558,25 +558,6 @@ pub enum ErrorKind {
)]
OnionServiceWrongClientAuth,
/// We tried to connect to an onion service, but could not send an INTRODUCE
/// message.
///
/// This likely means that the onion service is at not at its introduction points
/// any longer; perhaps it is down, or under a DoS attack, or perhaps we do not
/// have up-to-date information about it.
#[cfg(feature = "experimental-api")]
#[display(fmt = "Unable to send introduction to onion service.")]
OnionServiceIntroFailed,
/// We tried to connect to an onion service, but could not successfully get
/// a RENDEZVOUS message from it.
///
/// This likely means that the onion service is not running, or does not
/// want to talk to us, or all of its introduction points are subtly broken.
#[cfg(feature = "experimental-api")]
#[display(fmt = "Unable to rendezvous with onion service.")]
OnionServiceRendFailed,
/// An resolve operation finished with an error.
///
/// Contrary to [`RemoteHostNotFound`](ErrorKind::RemoteHostNotFound),