Telegram RegisterThe public register of Telegram
Telegram profile photo for Jumpserver PAM FAQ

Channel

Jumpserver PAM FAQ

@JumpServerPAM

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

1,033subscribers

+3 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001969043238
TypeChannel
Username@JumpServerPAM
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/JumpServerPAM

Growth

1,0301,0381,0347 August 2026 — 1,030 subscribers8 August 2026 — 1,030 subscribers14 August 2026 — 1,032 subscribers18 August 2026 — 1,035 subscribers20 August 2026 — 1,038 subscribers24 August 2026 — 1,037 subscribers28 August 2026 — 1,038 subscribers31 August 2026 — 1,032 subscribers3 September 2026 — 1,036 subscribers9 September 2026 — 1,033 subscribers1,0337 August 20269 September 2026
10 measurements spanning 33 days, net +3. 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,029–1,039 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 09:371,033-3
3 Sept 2026, 18:171,036+4
31 Aug 2026, 09:081,032-6
28 Aug 2026, 04:341,038+1
24 Aug 2026, 19:361,037-1
20 Aug 2026, 22:261,038+3
18 Aug 2026, 01:421,035+3
14 Aug 2026, 20:171,032+2
8 Aug 2026, 00:311,030no change
7 Aug 2026, 21:321,030first reading

Engagement

20 posts held, back to 26 February 2026the 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

162 reactions across 18 posts, in 9 distinct kinds. The most used accounts for 41.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥6741.4%
👍5030.9%
169.88%
👏148.64%
❤‍🔥63.70%
🫡42.47%
🎉31.85%
🍌10.617%
😱10.617%

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 18 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 162 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 26 February 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
1
of 19 we hold a reading for · 5%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @JumpServerPAM. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 26 February 2026 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Aug 2026, 12:53 UTC398 views6 reactionsread 8 August 2026
Photo

Как использовать Git через SSH-прокси JumpServer Проверили работу git clone, pull и других Git-операций через одноразовый токен JumpServer, делимся инструкцией на примере github.com: Создайте в JumpServer SSH-актив: хост: github.com; порт: 22; системная учётная запись: git; аутентификация: SSH-ключ, добавленный в GitHub. При этом в самом активе укажите только хост github.com. Путь к конкретному р

🔥5🍌1

30 Jul 2026, 10:29 UTC689 views3 reactionsread 8 August 2026
Photo

Подпись RDP файлов. Заметили новое окно предупреждения при открытии RDP-файлов? Это не баг — Microsoft с апрельского обновления 2026 стала жёстче предупреждать о непроверенных .rdp-файлах (на фоне уязвимости спуфинга CVE-2026-26151). Если издатель неизвестен — Windows прямо предлагает прервать подключение. Разбираем в статье, как в JumpServer EE закрыть этот вопрос — включить подпись RDP-файлов, чтобы издатель был

👍3

28 Jul 2026, 17:43 UTC758 views5 reactionsread 8 August 2026
Photo

Опубликована критическая уязвимость в JumpServer. Если вы ждали знак, чтобы обновить JumpServer, то это он 29 июля 2026 команда JumpServer опубликовала уведомление о 4 уязвимостях в версиях V3 < 3.10.22 LTS и V4 < 4.10.17 LTS: - CVE-2026-16723 — уязвимость fastjson в компоненте Chen - CVE-2026-54336 — path traversal в SFTP веб-терминала KoKo - CVE-2026-44845 — RCE через Jinja-инъекцию при развёртывании RemoteApp (н

🫡4😱1

28 Jul 2026, 08:50 UTC728 views4 reactionsread 8 August 2026

Вышла новая версия JumpServer v4.10.18 Улучшения: - Улучшен разбор и обработка длинных SQL-запросов в Chen. - Снижено потребление памяти Chen при одновременной работе нескольких сессий. - Обновлены внешний вид ИИ-помощника Luna и стиль иконки боковой панели. - Улучшен интерфейс встроенных уведомлений. Исправления: - Исправлены проблемы с настройкой порта прослушивания в KoKo. - Восстановлена работа передачи файлов

🔥4

22 Jul 2026, 11:48 UTC959 views14 reactionsread 8 August 2026
Photo

Подключение к целевой системы со своим SSH ключом По просьбам клиентов, в новой версии JumpServer 4.10.17 появилась возможность использовать свой SSH ключ для подключения к целевой системе.

👍11👏3

20 Jul 2026, 08:16 UTC823 views6 reactionsread 8 August 2026
Photo

Вышла новая версия JumpServer v4.10.17 По рекомендации вендора обновление продуктивной среды целесообразно отложить до выхода первых исправлений. Релиз содержит значительный объем изменений в кодовой базе, поэтому в ближайшее время, вероятнее всего, будут выпущены дополнительные хотфиксы. Новое в версии: - Django обновлён до 5.2, Python — до 3.14, Vue — до 3.5 - Поддержка кастомной SSO-аутентификации - Настройка сп

🔥6

15 Jul 2026, 15:02 UTC≈1,170 views11 reactionsread 8 August 2026

Port Forwarding в JumpServer Иногда нужно безопасно получить доступ к сервису на удаленном сервере, который недоступен напрямую: например, к веб-интерфейсу, базе данных, Grafana, Prometheus, Redis, PostgreSQL и т.д. Для этого в SSH используется port forwarding (проброс портов). Начиная с последних версий JumpServer эту возможность можно включить. Включение 1. Откройте конфигурационный файл: nano /opt/jumpserver/co

🔥10👏1

8 Jul 2026, 08:31 UTC≈1,130 views17 reactions2 Starsread 8 August 2026

Наши друзья и партнеры из TS Solution запустили полноценный практический курс по PAM на примере JumpServer. Что особенно приятно: — не очередная презентация «что такое PAM»; — акцент именно на практике и реальных сценариях; — в качестве учебной платформы выбран JumpServer — один из самых популярных open-source PAM в мире. И, пожалуй, самое ценное — такие материалы появляются не потому, что производитель занес рекла

🔥12🎉3❤‍🔥1👏1

1 Jul 2026, 09:10 UTC≈1,210 views20 reactionsread 8 August 2026

Тест производительности JumpServer: 222 одновременные RDP-сессии на сервере 8 vCPU / 16 GB RAM Попался интересный отчет по нагрузочному тестированию JumpServer с графическимиу RDP-сессиями. Конфигурация стенда: • 8 vCPU • 16 GB RAM • SSD 500 GB • 222 одновременные RDP-сессии • длительность теста — 6 часов Результат: Все 222 RDP-сессии оставались активными в течение 6 часов. Разрывов соединений не было. Средняя

👍10👏5🔥5

4 Jun 2026, 12:06 UTC≈1,230 views13 reactionsread 8 August 2026
Photo

У нас появилась система заявок в техническую поддержку Запустили портал: https://systema-zayavok.afi-d.ru Если честно — основная причина довольно простая: рабочих чатов, переписок и разных каналов связи стало уже слишком много 😅 Плюс у части заказчиков Telegram не всегда удобно доступен из-за блокировок, политик безопасности и корпоративных ограничений. Поэтому сделали единый портал для обращений: — создание и от

🔥93👏1

22 May 2026, 08:57 UTC≈1,220 views4 reactionsread 8 August 2026
Photo

О чем написать статью? О чем сделать видео? Какие вопросы есть по JumpServer PAM? Пилоты и внедрения идут, всё в порядке, в мессенджер МАКС мы не ушли :) Давно не было постов, потому что JumpServer PAM давно (целых 2.5 месяца!) не обновлялся. По информации от вендора, они пока все дружно заняты на крупном проекте, а также уже вовсю делают 5ю версию JumpServer. Но возможно, вам интересно разобрать решения для каких-

👍31

Showing the 12 most recent of 20 posts we hold for @JumpServerPAM. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“Jumpserver PAM FAQ” (@JumpServerPAM), 1,033 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/JumpServerPAM.

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.