Channel
@public_sec
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,668subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002160960271 |
|---|---|
| Type | Channel |
| Username | @public_sec |
| Created | Between 1 May 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/public_sec |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 04:02 | 1,668 | -6 |
| 7 Aug 2026, 23:00 | 1,674 | no change |
| 7 Aug 2026, 22:48 | 1,674 | first reading |
20 posts held, back to 16 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 19 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 21 July 2026 |
|---|---|
| Posts held | 20 (16 July 2026 – 21 July 2026) |
| Views total | 13,351 |
| Reactions total | 186 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:00 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
186 reactions across 19 posts, in 5 distinct kinds. The most used accounts for 55.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 103 | 55.4% | |
| 👍 | 39 | 21.0% | |
| 🔥 | 37 | 19.9% | |
| 👌 | 4 | 2.15% | |
| 🤣 | 3 | 1.61% |
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 186reactions 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 16 July 2026 to 21 July 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.
یه نکته رو بگم این سرفصل قطعی نیست در طول مسیر ممکنه مباحث حذف یا اضافه بشن و یا جابجایی صورت بگیره. همچنین کانسپت Windows Internal به سرفصل اضافه خواهد شد که در مباحث Reverse Engineering به کار میاد و در بخش PWN هم کاملا درمورد WinDbg صحبت خواهیم کرد و همچنین در فارنزیک کانسپت Windows Artifacts هم اضافه خواهد شد که به پیش نیازش ویندوز اینترنال هست. در بخش رمزنگاری ماژول ChaCha20-Poly1305 هم کار خواهیم کرد که یکی از…
❤9🔥1
🔖 دوره CTF JANUS سرفصل های دوره: از طریق لینک دانلود سرفصل ها قابل دریافت است. مدت زمان دوره: مدت زمان تقریبی دوره تا ۹ ماه در نظر گرفته شده. ظرفیت : 15 نفر پشتیبانی: تا پایان دوره پشتیبانی آموزشی برقرار خواهد بود و علاوه بر بنده ، TAهای دوره نیز برای پاسخ گویی به سؤالات و رفع اشکال در کنار دانشجویان خواهند بود. شهریه دوره: ۸,۰۰۰,۰۰۰ تومان شیوه برگزاری: دوره بهصورت نیمه آنلاین برگزار می شود و شامل جلسات آموزشی…
❤13🤣3🔥1
https://medium.com/@Aacle/the-bug-bounty-playbook-idor-72038e510337
❤5
امشب جزئیات نهایی دوره CTF Janus رو اطلاع رسانی می کنم. یه سوالی هم که خیلی ازم پرسیده میشه اینه چقدر طول میکشه تموم بشه؟ بهترین حالت رو 9 ماه براش در نظر گرفتم. و اینکه ظرفیت هم نهایت تا 15 نفر هست سوالی بود میتونید پیوی بپرسید.
❤6👌1
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-security-identifiers
❤4
این مبحث توی Privilege Escalation کاربرد زیادی داره چون با بررسی SID ها و تحلیل RID ها میشه یوزرهای موجود تو سیستم رو و سطح دسترسی اون ها رو و حساب های دارای دسترسی بالا تر رو شناسایی کرد. و ما اینجا فقط یه قطره کوچیک از Windows Security Identifiers رو گفتیم و مباحث تخصصی تر و پیچیده تر هم داره که از حوصله بنده و کانال خارجه خواستین و علاقه داشتین میتونین سری به کتاب ها یا سورس های مربوط به Privilege Escalation بزنی…
❤7
برای اینکه SID یوزر ها رو تو سیستممون ببینیم میتونیم کامند زیر رو بزنیم: wmic useraccount get name,sid این دستور تموم SID های مربوط به یوزر های موجود تو سیستم رو نمایش میده. خروجی هم معمولا به شکلیه که تو عکس اومده و چیزی که برای مهمه مقادیر RID هست و تو عکس میبینیم که یه حساب Administrator و یه حساب Guest تو سیستم وجود داره که میتونه اون ها رو بر اساسRID مربوط بهش شناسایی کرد. ━━━━━━━━━━━━ @public_sec
👍5
این نکته هم بگم تو ویندوز خیلی از حساب ها یه سری RID ثابت دارن و از اون طریق میشه یوزر هایی که مهمن و سطح دسترسی بالایی دارن رو شناسایی کنیم Administrator: 500 Guest User: 501 Domain Administrator: 512 Domain Computer: 515 ━━━━━━━━━━━━ @public_sec
❤5
گفتیم که مقادیر مختلفی داره و معمولا اینان : Null Authority: 0 World Authority: 1 Local Authority: 2 Creator Authority: 3 Non-Unique Authority: 4 NT Authority: 5 ━━━━━━━━━━━━ @public_sec
❤5
تو سیستم عامل ویندوز User Identification با استفاده از یک شناسه امنیتی به اسم SID انجام میشه. هر یوزر و هر گروه توی ویندوز دارای یه SID یونیک هست که از چند بخش مختلف تشکیل شده. هر بخش از این شناسه دیتای مشخصی درباره تایپ اون شناسه و Authority گروه یا یوزر مربوطه و شناسه نسبی اون به ما میگه. حالا ساختار SID رو ما تو عکس میبینیم که به چه شکله و اجزای مختلفی رو به خودش اختصاص داده. ما یه SID String داریم که حرف s در ا…
❤7
یکی از دوستان سوال پرسیده برای حل این چلنج ها چی نیازه بدونیم؟ یاشار جوابتو تو مقدمه شروع این چلنج داده.! تو بخش Knowledge مشخص کرده که برای حل این چالش ها باید آشنایی پایه با شبکه و وب و بحث HTTP و JS و یه سری مفاهیم برنامه نویسی و امنیت داشته باشید. تو بعضی مراحل هم به مفاهیمی مثل استگانوگرافی و رمزنگاری و طریقه سرچ موثر تو گوگل و مهم تر از همه تفکر تحلیلی نیاز دارید. کلیت اینه شما با این دانش ها باید بتونین رفتا…
👍8❤1
دیشب تمام مراحل رو رفتم و تمام شد ، چالش جالبی بود ولی نسبت به چالش های سال پیش زیاد تعریفی نبود. به زودی درموردش مینویسم. جایی گیر کردین بگید hint میدم
🔥6❤4👍3
Showing the 12 most recent of 20 posts we hold for @public_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.
Citation-graph rank — 911,845 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“R3dLineSec” (@public_sec), 1,668 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/public_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.