Bug#693460: Bug#694091: bcrypt: Tries to load whole file into memory regardless of the size

2012-11-30 Thread Michael Stapelberg
Hi Kevin, Kevin Coyner writes: > I've got a package complete but just want to tidy it up and test it a > little more. Thanks. Please keep in mind that packages should have minimal differences to their previous version if we want to get them into wheezy. The more changes you do, the smaller the c

Bug#693460: Bug#694091: bcrypt: Tries to load whole file into memory regardless of the size

2012-11-30 Thread Kevin Coyner
I've got a package complete but just want to tidy it up and test it a little more. Thanks. Kevin On Fri, Nov 30, 2012 at 4:37 AM, Michael Stapelberg wrote: > Hi Kevin, > > Michael Stapelberg writes: > >> I'm on the road right now, but would be happy to upload a new version > later > >> tonight

Bug#693460: Bug#694091: bcrypt: Tries to load whole file into memory regardless of the size

2012-11-30 Thread Michael Stapelberg
Hi Kevin, Michael Stapelberg writes: >> I'm on the road right now, but would be happy to upload a new version later >> tonight or early tomorrow morning. > Thanks. Please let us know when you are done. Any news on that? If you need any help, please tell us. -- Best regards, Michael -- To UN

Bug#693460: Bug#694091: bcrypt: Tries to load whole file into memory regardless of the size

2012-11-26 Thread Michael Stapelberg
Hi Kevin, Kevin Coyner writes: > I'm on the road right now, but would be happy to upload a new version later > tonight or early tomorrow morning. Thanks. Please let us know when you are done. In the meantime, new upstream has merged the fix and also improved error messages and fixed a memory lea

Bug#693460: Bug#694091: bcrypt: Tries to load whole file into memory regardless of the size

2012-11-25 Thread Kevin Coyner
-- Kevin Coyner. GnuPG key: 2048R/C85D8F71 On Nov 25, 2012 12:33 PM, "Michael Stapelberg" wrote: > > > Your patch does seem to work on fixing most of the issues that I had > > identified, and you have tested it thoroughly (I haven't run the tests > > myself, though), so I guess it would be alrigh