[PATCH] wget: allow HTTP 307/308 redirects

This resolves failures like wget: server returned error: HTTP/1.1 307 Temporary Redirect Signed-off-by: Jeremy Lin --- networking/wget.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/networking/wget.c b/networking/wget.c index 3edc5f870..6a9604421 100644 --- a/networking/wget.c +++

[PATCH] login: permit change expired password

Add support in login command to change password in case it is expired: --- --- a/loginutils/login.c2021-03-22 01:34:05.628165667 +0100 +++ b/loginutils/login.c2021-03-22 01:36:22.719612349 +0100 @@ -434,6 +434,9 @@ } /* check that the account is healthy */

RE: CVE-2021-28831

I got a response on https://github.com/docker-library/busybox/issues/101: - We strive to follow upstream releases and so don't really backport patches. Once there is a release available on https://busybox.net/, we'll publish a new image. So, could a new release of BusyBox please be published?

RE: CVE-2021-28831

Thanks again for the quick reply. I don't know why I assumed the maintainers of BusyBox would also maintain the docker images published. I filed https://github.com/docker-library/busybox/issues/101 for the BusyBox docker image. Not sure if this will require a new release to be published in

Re: CVE-2021-28831

> "Mousaw," == Mousaw, Tim writes: > Thanks for the quick replies. > So, once this was merged, did the 1.32.1 image tag of the BusyBox > docker image get rebuilt with it? From what I can tell, this is the > image tag that gets pulled when the "latest" tag is used. Sorry, I have no idea

RE: CVE-2021-28831

Thanks for the quick replies. So, once this was merged, did the 1.32.1 image tag of the BusyBox docker image get rebuilt with it? From what I can tell, this is the image tag that gets pulled when the "latest" tag is used. Is there any way I can validate that the latest image has the fix? I'm

Re: CVE-2021-28831

> "Christophe" == Christophe Leroy writes: Hi, > As far as I can see, that commit is in 1_32_stable > See https://git.busybox.net/busybox/commit/?h=1_32_stable But strangely enough not in 1_33_stable. -- Bye, Peter Korsgaard ___ busybox

Re: CVE-2021-28831

Hi Tim, Le 28/04/2021 à 14:30, Mousaw, Tim a écrit : I’m not sure if this is the correct place to make this inquiry, so if this is the wrong place, I apologize in advance. I am trying to understand how a particular commit will make it into an official release of BusyBox. The commit

CVE-2021-28831

I'm not sure if this is the correct place to make this inquiry, so if this is the wrong place, I apologize in advance. I am trying to understand how a particular commit will make it into an official release of BusyBox. The commit

Re: [PATCH 0/8] vi: patch set 5

Applied, thank you On Sun, Apr 25, 2021 at 12:51 PM Ron Yorston wrote: > > I've finished working through my vi book so this is the last set > of patches for now. > > Enjoy, > > Ron > ___ > busybox mailing list > busybox@busybox.net >