[Buildroot] servers unavailable

[Buildroot] servers unavailable

[Vlad Zakharov]

Hi Peter and Thomas,

Today (June 13, 2016) many buildroot resources became unavailable. E.g. me and Alexey Brodkin are not able to get response from:
	-?https://git.buildroot.net/
	-?https://buildroot.org/

So inter alia we can't access your git repo to download upstream changes.
Are you working now on this problem??
Could we hope the issue would be solved in near future??

Thank you.

-- 
Best regards,
Vlad Zakharov <vzakhar@synopsys.com>

[Buildroot] servers unavailable

[Yann E. MORIN]

On July 13, 2016 1:18:55 PM GMT+02:00, Vlad Zakharov <Vladislav.Zakharov@synopsys.com> wrote:
>Hi Peter and Thomas,
>
>Today (June 13, 2016) many buildroot resources became unavailable. E.g.
>me and Alexey Brodkin are not able to get response from:
>	-?https://git.buildroot.net/
>	-?https://buildroot.org/
>
>So inter alia we can't access your git repo to download upstream
>changes.
>Are you working now on this problem??
>Could we hope the issue would be solved in near future??
>
>Thank you.
>
>-- 
>Best regards,
>Vlad Zakharov <vzakhar@synopsys.com>
>_______________________________________________
>buildroot mailing list
>buildroot at busybox.net
>http://lists.busybox.net/mailman/listinfo/buildroot

Vlad, All,

The server has been under DDoS attack for ~24h now. It has been taken down voluntarily until the attacks ceases.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160713/375e603a/attachment.html>

[Buildroot] servers unavailable

[Peter Korsgaard]

>>>>> "Vlad" == Vlad Zakharov <Vladislav.Zakharov@synopsys.com> writes:

 > Hi Peter and Thomas,
 > Today (June 13, 2016) many buildroot resources became
 > unavailable. E.g. me and Alexey Brodkin are not able to get response
 > from:
 > 	-?https://git.buildroot.net/
 > 	-?https://buildroot.org/

 > So inter alia we can't access your git repo to download upstream changes.
 > Are you working now on this problem??
 > Could we hope the issue would be solved in near future??

Yes, the server is unfortunately under a DDoS attack. For git, you can
temporarily use the github mirror:

https://github.com/buildroot/buildroot

-- 
Venlig hilsen,
Peter Korsgaard 

[Buildroot] servers unavailable

[Angelo Compagnucci]

Dear All,

2016-07-13 14:23 GMT+02:00 Peter Korsgaard <peter@korsgaard.com>:
>>>>>> "Vlad" == Vlad Zakharov <Vladislav.Zakharov@synopsys.com> writes:
>
>  > Hi Peter and Thomas,
>  > Today (June 13, 2016) many buildroot resources became
>  > unavailable. E.g. me and Alexey Brodkin are not able to get response
>  > from:
>  >      - https://git.buildroot.net/
>  >      - https://buildroot.org/
>
>  > So inter alia we can't access your git repo to download upstream changes.
>  > Are you working now on this problem?
>  > Could we hope the issue would be solved in near future?
>
> Yes, the server is unfortunately under a DDoS attack. For git, you can
> temporarily use the github mirror:
>
> https://github.com/buildroot/buildroot

Since buildroot has a github account, why keep the website outside?!
Github offers github pages with custom domain and protected against
ddos attacks (and many more attack vectors).
And why use a custom git server? We can always switch off pull
requests and issues and keep the patch flow going as it goes now if we
switch to github.

Sincerely, Angelo


>
> --
> Venlig hilsen,
> Peter Korsgaard
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot



-- 
Profile: http://it.linkedin.com/in/compagnucciangelo

[Buildroot] servers unavailable

[Thomas Petazzoni]

Hello,

On Wed, 13 Jul 2016 15:26:45 +0200, Angelo Compagnucci wrote:

> Since buildroot has a github account, why keep the website outside?!
> Github offers github pages with custom domain and protected against
> ddos attacks (and many more attack vectors).
> And why use a custom git server? We can always switch off pull
> requests and issues and keep the patch flow going as it goes now if we
> switch to github.

I am also starting to think we should switch to use github. We could
also use the Github issue tracker, since http://bugs.busybox.net/ is
down as well.

How does one disable pull requests in a Github project? This is clearly
one aspect where I (and I believe most of the core developers) prefer
the mailing list based review than the Web-based review for pull
requests.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] servers unavailable

[James Knight]

Thomas,

On Wed, Jul 13, 2016 at 9:49 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> How does one disable pull requests in a Github project?

You can't. :(

Aside from ignoring or manually closing requests, you can setup
scripts [1] to auto-close pull requests (although, I've never tried
them).

[1]: https://github.com/imjasonh/nopullrequests

[Buildroot] servers unavailable

[Angelo Compagnucci]

Hello,

2016-07-13 16:14 GMT+02:00 James Knight <james.knight@rockwellcollins.com>:
> Thomas,
>
> On Wed, Jul 13, 2016 at 9:49 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> How does one disable pull requests in a Github project?
>
> You can't. :(
>
> Aside from ignoring or manually closing requests, you can setup
> scripts [1] to auto-close pull requests (although, I've never tried
> them).
>
> [1]: https://github.com/imjasonh/nopullrequests

Indeed, and it's really annoynig ...

The only way is closing PR with an autoscript or using github PR
without merge commit.

Actually, I work for a company where we make massive use of github
issuses and PR and I think the systsem works well enough from the
moment github introduced the option to suppress the merge commit.

Sincerely, Angelo


-- 
Profile: http://it.linkedin.com/in/compagnucciangelo