ICANN is predicting that about 750 accredited registrars will close over the next 12 months due to the over-saturation of the drop-catching market. ICANN VP Cyrus Namazi made the estimate while explaining ICANN's fiscal 2018 budget, which is where the projection originated, at the organization's public meeting in South Africa last week. He said that ICANN ended its fiscal 2017 last week with 2,989 accredited registrars, but that ICANN expects to lose about 250 per quarter starting from October until this time next year. These almost 3,000 registrars belong to about 400 registrar families, he said. By my estimate, roughly two thirds of the registrars are shell accreditations under the ownership of just three companies -- Web.com (Namejet and SnapNames), Pheenix, and TurnCommerce (DropCatch.com). These companies lay out millions of dollars on accreditation fees in order to game ICANN rules and get more connections to registries -- mainly Verisign's .com. More connections gives them a

Что такое реестр организаторов распространения информации и много ли в нем мессенджеров кроме Telegram. На эти и другие вопросы "РГ" ответил замруководителя Роскомнадзора Олег Иванов

Просмотр статистики Telegram-канала "ЗаТелеком" - @zatelecom. Подписчики, прирост, просмотры за день, репосты и другая аналитика на сайте Telegram Analytics.

A vulnerability in certain commands of Cisco Elastic Services Controller could allow an authenticated, remote attacker to elevate privileges to root and run dangerous commands on the server.

The vulnerability occurs because a &quo;tomcat&quo; user on the system can run certain shell commands, allowing the user to overwrite any file on the filesystem and elevate privileges to root. An exploit could allow an authenticated, remote attacker to elevate privileges and run dangerous commands on the server.

Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. 


This advisory is available at the following link:
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20170705-esc1