TGTGInsighttelegram intelligenceLIVE / telegram public index
← Newlearnerの自留地

TGINSIGHT SIMILAR POSTS

類似コンテンツを探す

ソースチャンネル @NewLearnerChannel · Post #14708 · 9月9日

#APPLE 🍎Apple 2025 秋季发布会看些啥?—— 自留地 の 前瞻盘点 明天凌晨,一年一度的阿果秋季春晚又要来了。老规矩,结合此前种种爆料和信息,我们一起来盘点一下今年可能的看点 📱iPhone 17 系列 - A19 系列处理器 - 推出全新 Air 系列,主打 5.5mm 超薄机身,配备「药丸」后摄模组,预计搭载 12GB RAM、Apple C1 调制解调器和 6.6 英寸显示屏 - Air 首发或暂无国行,因其大概率仅支持 eSIM,需等 eSIM 政策落地 - Pro 系列将采用半玻璃半铝的设计,其中玻璃区域用于 MagSafe 充电,后背还将采用巨大摄影头模组 - Pro 系列有望搭载 A19 Pro 处理器,以及全 48MP 后置三摄 / 最高 8 倍光学变焦 - Pro 机型将提供橙色、深蓝色、灰色、白色和黑色机型 - 数字版将迎来 6.3 英寸显示屏、A19 处理器以及「小药丸」后摄模组,有望带来 ProMotion 功能 - 将采用均热板等手段,进一步改善 iPhone 散热问题 📸 今年升级的亮点,我觉得除了推出轻薄 SKU 取代了 Plus 系列之外,依然是影像。随着国产 Android 品牌以及三星等竞品的不断发力,光学长焦等手机相机体验越来越好,Apple 这几年感受到了压力。去年使得 Pro 和 Pro Max 在影像功能上做到了对等,今年很高兴看到模组增大的同时,有新的功能和变化 像素提升、光学倍数增加,都是我们喜闻乐见的,拍演唱会等场景可以排上大用场。但是,正如我去年说的那样,我们也应该拥有一个「专业模式」来充分发挥这些硬件的实力。此外,对于日常用的中焦焦段的选择,Apple 应该有自己的思考 🧠 去年以为 Apple Intelligence 会在过去的这一年大展拳脚,但其实 Apple 还是在做底层的框架协议,至于落地一直传闻想要通过合作或者收购其他 LLM 来实现。我能理解 Apple 站到了一个十字路口,下一步选择很重要。但去全球化日益明显的今天,Apple Intelligence 在各国的落地也受到诸多法律和监管方面阻碍 从我个人的角度来看,对 Apple Intelligence 的需求也不是太强烈,日常主要还是以电脑使用为主。因此,今年也不排除会继续选择国行。最后,eSIM 或许是接下来一年每个人都要考虑的问题,如果新机真的大规模砍掉双 nano-SIM 卡,变为单卡 + eSIM 的模式,应该怎么处理自己目前的多卡问题 ⌚️Apple Watch 系列 - Apple Watch Ultra 3 将搭载全新 S11 芯片,并支持 5G 网络连接,保留卫星通信功能,略微增大屏幕尺寸 - Apple Watch Series 11 预计延续 Series 10 的设计语言 - Apple Watch SE 3 也可能获得升级,重点是升级芯片 - 目前尚不清楚是否会引入血压监测功能 🎧AirPods - AirPods Pro 3 有望在下半年发布 - 有望取消背部的传统实体配对按键,同时为充电盒正面引入触控操作区 - 耳机盒将变得更小 - 引入心率监测、体温监测等健康功能 - 实时翻译功能可能无法随硬件首发一同提供 之前通过 AC+ 更换的越南产 AirPods Pro 一代,已经快要罢工了,因此我迫切地等待第三代的发布 👀 今年的传闻大致如上所述,期待 iPad 和 Mac 更新的朋友或需要等更迟一些的发布会了。随着年龄增长,逐渐发现即便如 Apple 这样的品牌,也不能做对、做好每一件事,黄金时期的发展掩盖了很多问题,一旦停滞进入瓶颈期便暴露无遗。不管怎样,我还是很怀念那个爆料没有这么发达、发布会还是实时直播的年代 🔗 附上一些国内外媒体长文前瞻:Bloomberg | 9to5Mac | MacRumors | The Verge | sspai * 以上所有前瞻信息来自网络和爆料人,均在早晚报出现过,不一一列举来源。请以最终发布会结果为准,欢迎大家届时进群 @NewlearnerGroup 和我们一同观看 🍿️ 频道:@NewlearnerChannel

Hashtags

結果

26件の類似投稿が見つかりました

検索: #devsecops

当前筛选 #devsecops清除筛选
infosecurity

@tg_infosec · Post #3377 · 2025/07/10 16:29

👨‍💻 HTTP Security Headers. • X-Content-Type-Options Header; • Reflected File Download (RFD); • CORS Deception; • Clickjacking; • XSS (Cross-Site Scripting); • SSL/TLS Stripping (MITM); • Cookie Hijacking; • CSRF (Cross-Site Request Forgery); • Information Disclosure Attacks; • Cache-Control Header; • Content-Disposition Header; • Cross-Origin Resource Policy (CORP); • Extra HTTP Header Injection; • Content-Encoding Header; • Access-Control-Allow-Origin Header; • X-Rate-Limit and X-Forwarded Headers; • X-Content-Type-Options Header; • XSS and CSRF Protection; • Content-Security-Policy (CSP). #devsecops

Hashtags

infosecurity

@tg_infosec · Post #3323 · 2025/06/25 12:30

👨‍💻 File Upload Vulnerabilities. • Attack Scenario: Insecure File Content: - 2. Non-Compliant Code: Insecure File Upload Example; - Issues with Non-Compliant Code; - 3. Compliant Code: Secure File Upload Example; - Security Enhancements in Compliant Code; - 4. Reverse Access Control; • Magic Byte Exploits and Securing File Uploads: - Magic Bytes Overview; - Attack Scenario: Magic Byte Exploit; - Non-Compliant Code: Insecure File Upload Example; - Issues with Non-Compliant Code; - Compliant Code: Secure File Upload Example; - Security Enhancements in Compliant Code; - Reverse Access Control; - Process of Securing File Uploads; • Config Overwrite: - Attack Scenario: Configuration Overwrite and Null Byte Injection; - Non-Compliant Code: Insecure File Upload Example; - Issues with Non-Compliant Code; - Compliant Code: Secure File Upload Example; - Security Enhancements in Compliant Code; - Reverse Access and Configuration Overwrite; - Process of Securing File Uploads; • Insecure Handler: - Attack Scenario: Insecure Handler Exploit; - Non-Compliant Code: Insecure File Upload Example; - Issues with Non-Compliant Code; - Compliant Code: Secure File Upload Example; - Security Enhancements in Compliant Code; - Insecure Handler and Web Shell Exploit; - Process of Securing File Uploads. #devsecops

Hashtags

infosecurity

@tg_infosec · Post #3269 · 2025/06/05 16:31

👨‍💻Attacking OpenStack. • Apply Restrictive File Permissions: - Incorrect Example; - Writing Files with Python; - Correct Example; - Secure File Creation in Python; - Verify Ownership and Group; • Avoid Dangerous File Parsing and Object Serialization Libraries; • Python Pipes to Avoid Shells; • Unvalidated URL redirect; • Validate Certificates on HTTPS Connections to Avoid Man-in-the-Middle Attacks; • Create, Use, and Remove Temporary Files Securely: - Python Temporary File Handling; • Restrict Path Access to Prevent Path Traversal; • Use Subprocess Securely; • Parameterize Database Queries: - SQLAlchemy; - MySQL; - PostgreSQL (Psycopg2); • Protect Sensitive Data in Config Files from Disclosure: - Consequences; - Example Log Entries; • Use Secure Channels for Transmitting Data: - Clear Example; - Less Obvious Example; • Escape User Input to Prevent XSS Attacks; • Resources. #devsecops

Hashtags

infosecurity

@tg_infosec · Post #3261 · 2025/06/03 08:31

👨‍💻 Attacking CI/CD. • CI Debug Enabled; • Default permissions used on risky events; • Github Action from Unverified Creator used; • If condition always evaluates to true; • Injection with Arbitrary External Contributor Input; • Job uses all secrets; • Unverified Script Execution; • Arbitrary Code Execution from Untrusted Code Changes; • Unpinnable CI component used; • Pull Request Runs on Self-Hosted GitHub Actions Runner; • Mitigation Strategies; • Example GitHub Actions Workflow; • RCE via Git Clone; • Resources. #devsecops

Hashtags

infosecurity

@tg_infosec · Post #3209 · 2025/05/16 12:32

👨‍💻 Attacking Policy. • Open Policy Agent — это open-source-инструмент контроля доступа, основанный на политиках, который создан в 2016 году и с тех пор стабильно развивается. Сейчас он входит в каталог дипломированных проектов Cloud Native Computing Foundation (CNCF). Его используют Netflix, Pinterest, TripAdvisor и другие компании. • В этой статье перечислены определенные векторы атак, которые могут быть вызваны неправильной конфигурацией Open Policy Agent: • Allowed Repositories; • Automount Service Account Token for Pod; • Block Endpoint Edit Default Role; • Block Services with type LoadBalancer; • Block NodePort; • Block Wildcard Ingress; • Disallow Interactive TTY Containers; • Step-by-Step Instructions; • Allow Privilege Escalation in Container; • Step-by-Step Instructions; • Privileged Container; • Read Only Root Filesystem; • Host Networking Ports; • App Armor; • SELinux V2; • Resources. #devsecops

Hashtags

infosecurity

@tg_infosec · Post #3200 · 2025/05/13 08:30

👨‍💻 Attacking Secrets. • Secrets in private repositories; - Scenario: An Attacker Scanning a Private Repository for Secrets; - Example Commands and Codes; • User Credentials in CI Pipelines; - Scenario: An Adversary Exploiting CI Pipeline Credentials; - Example Commands and Codes; • Azure Key-Vault Authentication Abuse; - Azure’s Documentation Overview; • Practical Implementation: Azure’s Authentication Solution; - Steps for Compromising Azure Key Vault; • Azure Key Vault RBAC; • Ansible Vault Secret; - Generating a Hash for Cracking; - Cracking the Hash; - Decrypting the File; • Vault-Backend-Migrator; - Threats; • Kubernetes Sealed Secrets; • chamber; • Vault Secrets Operator; • Buttercup Weak Password; • teller manipulate files; • BlackBox; • Conclusion; - Attacker's Next Steps. #devsecops

Hashtags

infosecurity

@tg_infosec · Post #3108 · 2025/04/10 08:00

🏰 DevSecOps Security Architecture. • Honeypot Network and Services in DevSecOps Security Architecture; • Flume log collection; • Kafka Knowledge System; • Zookeeper Knowledge System; • ElastAlert ES Alarm Tool; • Elastic Knowledge System; • Real IP address Detection; • Nginx configuration log format; • Container security tools; • osquery operating system detection and analysis; • jumpserver open source bastion server; • wazuh Host Intrusion Detection System; • Bro Network Security Monitoring; • GitHub Information Leak Monitoring; • Application layer denial of service attacks; • Slowloris; • Resources. #DevSecOps

Hashtags

infosecurity

@tg_infosec · Post #3065 · 2025/03/26 16:34

👨‍💻 Attacking .NET • Code Access Security (CAS); • AllowPartiallyTrustedCaller attribute (APTCA); • Distributed Component Object Model (DCOM); • Timing vulnerabilities with CBC-mode symmetric; • Race Conditions; • App Secrets; • XML Processing; • Timing attacks; • ViewState is love; • Formatter Attacks; • TemplateParser; • ObjRefs. ➡️https://blog.devsecopsguides.com/p/attacking-net #DevSecOps

Hashtags

infosecurity

@tg_infosec · Post #3047 · 2025/03/21 12:35

👩‍💻 Attacking Rust. - Cargo Dependency Confusing; - Unsafe Code Usage; - Integer Overflow; - Panics in Rust Code; - memory leaks; - Uninitialized memory; - Foreign Function Interface; - OOB Read plus; - race condition to escalate privileges; - TOCTAU race condition; - out-of-bounds array access; - References. #devsecops

Hashtags

infosecurity

@tg_infosec · Post #2995 · 2025/03/04 12:33

👩‍💻 Attacking NodeJS Application. - Use flat Promise chains; - Set request size limits; - Do not block the event loop; - Perform input validation; - Perform output escaping; - Perform application activity logging; - Monitor the event loop; - Take precautions against brute-forcing; - Use Anti-CSRF tokens; - Prevent HTTP Parameter Pollution; - Do not use dangerous functions; - Use appropriate security headers; - Listen to errors when using EventEmitter; - Set cookie flags appropriately; - Avoid eval(), setTimeout(), and setInterval(); - Avoid new Function(); - Avoid code serialization in JavaScript; - Use a Node.js security linter; - References. #devsecops

Hashtags

infosecurity

@tg_infosec · Post #2847 · 2025/01/14 08:30

👨‍💻 Attacking APIs \ Атаки на API. • Программный интерфейс приложений (API) - фундаментальный элемент инноваций в современном, движимом приложениями мире. API - важная составляющая современных мобильных, SaaS и веб приложений, используемая в клиентских, партнерских и внутренних приложениях от банковской сферы, сфер розничных продаж и логистики до интернета вещей, автономных автомобилей и умных городов. • По своей природе API раскрывают логику приложения и критичные данные, например, персональные данные, именно поэтому API все чаще становятся целью злоумышленников. Стремительные инновации невозможны без безопасных API. В этой статье рассматриваются общие векторы атак на API и приводятся примеры безопасной разработки. ➡️https://blog.devsecopsguides.com/attacking-apis #devsecops

Hashtags

infosecurity

@tg_infosec · Post #3252 · 2025/05/30 12:30

👨‍💻 Attacking Pipeline. • DevOps resources compromise; • Control of common registry; • Direct PPE (d-PPE); • Indirect PPE (i-PPE); • Public PPE; • Changes in repository; • Inject in Artifacts; • User/Services credentials; • Typosquatting docker registry image; • Resources. #DevOps#DevSecOps

前へ1ページ / 3ページ中次へ