Keyword-Based Delegable Proofs of Storage

Cloud users (clients) with limited storage capacity at their end can outsource bulk data to the cloud storage server. A client can later access her data by downloading the required data files. However, a large fraction of the data files the client outsources to the server is often archival in nature that the client uses for backup purposes and accesses less frequently. An untrusted server can thus delete some of these archival data files in order to save some space (and allocate the same to other clients) without being detected by the client (data owner). Proofs of storage enable the client to audit her data files uploaded to the server in order to ensure the integrity of those files. In this work, we introduce one type of (selective) proofs of storage that we call keyword-based delegable proofs of storage, where the client wants to audit all her data files containing a specific keyword (e.g., "important"). Moreover, it satisfies the notion of public verifiability where the client can delegate the auditing task to a third-party auditor who audits the set of files corresponding to the keyword on behalf of the client. We formally define the security of a keyword-based delegable proof-of-storage protocol. We construct such a protocol based on an existing proof-of-storage scheme and analyze the security of our protocol. We argue that the techniques we use can be applied atop any existing publicly verifiable proof-of-storage scheme for static data. Finally, we discuss the efficiency of our construction.Comment: A preliminary version of this work has been published in International Conference on Information Security Practice and Experience (ISPEC 2018

The Parkes Observatory Pulsar Data Archive

The Parkes pulsar data archive currently provides access to 144044 data files obtained from observations carried out at the Parkes observatory since the year 1991. Around 10^5 files are from surveys of the sky, the remainder are observations of 775 individual pulsars and their corresponding calibration signals. Survey observations are included from the Parkes 70cm and the Swinburne Intermediate Latitude surveys. Individual pulsar observations are included from young pulsar timing projects, the Parkes Pulsar Timing Array and from the PULSE@Parkes outreach program. The data files and access methods are compatible with Virtual Observatory protocols. This paper describes the data currently stored in the archive and presents ways in which these data can be searched and downloaded.Comment: Accepted by PAS

The Mark 3 data base handler

A data base handler which would act to tie Mark 3 system programs together is discussed. The data base handler is written in FORTRAN and is implemented on the Hewlett-Packard 21MX and the IBM 360/91. The system design objectives were to (1) provide for an easily specified method of data interchange among programs, (2) provide for a high level of data integrity, (3) accommodate changing requirments, (4) promote program accountability, (5) provide a single source of program constants, and (6) provide a central point for data archiving. The system consists of two distinct parts: a set of files existing on disk packs and tapes; and a set of utility subroutines which allow users to access the information in these files. Users never directly read or write the files and need not know the details of how the data are formatted in the files. To the users, the storage medium is format free. A user does need to know something about the sequencing of his data in the files but nothing about data in which he has no interest

Strip and load data

The method of taking batch data files and loading these files into the ADABAS data base management system (DBMS) is examined. This strip and load process allows the user to quickly become productive. Techniques for data fields and files definition are also included

Flexibility of Various Nickel-Titanium Rotary Endodontic Files

Introduction: Nickel-titanium rotary files were originally developed to allow for greater flexibility when instrumenting root canals. The increased flexibility of nickel-titanium instruments allowed operators to negotiate canal curvatures with greater ease. File design is continually changing. Manufacturers are trying to produce files that will work more efficiently and safely. Knowing the properties of files marketed is especially important in helping to choose an appropriate file system. Current ISO standards require force measurements at a static point along the file. The purpose of this study was to evaluate the flexibility of four different nickel-titanium files at three different points along the file. Materials and Methods: Flexibility of four different nickel-titanium rotary files (EndoSequence, ProFile, Vortex, and Vortex Blue) was measured. Each file was clamped at 3mm, 5mm, or 7mm (n = 10/length/file) and a universal testing machine was used to bend the files to a maximum deflection of 4.5mm. All data were statistically analyzed by two-way analysis of variance and post-hoc Tukey test (P = 0.05) to determine any significant differences. Results: Statistically significant (P \u3c 0.05) differences were present. In general, ProFile was the stiffest, displaying the greatest force and bending moment values. Vortex Blue was significantly more flexible, with lower force needed for deflection and bending moments. Conclusion: Vortex Blue files showed greater flexibility compared with the other nickel-titanium rotary files studied

The online buffer

Copyright @ 2009 MICEThis is a discussion document regarding the proposed use of the Online Buffer. The Online Buffer is used to store locally the RAW data files created by the Event Builder, before they are uploaded to Castor by the data mover. The files may also be used by the online monitoring and reconstruction activities. At the Trigger-DAQ-Controls Review, the reviewers warned that this three-way activity might saturate the disks, and also that the file uploads to the Grid could conflict with the writing of DAQ data. It was proposed to ameliorate this by splitting the buffer into a set of independent volumes into which the DAQ data would be written on a round-robin basis; outgoing files would meanwhile be read only from one of the other volumes. Further, files being uploaded to the Grid would be staged on the transfer box’ system disk, as the (local) staging process is expected to be more deterministic and easier to control than transfers across the WAN

Standardization of power system protection settings using IEC 61850 for improved interoperability

One of the potential benefits of smart grid development is that data becomes more open and available for use by multiple applications. Many existing protection relays use proprietary formats for storing protection settings. This paper proposes to apply the IEC 61850 data model and System Configuration description Language (SCL), which are formally defined, to represent protection settings. Protection setting files in proprietary formats are parsed using rule-based reasoning, mapped to the IEC 61850 data model, and exported as SCL files. An important application of using SCL-based protection setting files is to achieve protection setting interoperability, which could bring multiple compelling benefits, such as significantly streamlining the IED configuration process and releasing utilities from being “locked in” to one particular vendor. For this purpose, this paper proposes a uniform configuration process for future IEDs. The challenges involved in the implementation of the proposed approach are discussed and possible solutions are presented