DOCSLIB.ORG

Techno-Social Platform for Sustainable Models and Value Generation in Commons-Based Peer Production in the Future Internet

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Techno-Social Platform for Sustainable Models and Value Generation in Commons-Based Peer Production in the Future Internet P2Pvalue Deliverable 1.2 P2Pvalue – Techno-social platform for sustainable models and value generation in commons-based peer production in the Future Internet Programme: FP7-ICT-2013-10 Project: 610961 Start date: 2013-10-01 Duration: 36 months Deliverable D1.2 [Theoretical synthesis: Final theoretical synthesis of WP1, including research reports on data collection] Submission date: 2014-07-31 Organisation name of lead contractor for this deliverable: Universitat Autònoma de Barcelona I P2Pvalue Deliverable 1.2 Dissemination Status PU Public x PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) ii P2Pvalue Deliverable 1.2 Document information 1.1 Author(s) -(in alphabetic order and by partners) Author Organisation E-mail Primavera De Filippi CNRS [email protected] Melanie Dulong de CNRS [email protected] Rosnay Francesca Musiani CNRS [email protected] Ignasi Capdevila P2PF [email protected] Marco Berlinguer Universitat [email protected] Autonoma de Barcelona (IGOP) Mayo Fuster Morell Universitat [email protected] (Deliverable and WP Autonoma de coordinator) Barcelona (IGOP) Jorge L Salcedo Universitat [email protected] Autonoma de Barcelona (IGOP) Wouter Tebbens Universitat [email protected] Autonoma de Barcelona (IGOP) Adam Arvidsson UMIL [email protected] Alessandro UMIL [email protected] Caliandro Alessandro Gandini UMIL [email protected] David Rosas U Surrey [email protected] 1.2 Other contributors -(in alphabetic order and by partners) Name Organisation E-mail James Burke P2PF [email protected] iii P2Pvalue Deliverable 1.2 Chris Pinchen P2PF [email protected] Kevin Flanagan P2PF [email protected] Karthik Iyer P2PF [email protected] Quim Brugué UAB [email protected] Rubén Martínez UAB [email protected] Joan Miró Artigas UAB [email protected] Joan Subirats Humet UAB [email protected] Javier Arroyo UCM [email protected] Samer Hassan UCM [email protected] Pablo Ojanguren UCM [email protected] Antonio Tapiador UCM [email protected] Antonio Tenorio UCM [email protected] Nigel Gilbert USurrey [email protected] 1.3 Document history Version# Date Change V0.1 22/07/2014 Starting version, template V0.2 Etc. V1.0 Approved version to be submitted to EU 1.4 Document data Keywords Common Based Peer Production (CBPP), P2P production , value, digital economy Editor address data [email protected] Delivery date 31/07/2014 1.5 Distribution list iv P2Pvalue Deliverable 1.2 Date Issue E-mail Consortium members [email protected] Project officer [email protected] EC archive CNECT-ICT- [email protected] v P2Pvalue Deliverable 1.2 P2Pvalue Consortium University Of Surrey (Coordinator) Centre National De La Recherche Scientifique Stichtung Peer To Peer Alternatives (P2P Foundation) Universitat Autònoma De Barcelona Universidad Complutense De Madrid Università Degli Studi Di Milano vi P2Pvalue Deliverable 1.2 Executive Summary Deliverable 1.3 Theoretical synthesis Mayo Fuster Morell (UAB) This executive summary has been divided into sections. First is a report on the performance of work as planned in DoW for WP1. Next is a presentation of research work developed including the synthesis of the main results, which is based on the triangulation of the results of the four researches conducted. Further developments are likewise included. As to the organization of the rest of the Deliverable, the first section provides the “Criteria of delimitation and typification of CBPP”. These criteria establish our common understanding of the CBPP phenomenon and define our unit of analysis. Executive summaries of theresearch developed as part of WP1 are also included as follows:Task 1.1 on the statistical analysis of CBPP cases, Task 1.2 on techno-legal analysis of cases based on decentralized infrastructure, Task 1.3 based on the digital ethnography of case studies, and Task 1.4 on participants survey. The annex includes the extended reports for each of these four areas of research. Methodological annexes are also provided in each research report. I. Report on Performance of work planned in DoW We have performed and completed the planned task as part of WP1 (see page 26 and 27 of DoW for a task description): The tasks planned were: Task 1.1 (UAB with input from UMIL, CNRS and UniS): Statistical analysis of a sample of 300 CBPP cases (1-11 months) Task 1.2 (CNRS with input from UCM, UniS and UAB): Technical analysis of CBPP software platforms (4-9 months) VII P2Pvalue Deliverable 1.2 Task 1.3 (UMIL): Digital Ethnography on value within CBPP (3-9 months) Task 1.4 (P2PF with input from UMIL and UAB): Survey of CBPP projects’ participants on value, rewards and institutional design (7-9 months) As planned, during the 11-14 months, we will complete Task 1.5 (UAB, UMIL, CNRS and P2PF): Selection of the case study communities and synthesis of theoretical findings (11-14 months). This Deliverable (1.3) provides a research report for each of these four research tasks. Deliverable 1.2 provides the design guidelines derived from them and Deliverable 1.1 provides the datasets generated. We have followed the presented plan in DoW and performed the described work. Two main relevant deviation from the work. On the one hand, we have done as much extended work building a directory of CBPP as expected. The P2Pvalue directory of CBPP (http://directory.p2pvalue.eu) was planned as a dataset of cases. However, we have given more functionalities and designed it as an open and collaborative research tool following CBPP principles. The reason for doing so was mainly functional. We considered it was easier to build a departing list of cases from which samples are drawn for the researchers. Additionally, the building of a CBPP resource as part of the research process has constituted a very interesting experience in order to rethink and apply the same knowledge emerging from the research on CBPP and to have insights from bringing them into practice. It is also an additional source for research dissemination. The methodological section of research report of Task 1.1 provide further explanation on how the directory has been used as a research tool. The other variation for the plan regards Task 1.2. and the techno-legal analysis. The plan for this task was to build the analysis over the statistical sample of 300 cases in Task 1.1. Instead of developing the techno-legal analysis over the 300 cases statistical sample based on any type of infrastructure, we conducted case studies based on decentralized infrastructure. The change was based on two main reasons: firstly, to deepen our knowledge on decentralized infrastructures. There are very viii P2Pvalue Deliverable 1.2 few case studies of online platforms relying on decentralized architectures and we need this knowledge in order to rethink the design of P2Pvalue platform as it is based on decentralized infrastructure. Case studies provide a deep analysis that we considered more useful in this regard. On the other hand, time was an important limitation. The changes in the WP1 calendar at the negotiation meeting (advancing the deliverables' deadlines) meant that the statistical analyses were going to be ready too late to be able to perform a deep techno-legal analysis in time for the deliverables. Time constraints were the main problem we have encountered throughout the development of the work. Initially, the tasks were going to be performed during 4 more months for Tasks 1.1-1.4. However, during the negotiation meeting, we agreed to shorten them in order to submit the Deliverable during the first project year. This became a serious problem as we had to work fast and under significant time pressure. For Task 1.5 (Selection of the case study communities and synthesis of theoretical findings), we have developed an initial triangulation of results between the several tasks, provided in the following section of this Executive summary. We have also completed a pre-selection of communities and contacted them. In the next months, we will further develop Task 1.5 to explore the triangulation of the results of the statistical analysis, techno-legal analysis, digital ethnography and participant surveys. Theory building will continue as part of WP2 and WP4. At the moment of presenting the deliverables, we have accomplished the agreed objectives for WP1 (see the following italic text with the presentation of WP1 objectives as presented in DoW). Presentation of WP1 objectives (as presented in DoW) Objectives To identify, frame and classify on-going CBPPs as a form of value creation and to identify the institutional and technical design features, value ix P2Pvalue Deliverable 1.2 metrics and reward mechanisms that favour CBPP value creation. More concretely, the objectives of WP1 are to: 1. Build and analyse a large sample of on-going CBPPs using Ostrom’s institutional and developmental framework to extract the conditions that favour value creation in CBPP. 2. Analyse systems of value metrics and rewards in CBPP communities through digital ethnography and a survey of participants. 3. Select the communities that will join the P2Pvalue platform in WP4. 4. Propose guidelines for institutional design, value metrics, reward mechanisms, and technical features to be considered in WP2 for the implementation of the P2Pvalue platform. Objectives 1 and 2 are reported in this Deliverable 1.3. Objective 4 is presented in Deliverable 1.2. on design guidelines derived from the research. Objective 3 has been developed and will be further developed as part of Task 1.5 in the final months of WP1 (until December 2014). In order to coordinate WP1, we held a three-day research seminar in Barcelona on January 2014.
Load more

Recommended publications
  • Cisco SCA BB Protocol Reference Guide
    Cisco Service Control Application for Broadband Protocol Reference Guide Protocol Pack #60 August 02, 2018 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Inside Dropbox: Understanding Personal Cloud Storage Services
    Inside Dropbox: Understanding Personal Cloud Storage Services → Idilio Drago → Marco Mellia → Maurizio M. Munafo` → Anna Sperotto → Ramin Sadre → Aiko Pras IRTF – Vancouver Motivation and goals 1 Personal cloud storage services are already popular Dropbox in 2012 “the largest deployed networked file system in history” “over 50 million users – one billion files every 48 hours” Little public information about the system How does Dropbox work? What are the potential performance bottlenecks? Are there typical usage scenarios? Methodology – How does Dropbox work? 2 Public information Native client, Web interface, LAN-Sync etc. Files are split in chunks of up to 4 MB Delta encoding, deduplication, encrypted communication To understand the client protocol MITM against our own client Squid proxy, SSL-bump and a self-signed CA certificate Replace a trusted CA certificate in the heap at run-time Proxy logs and decrypted packet traces How does Dropbox (v1.2.52) work? 3 Clear separation between storage and meta-data/client control Sub-domains identifying parts of the service sub-domain Data-center Description client-lb/clientX Dropbox Meta-data notifyX Dropbox Notifications api Dropbox API control www Dropbox Web servers d Dropbox Event logs dl Amazon Direct links dl-clientX Amazon Client storage dl-debugX Amazon Back-traces dl-web Amazon Web storage api-content Amazon API Storage HTTP/HTTPs in all functionalities How does Dropbox (v1.2.52) work? 4 Notification Kept open Not encrypted Device ID Folder IDs How does Dropbox (v1.2.52) work? 4 Client control Login File hash Meta-data How does Dropbox (v1.2.52) work? 4 Storage Amazon EC2 Retrieve vs.
    [Show full text]
  • Skype Voip Service- Architecture and Comparison Hao Wang Institute of Communication Networks and Computer Engineering University of Stuttgart Mentor: Dr.-Ing
    INFOTECH Seminar Advanced Communication Services (ACS), 2005 Skype VoIP service- architecture and comparison Hao Wang Institute of Communication Networks and Computer Engineering University of Stuttgart Mentor: Dr.-Ing. S. Rupp ABSTRACT Skype is a peer-to-peer (P2P) overlay network for VoIP and other applications, developed by KaZaa in 2003. Skype can traverse NAT and firewall more efficiently than traditional VoIP networks and it offers better voice quality. To find and locate users, Skype uses “supernodes” that are running on peer machines. In contrast, traditional systems use fixed central servers. Also Skype uses encrypted media channel to protect the dada. The main contribution of this article is illustrating the architecture and components of Skype networks and basically analyzing key Skype functions such as login, NAT and firewall traversal. Furthermore, it contains comparisons of Skype networks with VoIP networks regarding different scenarios. On that basis it reveals some reasons why Skype has much better performance than previous VoIP products. Keywords Voice over IP (VoIP), Skype, Peer-to-peer (p2p), Super Node (SN) 1. Introduction It is expected that real-time person-to-person communication, like IP telephony (VoIP), instant messaging, voice, video and data collaboration will be the next big wave of Internet usage. VoIP refers to technology that enables routing of voice conversations over the Internet or any other IP network. Another technology is peer-to-peer, which is used for sharing content like audio, video, data or anything in digital format. Skype is a combination of these two technologies. It has much better performance by making use of advantages of both technologies.
    [Show full text]
  • Devicelock® DLP 8.3 User Manual
    DeviceLock® DLP 8.3 User Manual © 1996-2020 DeviceLock, Inc. All Rights Reserved. Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means for any purpose other than the purchaser’s personal use without the prior written permission of DeviceLock, Inc. Trademarks DeviceLock and the DeviceLock logo are registered trademarks of DeviceLock, Inc. All other product names, service marks, and trademarks mentioned herein are trademarks of their respective owners. DeviceLock DLP - User Manual Software version: 8.3 Updated: March 2020 Contents About This Manual . .8 Conventions . 8 DeviceLock Overview . .9 General Information . 9 Managed Access Control . 13 DeviceLock Service for Mac . 17 DeviceLock Content Security Server . 18 How Search Server Works . 18 ContentLock and NetworkLock . 20 ContentLock and NetworkLock Licensing . 24 Basic Security Rules . 25 Installing DeviceLock . .26 System Requirements . 26 Deploying DeviceLock Service for Windows . 30 Interactive Installation . 30 Unattended Installation . 35 Installation via Microsoft Systems Management Server . 36 Installation via DeviceLock Management Console . 36 Installation via DeviceLock Enterprise Manager . 37 Installation via Group Policy . 38 Installation via DeviceLock Enterprise Server . 44 Deploying DeviceLock Service for Mac . 45 Interactive Installation . 45 Command Line Utility . 47 Unattended Installation . 48 Installing Management Consoles . 49 Installing DeviceLock Enterprise Server . 52 Installation Steps . 52 Installing and Accessing DeviceLock WebConsole . 65 Prepare for Installation . 65 Install the DeviceLock WebConsole . 66 Access the DeviceLock WebConsole . 67 Installing DeviceLock Content Security Server . 68 Prepare to Install . 68 Start Installation . 70 Perform Configuration and Complete Installation . 71 DeviceLock Consoles and Tools .
    [Show full text]
  • Insight Into the Gtalk Protocol
    1 Insight into the Gtalk Protocol Riyad Alshammari and A. Nur Zincir-Heywood Dalhousie University, Faculty of Computer Science Halifax NS B3H 1W5, Canada (riyad,zincir)@cs.dal.ca Abstract Google talk (Gtalk) is an instant messeger and voice over IP client developed by Google in 2005. Gtalk can work across firewalls and has very good voice quality. It encrypts calls end-to-end, and stores user information in a centralized fashion. This paper analyzes fundamental Gtalk functions such as login, firewall traversal, and call establishment under different network scenarios. The analysis is performed by both active and passive measurement techniques to understand the Gtalk network traffic. Based on our analysis, we devised algorithms for login and call establishment processes as well as data flow models. I. INTRODUCTION Voice over IP (VoIP) is becoming a major communication service for enterprises and individuals since the cost of VoIP calls is low and the voice quality is getting better. To date, there are many VoIP products that are able to provide high call quality such as Skype [1], Google Talk (Gtalk) [2], Microsoft Messenger (MSN) [3], and Yahoo! Messenger (YMSG) [4]. However, few information has been documented about protocol design used by these VoIP clients since the protocols are not standardized, many of them are proprietary, and the creators of these softwares want to keep their information confidential and protect their protocol design form competitors. In this paper, we have generated and captured network traffic in order to determine the broad characteristics of one of the most recent and fast growing VoIP applications, Google Talk.
    [Show full text]
  • 4-BAY RACKMOUNT NAS Technical Specifications
    4-BAY RACKMOUNT NAS Technical Specifications Operating System Seagate® NAS OS (embedded Linux) Number of Drive Bays 4 hot-swappable 3.5-inch SATA II/SATA III Processor Dual-core 2.13GHz Intel® 64-bit Atom™ processor Memory 2GB DDR III Networking Two (2) 10/100/1000 Base-TX (Gigabit Ethernet) • Two (2) USB 3.0 (rear) • Two (2) USB 2.0 (rear) External Ports • One (1) eSATA (rear) • One (1) USB 2.0 (front) Hard Drive Capacity Seagate NAS HDD 2TB, 3TB, 4TB for preconfigured models Total Capacity 4TB, 8TB, 12TB, 16TB Compatible Drives 3.5-inch SATA II or SATA III (see NAS Certified Drive list PDF for more details) Power 100V to 240V AC, 50/60Hz, 180W Power Supply and • Sleep mode for power saving • Scheduled power on/off Power Management • Wake-on-LAN Cooling Management Two (2) fans Transfer Rate 200MB/s reads and writes1 Network Protocols CIFS/SMB, NFS v3, AFP, HTTP(s), FTP, sFTP, iSCSI, Print serve, failover and load balancing and Services (LACP 802.3ad), Wuala file system integration (W:/ network drive), Active Directory™ • RAID 0, 1, 5, 6, 10 RAID • Hot spare • SimplyRAID™ technology with mixed capacity support, volume expansion and migration • Web-based interface through http/https • Hardware monitoring (S.M.A.R.T., casing cooling and temperature, CPU and RAM load) Management • Log management and email notification • NAS OS Installer for diskless setup, data recovery and restore to factory settings • Product discovery with Seagate Network Assistant 1 Tested in RAID 5 configuration utilizing load balancing for Ethernet ports. Actual performance may vary depending on system environment.
    [Show full text]
  • The Application Usage and Risk Report an Analysis of End User Application Trends in the Enterprise
    The Application Usage and Risk Report An Analysis of End User Application Trends in the Enterprise 8th Edition, December 2011 Palo Alto Networks 3300 Olcott Street Santa Clara, CA 94089 www.paloaltonetworks.com Table of Contents Executive Summary ........................................................................................................ 3 Demographics ............................................................................................................................................. 4 Social Networking Use Becomes More Active ................................................................ 5 Facebook Applications Bandwidth Consumption Triples .......................................................................... 5 Twitter Bandwidth Consumption Increases 7-Fold ................................................................................... 6 Some Perspective On Bandwidth Consumption .................................................................................... 7 Managing the Risks .................................................................................................................................... 7 Browser-based Filesharing: Work vs. Entertainment .................................................... 8 Infrastructure- or Productivity-Oriented Browser-based Filesharing ..................................................... 9 Entertainment Oriented Browser-based Filesharing .............................................................................. 10 Comparing Frequency and Volume of Use
    [Show full text]
  • Building Large-Scale Distributed Applications on Top of Self-Managing Transactional Stores
    Building large-scale distributed applications on top of self-managing transactional stores June 3, 2010 Peter Van Roy with help from SELFMAN partners Overview Large-scale distributed applications Application structure: multi-tier with scalable DB backend Distribution structure: peer-to-peer or cloud-based DHTs and transactions Basics of DHTs Data replication and transactions Scalaris and Beernet Programming model and applications CompOz library and Kompics component model DeTransDraw and Distributed Wikipedia Future work Mobile applications, cloud computing, data-intensive computing Programming abstractions for large-scale distribution Application structure What can be a general architecture for large-scale distributed applications? Start with a database backend (e.g., IBM’s “multitier”) Make it distributed with distributed transactional interface Keep strong consistency (ACID properties) Allow large numbers of concurrent transactions Horizontal scalability is the key Vertical scalability is a dead end “NoSQL”: Buzzword for horizontally scalable databases that typically don’t have a complete SQL interface Key/value store or column-oriented ↑ our choice (simplicity) The NoSQL Controversy NoSQL is a current trend in non-relational databases May lack table schemas, may lack ACID properties, no join operations Main advantages are excellent performance, with good horizontal scalability and elasticity (ideal fit to clouds) SQL databases have good vertical scalability but are not elastic Often only weak consistency guarantees, such as eventual consistency (e.g., Google BigTable) Some exceptions: Cassandra also provides strong consistency, Scalaris and Beernet provide a key-value store with transactions and strong consistency Distribution structure Two main infrastructures for large-scale applications Peer-to-peer: use of client machines ← our choice (loosely coupled) Very popular style, e.g., BitTorrent, Skype, Wuala, etc.
    [Show full text]
  • Mass Surveillance
    Mass Surveillance Mass Surveillance What are the risks for the citizens and the opportunities for the European Information Society? What are the possible mitigation strategies? Part 1 - Risks and opportunities raised by the current generation of network services and applications Study IP/G/STOA/FWC-2013-1/LOT 9/C5/SC1 January 2015 PE 527.409 STOA - Science and Technology Options Assessment The STOA project “Mass Surveillance Part 1 – Risks, Opportunities and Mitigation Strategies” was carried out by TECNALIA Research and Investigation in Spain. AUTHORS Arkaitz Gamino Garcia Concepción Cortes Velasco Eider Iturbe Zamalloa Erkuden Rios Velasco Iñaki Eguía Elejabarrieta Javier Herrera Lotero Jason Mansell (Linguistic Review) José Javier Larrañeta Ibañez Stefan Schuster (Editor) The authors acknowledge and would like to thank the following experts for their contributions to this report: Prof. Nigel Smart, University of Bristol; Matteo E. Bonfanti PhD, Research Fellow in International Law and Security, Scuola Superiore Sant’Anna Pisa; Prof. Fred Piper, University of London; Caspar Bowden, independent privacy researcher; Maria Pilar Torres Bruna, Head of Cybersecurity, Everis Aerospace, Defense and Security; Prof. Kenny Paterson, University of London; Agustín Martin and Luis Hernández Encinas, Tenured Scientists, Department of Information Processing and Cryptography (Cryptology and Information Security Group), CSIC; Alessandro Zanasi, Zanasi & Partners; Fernando Acero, Expert on Open Source Software; Luigi Coppolino,Università degli Studi di Napoli; Marcello Antonucci, EZNESS srl; Rachel Oldroyd, Managing Editor of The Bureau of Investigative Journalism; Peter Kruse, Founder of CSIS Security Group A/S; Ryan Gallagher, investigative Reporter of The Intercept; Capitán Alberto Redondo, Guardia Civil; Prof. Bart Preneel, KU Leuven; Raoul Chiesa, Security Brokers SCpA, CyberDefcon Ltd.; Prof.
    [Show full text]
  • On the Security of Cloud Storage Services
    FRAUNHOFER INSTITUTE FOR SECURE INFORMATION TECHNOLOGY ON THE SECURITY OF CLOUD Sharing of data was a problem for CloudMe, Dropbox, Team- Summary Individuals or companies considering to use cloud STORAGE SERVICES Drive and Wuala. Problems occur if fi les are shared with non- storage services are advised to check whether a cloud provider MANAGEMENT SUMMARY subscribers by a long, unpredictable URL. CloudMe does not meets these security requirements. obfuscate this URL adequately. Dropbox gives an unclear de- scription wrt to sharing details, TeamDrive is weak when disin- In addition, it is worthwhile to consider using more than one viting a group member and Wuala enables information gathe- service to reduce the impacts of service downtime. Further, ring by including the user name in public URLs. CloudMe does calculation of the time to recover all data from the cloud is re- not prevent search engines from accessing the workspace. commended. Depending on the individual amount of data, this may take several days. Having a plan for a provider Deduplication was a problem for Mozy and Wuala, because change in the future reduces the dependancy on a particular in some cases it is possible to ask the cloud storage provider provider (provider lock-in). This will be relevant, for example, if whether a fi le is already stored or not. the chosen provider is getting too expensive or is not longer compliant with governmental rules. As a major result, the stu- Data confi dentiality can be improved by users by encrypting dy shows that most of the analyzed cloud storage providers their data locally before uploading it to the cloud.
    [Show full text]
  • Online Research Tools
    Online Research Tools A White Paper Alphabetical URL DataSet Link Compilation By Marcus P. Zillman, M.S., A.M.H.A. Executive Director – Virtual Private Library [email protected] Online Research Tools is a white paper link compilation of various online tools that will aid your research and searching of the Internet. These tools come in all types and descriptions and many are web applications without the need to download software to your computer. This white paper link compilation is constantly updated and is available online in the Research Tools section of the Virtual Private Library’s Subject Tracer™ Information Blog: http://www.ResearchResources.info/ If you know of other online research tools both free and fee based feel free to contact me so I may place them in this ongoing work as the goal is to make research and searching more efficient and productive both for the professional as well as the lay person. Figure 1: Research Resources – Online Research Tools 1 Online Research Tools – A White Paper Alpabetical URL DataSet Link Compilation [Updated: August 26, 2013] http://www.OnlineResearchTools.info/ [email protected] eVoice: 800-858-1462 © 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 Marcus P. Zillman, M.S., A.M.H.A. Online Research Tools: 12VPN - Unblock Websites and Improve Privacy http://12vpn.com/ 123Do – Simple Task Queues To Help Your Work Flow http://iqdo.com/ 15Five - Know the Pulse of Your Company http://www.15five.com/ 1000 Genomes - A Deep Catalog of Human Genetic Variation http://www.1000genomes.org/
    [Show full text]
  • Sailpoint Direct Connectors Administration and Configuration Guide for Version 7.3
    SailPoint Direct Connectors Version 7.3 Administration and Configuration Guide Copyright © 2018 SailPoint Technologies, Inc., All Rights Reserved. SailPoint Technologies, Inc. makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. SailPoint Technologies shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Restricted Rights Legend. All rights are reserved. No part of this document may be published, distributed, reproduced, publicly displayed, used to create derivative works, or translated to another language, without the prior written consent of SailPoint Technologies. The information contained in this document is subject to change without notice. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 for other agencies. Regulatory/Export Compliance. The export and re-export of this software is controlled for export purposes by the U.S. Government. By accepting this software and/or documentation, licensee agrees to comply with all U.S. and foreign export laws and regulations as they relate to software and related documentation. Licensee will not export or re-export outside the United States software or documentation, whether directly or indirectly, to any Prohibited Party and will not cause, approve or otherwise intentionally facilitate others in so doing.
    [Show full text]