patchWeeChat - Patches: patch #8020, [PATCH] Implement DH-AES SASL...

 
 

patch #8020: [PATCH] Implement DH-AES SASL encryption method

Submitter:  None
Submitted:  Tue 16 Apr 2013 07:14:05 AM UTC
 
Category:  irc plugin Priority:  5 - Normal
Status:  Done Privacy:  Public
Assigned to:  flashcode Originator Email:  -email is unavailable-
Open/Closed:  Closed IRC nick:  Elizacat
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

Tue 16 Apr 2013 07:14:05 AM UTC, comment #1: 

This item has been reassigned from the project WeeChat bugs tracker to your tracker.

The original report is still available at bugs #38749

Following are the information included in the original report:

[field #0]                  Item ID: 38749
[field #1]                 Group ID: 4783
[field #2]              Open/Closed: Open
[field #3]                 Severity: 3 - Normal
[field #4]                  Privacy: Public
[field #7]                         : Unknown bugs Field Display Type
[field #8]                         : Unknown bugs Field Display Type
[field #9]                 Category: irc plugin
[field #10]             Submitted by: None
[field #11]              Assigned to: None
[field #12]             Submitted on: mar. 16 avril 2013 08:51:00 CEST
[field #13]                  Summary: [PATCH] Implement DH-AES SASL encryption method
[field #14]      Original Submission: Hello,

I have implemented DH-AES (one of the intended successors to DH-BLOWFISH) support in WeeChat. It has been added to Atheme and tested with such.

DH-BLOWFISH is no longer recommended, as Blowfish suffers from certain classes of weak keys and is not exactly easy to mitigate with DH negotiation (it would require verifying that the key is not a weak key and generating a new random value if it is). The original author of Blowfish, Bruce Schneier, also advises against using Blowfish and suggests using a different cipher.

As its initial DH parameters parsing is the same as DH-BLOWFISH, I have separated that into a function to be used as common code in DH-BLOWFISH and DH-AES. However, the padding scheme (16 vs 8 bytes), data encrypted (both username and password rather than just the password), packing scheme (IV is placed where the username used to be, since that is sent encrypted), and obviously cipher (AES-{128,192,256}-CBC), are all totally different.

Services-side reference implementation is at https://github.com/atheme/atheme/blob/master/modules/saslserv/dh-aes.c />[field #16]               Item Group: irc protocol
[field #17]                   Status: None
[field #18]        Component Version: None
[field #19]         Operating System: None
[field #20]          Reproducibility: None
[field #21]               Size (loc): None
[field #22]            Fixed Release: None
[field #23]          Planned Release: None
[field #24]                   Effort: 0.00
[field #28]                 Priority: 5 - Normal
[field #31]         Percent Complete: 0%
[field #33]                  Release: other
[field #35]          Originator Name: Elizabeth Myers
[field #36]         Originator Email: elizabeth@interlinked.me
[field #38]                 IRC nick: Elizacat
[field #58]     Custom Select Box #1: None
[field #59]     Custom Select Box #2: None
[field #60]     Custom Select Box #3: None
[field #61]     Custom Select Box #4: None
[field #62]     Custom Select Box #5: None
[field #63]     Custom Select Box #6: None
[field #64]     Custom Select Box #7: None
[field #65]     Custom Select Box #8: None
[field #66]     Custom Select Box #9: None
[field #67]    Custom Select Box #10: None

Sebastien Helleu <flashcode>
Project Administrator
Tue 16 Apr 2013 07:14:05 AM UTC, original submission:  

Hello,

I have implemented DH-AES (one of the intended successors to DH-BLOWFISH) support in WeeChat. It has been added to Atheme and tested with such.

DH-BLOWFISH is no longer recommended, as Blowfish suffers from certain classes of weak keys and is not exactly easy to mitigate with DH negotiation (it would require verifying that the key is not a weak key and generating a new random value if it is). The original author of Blowfish, Bruce Schneier, also advises against using Blowfish and suggests using a different cipher.

As its initial DH parameters parsing is the same as DH-BLOWFISH, I have separated that into a function to be used as common code in DH-BLOWFISH and DH-AES. However, the padding scheme (16 vs 8 bytes), data encrypted (both username and password rather than just the password), packing scheme (IV is placed where the username used to be, since that is sent encrypted), and obviously cipher (AES-{128,192,256}-CBC), are all totally different.

Services-side reference implementation is at https://github.com/atheme/atheme/blob/master/modules/saslserv/dh-aes.c

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #27889:  0001-Implement-DH-AES-encrypted-password-scheme.patch added by None (16KiB - text/x-patch - Patch implementing DH-AES support.)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by flashcode (Updated the item)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

     

     

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-05-20 flashcode Open/ClosedOpen Closed
    2013-05-01 flashcode CategoryNone irc plugin
        StatusNone Done
        Assigned toNone flashcode
        IRC nick Elizacat
    2013-04-16 flashcode Reassign itemWeeChat, bug #38749 WeeChat, patch #8020

    Back to the top


    Powered by Savane 3.9