С
А что вы называете "падали"?
Size: a a a
2019 October 23
С
И скорее надо спрашивать, не падали ли чаще/сильнее, чем обычно. А то может они каждый день падают массово у кого-нибудь.
A
Aws говорят досили хорошо
k
У меня на одном кламав повесил систему повесив свой сокет, +10впс мускульный сокет повесил. Все в разных сетях, разные конфигурации. Возможно просто совпадение. Но все произошло в течении суток
AM
привет, ковыряем такую задачку по hashicorp vault:
"узнать какие сущности (username/approle/ldap и тд) имеют доступ для указаного пути" наподобие команды для токенов "vault token capabilities"
может кто решал уже подобную задачку? свой велосипед городить не очень хочется
"узнать какие сущности (username/approle/ldap и тд) имеют доступ для указаного пути" наподобие команды для токенов "vault token capabilities"
может кто решал уже подобную задачку? свой велосипед городить не очень хочется
С
У меня велосипеда нет, но я примерно представляю, как его сделать )
С
Ещё в goldfish(https://github.com/Caiyeon/goldfish) есть что-то про Dependencies. Можно их код позаимствовать попробовать.
2019 October 24
N
Можно было кстати заранее спросить.
GG
Amazon Route 53[RESOLVED]
5:44 PM PDT On October 22, 2019, we detected and then mitigated a DDoS (Distributed Denial of Service) attack against Route 53. Due to the way that DNS queries are processed, this attack was first experienced by many other DNS server operators as the queries made their way through DNS resolvers on the internet to Route 53. The attack targeted specific DNS names and paths, notably those used to access the global names for S3 buckets. Because this attack was widely distributed, a small number of ISPs operating affected DNS resolvers implemented mitigation strategies of their own in an attempt to control the traffic. This is causing DNS lookups through these resolvers for a small number of AWS names to fail. We are doing our best to identify and contact these operators, as quickly as possible, and working with them to enhance their mitigations so that they do not cause impact to valid requests. If you are experiencing issues, please contact us so we can work with your operator to help resolve.
https://status.aws.amazon.com
#route53
5:44 PM PDT On October 22, 2019, we detected and then mitigated a DDoS (Distributed Denial of Service) attack against Route 53. Due to the way that DNS queries are processed, this attack was first experienced by many other DNS server operators as the queries made their way through DNS resolvers on the internet to Route 53. The attack targeted specific DNS names and paths, notably those used to access the global names for S3 buckets. Because this attack was widely distributed, a small number of ISPs operating affected DNS resolvers implemented mitigation strategies of their own in an attempt to control the traffic. This is causing DNS lookups through these resolvers for a small number of AWS names to fail. We are doing our best to identify and contact these operators, as quickly as possible, and working with them to enhance their mitigations so that they do not cause impact to valid requests. If you are experiencing issues, please contact us so we can work with your operator to help resolve.
https://status.aws.amazon.com
#route53
GG
@x4380 вот - не оно ли?
T
@x4380 вот - не оно ли?
Похоже да
2019 October 28
ST
Привет секурити
MB
так откатили же уже.. на пока..
2019 October 29
rd
так откатили же уже.. на пока..
Как бучу подняли, а так бы и сидели с телеметрией =)
MM
У нас тут тож самое
2019 October 30
