{"id":96270,"date":"2020-10-10T01:42:13","date_gmt":"2020-10-09T23:42:13","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-ntp-serverov-ntpsec-1-2-0-i-shrony-4-0-s-podderzhkoj-zashhishhyonnogo-protokola-nts"},"modified":"2020-10-10T01:42:13","modified_gmt":"2020-10-09T23:42:13","slug":"vypusk-ntp-serverov-ntpsec-1-2-0-i-shrony-4-0-s-podderzhkoj-zashhishhyonnogo-protokola-nts","status":"publish","type":"post","link":"https:\/\/prohoster.info\/pt\/blog\/news\/vypusk-ntp-serverov-ntpsec-1-2-0-i-shrony-4-0-s-podderzhkoj-zashhishhyonnogo-protokola-nts","title":{"rendered":"Lan\u00e7amento dos servidores NTP NTPsec 1.2.0 e Chrony 4.0 com suporte ao protocolo protegido NTS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

O Comit\u00ea IETF (Internet Engineering Task Force), respons\u00e1vel pelo desenvolvimento de protocolos e arquitetura da internet, concluiu<\/a><\/noindex> a forma\u00e7\u00e3o do RFC para o protocolo NTS (Network Time Security) e publicou a especifica\u00e7\u00e3o relacionada sob o identificador RFC 8915<\/a><\/noindex>. O RFC recebeu o status de \u00abPadr\u00e3o Proposto\u00bb, ap\u00f3s o qual come\u00e7ar\u00e1 o trabalho para conceder ao RFC o status de Padr\u00e3o Draft, o que significa, na pr\u00e1tica, a completa estabiliza\u00e7\u00e3o do protocolo e a considera\u00e7\u00e3o de todos os coment\u00e1rios recebidos. <\/p>\n

A padroniza\u00e7\u00e3o do NTS \u00e9 um passo importante para aumentar a seguran\u00e7a dos servi\u00e7os de sincroniza\u00e7\u00e3o de tempo preciso e proteger os usu\u00e1rios contra ataques que imitam servidores NTP aos quais o cliente se conecta. As manipula\u00e7\u00f5es maliciosas relacionadas \u00e0 configura\u00e7\u00e3o de um tempo incorreto podem ser usadas para comprometer a seguran\u00e7a de outros protocolos que dependem do tempo, como o TLS. Por exemplo, a altera\u00e7\u00e3o do tempo pode levar a uma interpreta\u00e7\u00e3o errada dos dados relacionados \u00e0 validade dos certificados TLS. At\u00e9 agora, o NTP e a criptografia sim\u00e9trica das comunica\u00e7\u00f5es n\u00e3o garantiam que o cliente estivesse interagindo com o servidor NTP pretendido, e a autentica\u00e7\u00e3o baseada em chaves n\u00e3o se tornou comum devido \u00e0 sua complexidade de configura\u00e7\u00e3o.<\/p>\n

O NTS utiliza elementos da infraestrutura de chaves p\u00fablicas (PKI) e permite o uso de TLS e criptografia autenticada AEAD (Authenticated Encryption with Associated Data) para a prote\u00e7\u00e3o criptogr\u00e1fica da intera\u00e7\u00e3o entre cliente e servidor pelo protocolo NTP (Network Time Protocol). O NTS inclui dois protocolos distintos: NTS-KE (NTS Key Establishment para o tratamento da autentica\u00e7\u00e3o inicial e negocia\u00e7\u00e3o de chaves acima do TLS) e NTS-EF (NTS Extension Fields, respons\u00e1vel pela criptografia e autentica\u00e7\u00e3o da sess\u00e3o de sincroniza\u00e7\u00e3o de tempo). O NTS adiciona v\u00e1rios campos estendidos aos pacotes NTP e mant\u00e9m toda a informa\u00e7\u00e3o de estado apenas no lado do cliente, utilizando um mecanismo de transmiss\u00e3o de cookies. O protocolo NTS utiliza a porta de rede 4460 para o manuseio das conex\u00f5es.<\/p>\n

\"Lan\u00e7amento<\/a><\/noindex><\/center><\/p>\n

As primeiras implementa\u00e7\u00f5es do NTS padronizado foram propostas nas edi\u00e7\u00f5es publicadas recentemente NTPsec 1.2.0<\/a><\/noindex> e Chrony 4.0<\/a><\/noindex>. Chrony<\/a><\/noindex> fornece uma implementa\u00e7\u00e3o independente do cliente e servidor NTP, que \u00e9 usada para sincronizar o tempo preciso em v\u00e1rias distribui\u00e7\u00f5es Linux, incluindo Fedora, Ubuntu, SUSE\/openSUSE e RHEL\/CentOS. NTPsec<\/a><\/noindex> est\u00e1 em desenvolvimento<\/a><\/noindex> sob a lideran\u00e7a de Eric S. Raymond, e \u00e9 um fork da implementa\u00e7\u00e3o de refer\u00eancia do protocolo NTPv4 (NTP Classic 4.3.34), focado na reformula\u00e7\u00e3o da base de c\u00f3digo para aumentar a seguran\u00e7a (inclui limpeza de c\u00f3digo obsoleto, m\u00e9todos de preven\u00e7\u00e3o de ataques e fun\u00e7\u00f5es seguras para trabalho com mem\u00f3ria e strings).<\/p>\n

<\/a><\/noindex><\/p>\n

Fonte: opennet.ru<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041a\u043e\u043c\u0438\u0442\u0435\u0442 IETF (Internet Engineering Task Force), \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0449\u0438\u0439\u0441\u044f \u0440\u0430\u0437\u0432\u0438\u0442\u0438\u0435\u043c \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u0438 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u044b \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0430, \u0437\u0430\u0432\u0435\u0440\u0448\u0438\u043b \u0444\u043e\u0440\u043c\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 RFC \u0434\u043b\u044f \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 NTS (Network Time Security) \u0438 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043b \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u0443\u044e \u0441 \u043d\u0438\u043c \u0441\u043f\u0435\u0446\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044e \u043f\u043e\u0434 \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440\u043e\u043c RFC 8915. RFC \u043f\u043e\u043b\u0443\u0447\u0438\u043b \u0441\u0442\u0430\u0442\u0443\u0441 «\u041f\u0440\u0435\u0434\u043b\u043e\u0436\u0435\u043d\u043d\u043e\u0433\u043e \u0441\u0442\u0430\u043d\u0434\u0430\u0440\u0442\u0430», \u043f\u043e\u0441\u043b\u0435 \u0447\u0435\u0433\u043e \u043d\u0430\u0447\u043d\u0451\u0442\u0441\u044f \u0440\u0430\u0431\u043e\u0442\u0430 \u043f\u043e \u043f\u0440\u0438\u0434\u0430\u043d\u0438\u044e RFC \u0441\u0442\u0430\u0442\u0443\u0441\u0430 \u0447\u0435\u0440\u043d\u043e\u0432\u043e\u0433\u043e \u0441\u0442\u0430\u043d\u0434\u0430\u0440\u0442\u0430 (Draft Standard), \u0444\u0430\u043a\u0442\u0438\u0447\u0435\u0441\u043a\u0438 \u043e\u0437\u043d\u0430\u0447\u0430\u044e\u0449\u0435\u0433\u043e \u043f\u043e\u043b\u043d\u0443\u044e \u0441\u0442\u0430\u0431\u0438\u043b\u0438\u0437\u0430\u0446\u0438\u044e \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 \u0438 \u0443\u0447\u0451\u0442 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":96271,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-96270","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Lan\u00e7amento dos servidores NTP NTPsec 1.2.0 e Chrony 4.0 com suporte ao protocolo seguro NTS | ProHoster","description":"O Comit\u00ea IETF (Internet Engineering Task Force), encarregado do desenvolvimento de protocolos e da arquitetura da internet, foi conclu\u00eddo.","canonical_url":"https:\/\/prohoster.info\/pt\/blog\/news\/vypusk-ntp-serverov-ntpsec-1-2-0-i-shrony-4-0-s-podderzhkoj-zashhishhyonnogo-protokola-nts","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"pt_PT","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0412\u044b\u043f\u0443\u0441\u043a NTP-\u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 NTPsec 1.2.0 \u0438 \u0421hrony 4.0 \u0441 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u043e\u0439 \u0437\u0430\u0449\u0438\u0449\u0451\u043d\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 NTS | ProHoster","og:description":"\u041a\u043e\u043c\u0438\u0442\u0435\u0442 IETF (Internet Engineering Task Force), \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0449\u0438\u0439\u0441\u044f \u0440\u0430\u0437\u0432\u0438\u0442\u0438\u0435\u043c \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u0438 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u044b \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0430, \u0437\u0430\u0432\u0435\u0440\u0448\u0438\u043b.","og:url":"https:\/\/prohoster.info\/pt\/blog\/news\/vypusk-ntp-serverov-ntpsec-1-2-0-i-shrony-4-0-s-podderzhkoj-zashhishhyonnogo-protokola-nts","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-10-09T23:42:13+00:00","article:modified_time":"2020-10-09T23:42:13+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"96270","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 10:47:23","updated":"2022-10-01 20:34:45","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts\/96270","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/comments?post=96270"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts\/96270\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media\/96271"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media?parent=96270"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/categories?post=96270"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/tags?post=96270"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}