Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69316 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3620 invoked from network); 24 Sep 2013 14:13:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Sep 2013 14:13:34 -0000 Authentication-Results: pb1.pair.com header.from=william.a.bartlett@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=william.a.bartlett@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.176 as permitted sender) X-PHP-List-Original-Sender: william.a.bartlett@gmail.com X-Host-Fingerprint: 209.85.214.176 mail-ob0-f176.google.com Received: from [209.85.214.176] ([209.85.214.176:57120] helo=mail-ob0-f176.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 45/30-01825-D0E91425 for ; Tue, 24 Sep 2013 10:13:33 -0400 Received: by mail-ob0-f176.google.com with SMTP id uy5so4975714obc.35 for ; Tue, 24 Sep 2013 07:13:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=v98hI6LrNsAaG5uwkVtx9NOkNQZQl51Nde9B5ds0AI8=; b=u+CSHj5Mm8Fg86QCHhu8Eb+zoEMs0/YXaRPiaVxVGHbG1v4sUDVD38FVbKaPSvQ1GY jkFzxkpFY/8u97Ap3xiaGkTnNxyAOskMLGRAW4++dX9We5H5nQ2L6DFtmpXyBWYnMU4O H/RQiLrktQj8NGEj5wjzp5Ip26QkxxKh+dVXDQpkmESRLakhEBXUzvBTC76d44+GLmTC AtbALahAY1y9jRAZU3H6L6cTWlrZ1RfsBNWYNQder5Lsj8vtvpClrOPRH5KQQCf1s5k6 sCk6/wRK8l6oJa2ObGj5HA5CXRu+9x4GYo8hUnQZZYFIuZIFpuziXY/qOWW1sCzms9Wy xdBw== MIME-Version: 1.0 X-Received: by 10.182.242.112 with SMTP id wp16mr268072obc.85.1380032010868; Tue, 24 Sep 2013 07:13:30 -0700 (PDT) Received: by 10.60.34.164 with HTTP; Tue, 24 Sep 2013 07:13:30 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Sep 2013 10:13:30 -0400 Message-ID: To: Pierre Joye Cc: Yasuo Ohgaki , PHP internals Content-Type: multipart/alternative; boundary=e89a8ff1c9c0c960c304e721bd8a Subject: Re: [PHP-DEV] [VOTE] Change crypt() behavior w/o salt From: william.a.bartlett@gmail.com (William Bartlett) --e89a8ff1c9c0c960c304e721bd8a Content-Type: text/plain; charset=ISO-8859-1 I think BC (like requiring salt) are unnecessary given that password_* functions already exist with salt enabled by default. But an E_NOTICE isn't a bad idea. -- William Bartlett College of Engineering | Cornell University '14 240-432-5189 On Mon, Sep 23, 2013 at 10:47 PM, Pierre Joye wrote: > On Sep 23, 2013 6:42 PM, "Yasuo Ohgaki" wrote: > > > > Hi all, > > > > It's been a whole from the discussion. > > I setup vote for RFC: Change crypt() behavior w/o salt. > > > > https://wiki.php.net/rfc/crypt_function_salt > > > > If I missed something, please let me know. > > Thank you for pushing this RFC so far! > > One point to keep in mind: BC breaks disqualify an option for any 5.x > releases. Warning and the likes are not BC breaks per se. > > Cheers, > Pierre > --e89a8ff1c9c0c960c304e721bd8a--