Risk of Public Disclosure: Learning from Willy Wonka
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Webrtc and XMPP
webRTC and XMPP Philipp Hancke, XMPP Summit 2013 What is this webRTC thing … …and why should XMPP developers care? . I assume you know what XMPP is… . … you might have heard of Jingle . the XMPP framework for establishing P2P sessions . used for VoIP, filesharing, … . … you might have also heard about this webRTC thing . doing VoIP in the browser . without plugins . „no more flash“ . Do you want to know how it relates to XMPP ? Philipp Hancke © ESTOS GmbH 2013 2 What is webRTC? . P2P sessions between browsers . no servers involved in media transfer . using open standards . Javascript API in the browser . also an BSD-licensed C++ library from Google . Want to know more? . Listen to the evangelists! . Justin Uberti http://www.youtube.com/watch?v=E8C8ouiXHHk . Jose de Castro http://vimeo.com/52510068 . Cullen Jennings http://vimeo.com/cullenfluffyjennings/rtcwebexplained Philipp Hancke © ESTOS GmbH 2013 3 Initiating P2P sessions . initiate a P2P session between two browsers . negotiate media codecs, NAT traversal, etc . media is sent P2P . you need a session initiation protocol . SIP? . JSEP? . H.323? . Jingle! . webRTC does not mandate a signalling protocol . WG decision Philipp Hancke © ESTOS GmbH 2013 4 Call Flow - JSEP Philipp Hancke © ESTOS GmbH 2013 5 Jingle . You can use Jingle as signalling protocol . together with BOSH or XMPP over websockets in the browser . Demo later . But… . webRTC uses the Session Description Protocol as an API . Jingle does not use SDP . You need a mapping SDP -> Jingle -> SDP . Complicated, but doable . Topic for breakout Philipp Hancke © ESTOS GmbH 2013 6 Call Flow - Jingle Philipp Hancke © ESTOS GmbH 2013 7 webRTC-Jingle usecases . -
Military History Anniversaries 0101 Thru 0131
Military History Anniversaries 1 thru 31 January Events in History over the next 30 day period that had U.S. military involvement or impacted in some way on U.S military operations or American interests Jan 00 1944 – WW2: USS Scorpion (SS–278). Date of sinking unknown. Most likely a Japanese mine in Yellow or East China Sea. 77 killed. Jan 00 1945 – WW2: USS Swordfish (SS–193) missing. Possibly sunk by Japanese Coast Defense Vessel No. 4 on 5 January or sunk by a mine off Okinawa on 9 January. 89 killed. Jan 01 1942 – WW2: The War Production Board (WPB) ordered the temporary end of all civilian automobile sales leaving dealers with one half million unsold cars. Jan 01 1945 – WW2: In Operation Bodenplatte, German planes attack American forward air bases in Europe. This is the last major offensive of the Luftwaffe. Jan 02 1777 – American Revolution: American forces under the command of George Washington repulsed a British attack at the Battle of the Assunpink Creek near Trenton, New Jersey. Casualties and losses: US 7 to 100 - GB 55 to 365. Jan 02 1791 – Big Bottom massacre (11 killed) in the Ohio Country, marking the beginning of the Northwest Indian War. Jan 02 1904 – Latin America Interventions: U.S. Marines are sent to Santo Domingo to aid the government against rebel forces. Jan 02 1942 – The Federal Bureau of Investigation (FBI) convicts 33 members of a German spy ring headed by Fritz Joubert Duquesne in the largest espionage case in United States history-the Duquesne Spy Ring. Jan 02 1942 – WW2: In the Philippines, the city of Manila and the U.S. -
Copyrighted Material
Stichwortverzeichnis A B Abstreitbarkeit 167 Bequemlichkeit 30 Adblocker 96 Bitcoin 110 – Adblock Plus 96 Blackberry 215 – Disconnect 96 Bookmarks siehe Favoriten – Ghostery 96 Browser 68, 75 – Privacy Badger 96 – Add-on 87, 90 – uBlock 97 – Apple Safari 77 Add-on – Cache 88 – Browser 87, 90 – Chromium 78 – E-Mail-Client 126 – Chronik 87 – Enigmail siehe Enigmail – Fingerprinting 85, 98 – GpgOL 137 – Google Chrome 77 – Mailvelope 130, 132 – HTML-Engine 80 – Thunderbird 139 – Hygiene 88 Adium 170 – Iceweasel 78 Advanced Programming Interface (API) 90, – Inkognito-Modus 86 182 – integrierte Suche 84 Android – Internet Explorer 77 – Android Privacy Guard (App) 156 – Konqueror 78 – K9 Mail (E-Mail-Client) 156 – Microsoft Edge 92 – OpenKeychain (App) 156 – Midori 78 – PGP 156 – Mosaic 68 – R2Mail2 (E-Mail-Client) 158 – Mozilla Firefox 68, 76 – S/MIME 156 – Netscape Navigator 68 Anonymität 206 COPYRIGHTED– Opera 77MATERIAL AOL Instant Messenger (AIM) 164 – Plug-in 87 Apple Mail – Prole (Identitäten) 87 – PGP 145 – Synchronisation von Einstellungen – S/MIME 155 86 Authentizierung 167, 169, 176, 179 – Web (Epiphany) 78 – Adium 172 Buffer Overow 82 – Multifaktor- 201 Bugs 82 – Pidgin 169 Bundesamt für Sicherheit in der Informations- Authentizität 29, 54, 56 technik (BSI) 215 233 Stichwortverzeichnis C – E-Mail-Adresse 119 Caesar-Chiffre 36 – Header 121 Certicate Authority siehe Zertizierungsstelle – Provider 129, 131, 139 Chain of Trust siehe Web of Trust – Server 122 Chaos Computer Club (CCC) 133 Eingangsverschüsselung 125 Chat 161 Electronic -
Military History Anniversaries 1 Thru 15 January
Military History Anniversaries 1 thru 15 January Events in History over the next 15 day period that had U.S. military involvement or impacted in some way on U.S military operations or American interests Jan 00 1944 – WW2: USS Scorpion (SS–278). Date of sinking unknown. Most likely a Japanese mine in Yellow or East China Sea. 77 killed. Jan 00 1945 – WW2: USS Swordfish (SS–193) missing. Possibly sunk by Japanese Coast Defense Vessel No. 4 on 5 January or sunk by a mine off Okinawa on 9 January. 89 killed. Jan 01 1781 – American Revolution: Mutiny of the Pennsylvania Line – 1,500 soldiers from the Pennsylvania Line (all 11 regiments under General Anthony Wayne’s command) insist that their three-year enlistments are expired, kill three officers in a drunken rage and abandon the Continental Army’s winter camp at Morristown, New Jersey. Jan 01 1883 – Civil War: President Abraham Lincoln signs the final Emancipation Proclamation, which ends slavery in the rebelling states. The proclamation freed all slaves in states that were still in rebellion as of 1 JAN. Jan 01 1915 – WWI: The 15,000-ton British HMS class battleship Formidable is torpedoed by the German submarine U-24 and sinks in the English Channel, killing 547 men. The Formidable was part of the 5th Battle Squadron unit serving with the Channel Fleet. Jan 01 1942 – WW2: The War Production Board (WPB) ordered the temporary end of all civilian automobile sales leaving dealers with one half million unsold cars. Jan 01 1942 – WW2: United Nations – President Franklin D. -
A Counterintelligence Reader, Volume 2 Chapter 1, CI in World
CI in World War II 113 CHAPTER 1 Counterintelligence In World War II Introduction President Franklin Roosevelts confidential directive, issued on 26 June 1939, established lines of responsibility for domestic counterintelligence, but failed to clearly define areas of accountability for overseas counterintelligence operations" The pressing need for a decision in this field grew more evident in the early months of 1940" This resulted in consultations between the President, FBI Director J" Edgar Hoover, Director of Army Intelligence Sherman Miles, Director of Naval Intelligence Rear Admiral W"S" Anderson, and Assistant Secretary of State Adolf A" Berle" Following these discussions, Berle issued a report, which expressed the Presidents wish that the FBI assume the responsibility for foreign intelligence matters in the Western Hemisphere, with the existing military and naval intelligence branches covering the rest of the world as the necessity arose" With this decision of authority, the three agencies worked out the details of an agreement, which, roughly, charged the Navy with the responsibility for intelligence coverage in the Pacific" The Army was entrusted with the coverage in Europe, Africa, and the Canal Zone" The FBI was given the responsibility for the Western Hemisphere, including Canada and Central and South America, except Panama" The meetings in this formative period led to a proposal for the organization within the FBI of a Special Intelligence Service (SIS) for overseas operations" Agreement was reached that the SIS would act -
Google Talk: Is It Ready for the Enterprise?
Research Publication Date: 16 April 2009 ID Number: G00166834 Google Talk: Is It Ready for the Enterprise? David Mario Smith, James Lundy This report discusses the Google Talk instant messaging product and its suitability for enterprises. This is important for companies which are looking at alternatives to IBM and Microsoft for messaging and collaboration. Key Findings • Google Talk IM is based on the Extensible Messaging and Presence Protocol (XMPP) and Jingle protocols. • To get enterprise-level support for Google Talk, companies have to purchase the full Google Apps Premier Edition (GAPE) suite. • Enterprise users are already using the Google Talk and Gmail free services. Recommendations • Enterprises making collaboration decisions should include the Google Apps portfolio as part of an effort to compare the economics of their current incumbent provider vs. similar services provisioned in the cloud. © 2009 Gartner, Inc. and/or its Affiliates. All Rights Reserved. Reproduction and distribution of this publication in any form without prior written permission is forbidden. The information contained herein has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartner's research may discuss legal issues related to the information technology business, Gartner does not provide legal advice or services and its research should not be construed or used as such. Gartner shall have no liability for errors, omissions or inadequacies in the information contained herein or for interpretations thereof. The opinions expressed herein are subject to change without notice. WHAT YOU NEED TO KNOW Enterprise instant messaging (IM) has emerged to become an infrastructure component in enterprises. -
A Comparison Between Inter-Asterisk Exchange Protocol and Jingle Protocol: Session Time
Engineering, Technology & Applied Science Research Vol. 6, No. 4, 2016, 1050-1055 1050 A Comparison Between Inter-Asterisk eXchange Protocol and Jingle Protocol: Session Time H. S. Haj Aliwi N. K. A. Alajmi P. Sumari K. Alieyan School of Computer Sciences Saad Al-Abdullah Academy School of Computer Sciences National Advanced IPv6 Center Universiti Sains Malaysia for Security Sciences, Kuwait Universiti Sains Malaysia Universiti Sains Malaysia [email protected] [email protected] [email protected] [email protected] Abstract—Over the last few years, many multimedia conferencing sessions. Such applications are Gtalk, Talkonaut, and Hangouts and Voice over Internet Protocol (VoIP) applications have been [7]. developed due to the use of signaling protocols in providing video, audio and text chatting services between at least two participants. II. BACKGROUND This paper compares between two widely common signaling protocols: InterAsterisk eXchange Protocol (IAX) and the extension of the eXtensible Messaging and Presence Protocol A. IAX Protocol (Jingle) in terms of delay time during call setup, call teardown, In 2004, Mark Spencer created the Inter-Asterisk eXchange and media sessions. (IAX) protocol for asterisk that performs VoIP signaling [22]. IAX is supported by a few other softswitches, (Asterisk Private Keywords-multimedia conferencing; VoIP; signaling protocols; Branch eXchange) PBX systems [23], and softphones [18]. Jingle; IAX Any type of media (Video, audio, and document conferencing) can be managed, controlled and transmitted through the I. INTRODUCTION Internet Protocol (IP) networks based on IAX protocol [25]. With the appearance of numerous multimedia conferencing IAX2 is considered to be the current version of IAX. -
XEP-0234: Jingle File Transfer
XEP-0234: Jingle File Transfer Peter Saint-Andre Lance Stout mailto:xsf@stpeter:im mailto:lance@andyet:com xmpp:peter@jabber:org xmpp:lance@lance:im http://stpeter:im/ 2019-06-19 Version 0.19.1 Status Type Short Name Deferred Standards Track jingle-ft This specification defines a Jingle application type for transferring a file from one entity to another. The protocol provides a modular framework that enables the exchange of information about the file to be transferred as well as the negotiation of parameters such as the transport to be used. Legal Copyright This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF). Permissions Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the ”Specification”), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specifi- cation, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or sub- stantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or pub- lisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. -
Listener Feedback #170
Security Now! Transcript of Episode #409 Page 1 of 40 Transcript of Episode #409 Listener Feedback #170 Description: Steve and Leo discuss the week's major security events and discuss questions and comments from listeners of previous episodes. They tie up loose ends, explore a wide range of topics that are too small to fill their own episode, clarify any confusion from previous installments, and present real world 'application notes' for any of the security technologies and issues we have previously discussed. High quality (64 kbps) mp3 audio file URL: http://media.GRC.com/sn/SN-409.mp3 Quarter size (16 kbps) mp3 audio file URL: http://media.GRC.com/sn/sn-409-lq.mp3 SHOW TEASE: It's time for Security Now!. Steve Gibson is here. What a great show ahead. Questions, answers. We'll talk more about PRISM, more insight there. You've got to stay tuned. This is the show to keep your privacy and security up. Security Now! is next. Leo Laporte: This is Security Now! with Steve Gibson, Episode 409, recorded June 19th, 2013: Your questions, Steve's answers, #170. It's time for Security Now!, the post-NSA edition. Steve Gibson is here, our Explainer in Chief, the guy who does all the security and privacy and is really our guru in that realm. Hello, Steve. Good to see you. Steve Gibson: Hey, Leo. Great to be with you again. And we have largely, as expected, a follow-up to last week's blockbuster theory of how PRISM works, as I expected. Actually I probably had double the number of email that I normally pull from the mailbag, which would have only been in half of the period of time. -
International Spy Museum
International Spy Museum Searchable Master Script, includes all sections and areas Area Location, ID, Description Labels, captions, and other explanatory text Area 1 – Museum Lobby M1.0.0.0 ΚΑΤΆΣΚΟΠΟΣ SPY SPION SPIJUN İSPİYON SZPIEG SPIA SPION ESPION ESPÍA ШПИОН Language of Espionage, printed on SCHPION MAJASUSI windows around entrance doors P1.1.0.0 Visitor Mission Statement For Your Eyes Only For Your Eyes Only Entry beyond this point is on a need-to-know basis. Who needs to know? All who would understand the world. All who would glimpse the unseen hands that touch our lives. You will learn the secrets of tradecraft – the tools and techniques that influence battles and sway governments. You will uncover extraordinary stories hidden behind the headlines. You will meet men and women living by their wits, lurking in the shadows of world affairs. More important, however, are the people you will not meet. The most successful spies are the unknown spies who remain undetected. Our task is to judge their craft, not their politics – their skill, not their loyalty. Our mission is to understand these daring professionals and their fallen comrades, to recognize their ingenuity and imagination. Our goal is to see past their maze of mirrors and deception to understand their world of intrigue. Intelligence facts written on glass How old is spying? First record of spying: 1800 BC, clay tablet from Hammurabi regarding his spies. panel on left side of lobby First manual on spy tactics written: Over 2,000 years ago, Sun Tzu’s The Art of War. 6 video screens behind glass panel with facts and images. -
XEP-0353: Jingle Message Initiation
XEP-0353: Jingle Message Initiation Philipp Hancke Peter Saint-Andre mailto:fippo@andyet:com mailto:xsf@stpeter:im xmpp:fippo@goodadvice:pages:de xmpp:peter@jabber:org http://stpeter:im/ 2021-03-04 Version 0.3.1 Status Type Short Name Deferred Standards Track jingle-message This specification provides a way for the initiator of a Jingle session to propose sending an invitation in an XMPP message stanza, thus taking advantage of message delivery semantics instead of sending IQ stanzas to all of the responder’s online resources or choosing a particular online resource. Legal Copyright This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF). Permissions Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the ”Specification”), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specifi- cation, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or sub- stantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or pub- lisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. -
Multi-User Jingle
Multi-User Jingle Sjoerd Simons Collabora Ltd, sponsored by NlNet LCA 2009 Multi-User Jingle XMPP protocol extension for initiating and managing multiparty voice and video conferences within an XMPP MUC using Jingle Jingle XMPP protocol extension for initiating and managing peer-to-peer media sessions between two XMPP entities XMPP I Extensible Messaging and Presence Protocol I The protocol formaly known as Jabber I XML streams I XMPP Core: RFC 3920 I XMPP IM: RFC 3921 I Extensions using XMPP Extension Proposals (XEP) XMPP JID Almost but not entirely unlike an e-mailaddress: I [email protected] I [email protected] I [email protected]/balcony Messages <message to='[email protected] ' from='juliet@example .com/balcony ' type='chat ' xml:lang=' en '> <body>Wherefore art thou, Romeo?</ body> </ message> Presence <presence from='romeo@montague. lit/orchard '> <show>dnd</show> <s t a t u s>Wooing Juliet</ s t a t u s> <c xmlns='http://jabber.org/protocol/caps' hash=' sha −1 ' node='http://telepathy .freedesktop.org/wiki/Muji' ver='iuNYhdSOy4nYDVPDhoTqCFubSz8='/> </ p r e s e n c e> Info/Query <iq xmlns='jabber:client ' to='juliet@example .com/balcony ' from='romeo@example. net/orchard ' id='2846139002 ' t y p e= ' g e t '> <query xmlns='http://jabber.org/protocol/disco#info ' node=' http://telepathy . freedesktop . org/wiki/Muji#iuNYhdSOy4nYDVPDhoTqCFubSz8=' /> </ i q> <iq xmlns='jabber:client ' to='romeo@example. net/orchard ' from='juliet@example .com/balcony ' id='2846139002 ' type='result '> <query xmlns='http://jabber.org/protocol/disco#info '> <identity category='client ' t y p e= ' pc ' name='Telepathy Gabble 0 .