← Back to team overview

linuxdcpp-team team mailing list archive

[Bug 1436105] [NEW] KEYP checks not in effect with default settings

 

*** This bug is a security vulnerability ***

Private security bug reported:

I posted about this on the hub few days ago, figured it might be
beneficial to do so here as well

The issue is that the "allow untrusted" options as they are now are
honest to a fault, ie. they also disable all KEYP checks when turned on.
The attached patch fixes this. The ConnectionManager and UserConnection
changes are just a micro-optimization not to lookup the user twice if we
already have it.

In theory we could also avoid verifying KEYP twice in such scenario (ie.
just include the checkKeyprint() call to under the added if statement as
well, because if it fails in the first place the execution never reaches
this point, for outgoing connections).

Also, while this is more of a request it would be nice if someone would
come up with a way to reflect the verify_callback error "KeyPrint
mismatch" in HubFrame.

** Affects: dcplusplus
     Importance: Undecided
     Assignee: Crise (markuwil)
         Status: New

** Attachment added: "3599.patch"
   https://bugs.launchpad.net/bugs/1436105/+attachment/4355018/+files/3599.patch

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/1436105

Title:
  KEYP checks not in effect with default settings

Status in DC++:
  New

Bug description:
  I posted about this on the hub few days ago, figured it might be
  beneficial to do so here as well

  The issue is that the "allow untrusted" options as they are now are
  honest to a fault, ie. they also disable all KEYP checks when turned
  on. The attached patch fixes this. The ConnectionManager and
  UserConnection changes are just a micro-optimization not to lookup the
  user twice if we already have it.

  In theory we could also avoid verifying KEYP twice in such scenario
  (ie. just include the checkKeyprint() call to under the added if
  statement as well, because if it fails in the first place the
  execution never reaches this point, for outgoing connections).

  Also, while this is more of a request it would be nice if someone
  would come up with a way to reflect the verify_callback error
  "KeyPrint mismatch" in HubFrame.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/1436105/+subscriptions


Follow ups

References