<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    <responseDate>2026-04-17T17:44:59.011Z</responseDate>
    <request verb="GetRecord" identifier="ezaposleni.singidunum.ac.rs/rest/sciNaucniRezultati/oai:1:685" metadataPrefix="dim">http://ezaposleni.singidunum.ac.rs/rest/sciNaucniRezultati/oai</request>
    <GetRecord>
        <record>
            <header>
                <identifier>ezaposleni.singidunum.ac.rs/rest/sciNaucniRezultati/oai:1:685</identifier>
                <datestamp>2013-11-03T15:49:36Z</datestamp>
                <setSpec>1</setSpec>
            </header>
            <metadata>
                <dim:dim>
                    <dim:field mdschema="dc" element="title" lang="en">Using Cryptology Models for Protecting PHP Source Code</dim:field>
                    <dim:field mdschema="dc" element="date" qualifier="issued">2013</dim:field>
                    <dim:field mdschema="dc" element="identifier" qualifier="uri">http://ezaposleni.singidunum.ac.rs/rest/sciNaucniRezultati/oai/record/1/685</dim:field>
                    <dim:field mdschema="dc" element="contributor" qualifier="author" authority="orcid::0000-0002-5564-8344" confidence="-1">A. Jevremović</dim:field>
                    <dim:field mdschema="dc" element="contributor" qualifier="author" authority="id:4912" confidence="-1">N. Ristić</dim:field>
                    <dim:field mdschema="dc" element="contributor" qualifier="author" authority="orcid::0000-0001-6136-1895" confidence="-1">M. Veinović</dim:field>
                    <dim:field mdschema="dc" element="description" qualifier="abstract">Protecting PHP scripts from unwanted use, copying and modifications is a big issue today. Existing solutions
on source code level are mostly working as obfuscators, they are free, and they are not providing any serious protection.
Solutions that encode opcode are more secure, but they are commercial and require closed-source proprietary PHP
interpreter&amp;apos;s extension. Additionally, encoded opcode is not compatible with future versions of interpreters which imply
re-buying encoders from the authors. Finally, if extension source-code is compromised, all scripts encoded with that
solution are compromised too. In this paper, we will present a new model for free and open-source PHP script protection
solution. Protection level provided by the proposed solution is equal to protection level of commercial solutions. Model is
based on conclusions from use of standard cryptology models for analysis of strengths and weaknesses of the existing
solutions, when a scripts protection is seen as secure communication channel in the cryptology.</dim:field>
                    <dim:field mdschema="dc" element="type">conferenceObject</dim:field>
                    <dim:field mdschema="dc" element="citation" qualifier="spage">332</dim:field>
                    <dim:field mdschema="dc" element="citation" qualifier="epage">336</dim:field>
                    <dim:field mdschema="dc" element="identifier" qualifier="doi">10.1063/1.4825491</dim:field>
                    <dim:field mdschema="dc" element="source">AIP Conf. Proc. 1558</dim:field>
                </dim:dim>
            </metadata>
        </record>
    </GetRecord>
</OAI-PMH>
