Telegram RegisterThe public register of Telegram
Telegram profile photo for Нарыл

Channel

Нарыл

@naryl_sec

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

1,495subscribers

-1 since we began measuring on 4 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001588447640
TypeChannel
Username@naryl_sec
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live5 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/naryl_sec

Growth

1,4951,4961,495.54 Sept 2026, 14:47 — 1,496 subscribers4 Sept 2026, 15:22 — 1,496 subscribers5 Sept 2026, 21:41 — 1,495 subscribers4 Sept 2026, 14:475 Sept 2026, 21:41
3 measurements spanning 1 day, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,495–1,496 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 21:411,495-1
4 Sept 2026, 15:221,496no change
4 Sept 2026, 14:471,496first reading

Engagement

20 posts held, back to 4 September 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 September 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

240 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 56.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥13656.7%
👍6627.5%
114.58%
👏72.92%
👎52.08%
😢41.67%
😱31.25%
🥰31.25%
🤯20.833%
😁10.417%
🤔10.417%
🤬10.417%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 240 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 4 September 2023 to 9 September 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

9 Sept 2024, 10:33 UTC≈3,470 views15 reactionsread 4 September 2026

Gitlab pre_build_script. Part 2 Так что же делать чтобы after_script не выполнялся после падения pre_build_script? Можно, например, дергать из скрипта гитлабовскую апишку и канцелить джобу. Но можно поступить проще, если разобраться как раннер запускает джобы внутри (все нижеперечисленное я изучал для k8s-раннера, полагаю что верно и для docker-раннеров тоже). Тут важны два факта. Первый - для запуска любых скрип

🔥6🥰32👍2😁1😢1

Signed Pavel Sorokin

29 Aug 2024, 08:40 UTC≈3,250 views11 reactionsread 4 September 2026
Photo

Gitlab pre_build_script Иногда есть необходимость дополнительно защитить Gitlab Runner. Например, если на нем имеются дополнетильные credentials, если он имеет особые сетевые доступы и т.д. Способы защиты могут быть тоже разные: - проверка того что тот кто запустил джобу входит в белый список - проверка подписи коммитов - проверка целостности джобы - и т.д. Для реализации такой защиты может применяться параметр ра

🔥7😢3👍1

Signed Pavel Sorokin

19 Aug 2024, 11:12 UTC≈2,900 views6 reactionsread 4 September 2026

OFFZONE_CYBERED_SPECIAL - промокод на скидку на воркшопы OFFZONE (не только мой)

👍6

Signed Pavel Sorokin

19 Aug 2024, 09:05 UTC≈2,280 views5 reactionsread 4 September 2026

Второй год подряд буду проводить воркшоп на Offzone.

🔥31👍1

Signed Pavel Sorokin

19 Aug 2024, 09:05 UTC≈2,630 views10 reactionsread 4 September 2026
Forwarded from @offzone_moscowVideo

🔧 Воркшоп «Ломаем CI/CD 2.0» На воркшопе вы изучите работу с секретами в CI/CD и научитесь обходить защиты раннеров от PPE. Что в программе: ➡️ Секреты в CI/CD: GitLab variables / vault. ➡️ Интеграция Vault с GitLab и проблемы в ней. ➡️ Интеграция Vault с K8s и проблемы в ней. ➡️ Защита раннеров от PPE и способы ее обхода. Что потребуется: ➡️ docker, ➡️ kubectl, ➡️ vault (cli). Когда: 23 августа, 14:30–17:30.

🔥62👎2

Signed Pavel Sorokin

24 May 2024, 04:58 UTC≈3,470 views32 reactionsread 4 September 2026
File

Запись моего выступления на PHDays: https://phdays.com/forum/broadcast/?talk=645&tag=offense Слайды прикладываю UPD: youtube - https://www.youtube.com/watch?v=YAV9mbnlUho

🔥27👍4🤬1

Signed Pavel Sorokin

14 May 2024, 09:04 UTC≈8,200 views41 reactionsread 4 September 2026
Photo

Есть такая общеизвестная проблема когда делаешь non-root в k8s: контейнерам нужно биндить порты до 1024, что по умолчанию в Linux запрещено. Лично по-моему само по себе такое ограничение - архитектурная ошибка в Linux, которая привела к куче проблем и сложностей: сервису, например nginx, нужно стартовать от рута, забиндить порт, а потом дропнуть лишние привилегии. Что уже само по себе звучит не безопасно и разумеетс

🔥28👍6👎32🤯2

Signed Pavel Sorokin

12 Apr 2024, 10:15 UTC≈3,110 views11 reactionsread 4 September 2026

Мой бывший коллега классно развил тему о которой я рассказывал в прошлом году на БЕКОН. Там шла речь о том чтобы при наличии доступа к docker API socket нельзя было поднять привилегии и залезать в чужие контейнеры. Но было ограничение - доступ к собственным контейнерам также сильно ограничивался. Улучшенный подход он описал в статье на хабре. Теперь с помощью плагина https://github.com/I-am-Roman/docker-auth-plugin

👏73🤔1

Signed Pavel Sorokin

9 Feb 2024, 12:29 UTC≈3,090 views12 reactionsread 4 September 2026

Kyverno resourseFilters Если разворачивать kyverno с помощью values.yaml по умолчанию, то в них окажется интересный параметр resourceFilters Этот параметр добавляет в исключения Enforce политик kyverno некоторую часть ресурсов, среди которых хочется отметить почти первые три строчки. Они говорят о том что все yaml в неймспейсах: - kube-system - kube-public - kube-node-lease НЕ будут валидироваться. Также в исключен

🔥11👍1

Signed Pavel Sorokin

17 Jan 2024, 09:03 UTC≈3,570 views5 reactionsread 4 September 2026
Photo

Photo, posted without a caption

🔥5

Signed Pavel Sorokin

17 Jan 2024, 09:02 UTC≈3,440 views11 reactionsread 4 September 2026

Gitlab Access Tokens Gitlab позволяет создавать токены доступа для групп, проектов или персональные для пользователей. Если нам достался такой токен (например, нашли в репозитории), то встает вопрос - а что же именно с этим токеном можно делать? Для этого можно использовать запрос: curl --header "PRIVATE-TOKEN: token_here" https://gitlab.example.com/api/v4/personal_access_tokens/self В ответе будет имя токена,

🔥91👍1

Signed Pavel Sorokin

13 Nov 2023, 09:03 UTC≈3,130 views9 reactionsread 4 September 2026

apiVersion: v1 kind: Pod metadata: name: pwn annotations: container.apparmor.security.beta.kubernetes.io/pwned: unconfined #disable apparmor spec: hostPID: true #root PID namespace containers: - name: pwn image: ubuntu command: [ "cat", "/proc/1/root/etc/kubernetes/admin.conf" ] securityContext: capabilities: add: - SYS_PTRACE # SYS_PTRACE to bypass ptrace access mode c

🔥5👍4

Signed Pavel Sorokin

Showing the 12 most recent of 20 posts we hold for @naryl_sec. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Пакет Безопасности
@package_security · 33,214
Telegram ranks this channel #81 of 82 here — alongside 81 others — read 4 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 5 September 2026 — this entry's latest reading, not the date you are reading this.

“Нарыл” (@naryl_sec), 1,495 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/naryl_sec.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.