fragment_downloaded_cb({"url":"security.html#api-user-considerations","fragment":"API user considerations\nUsers of the Tracker API and SPARQL interface are encouraged to make some\nconsiderations and take some precautions:\nDo not expose any endpoints that does not need exposing.\nFor local D-Bus endpoints, consider using a graph partitioning scheme that\nmakes it easy to policy the access to the data when accessed through the\nportal.\nAvoid the possibility of injection attacks. Use TrackerSparqlStatement\nand avoid string-based approaches to build SPARQL queries from user input.\nConsider that IRIs are susceptible to homograph attacks. Quoting\nhttps://www.w3.org/TR/sparql11-protocol/#policy-security:\nThe situations where this might be a source of confusion or mischief, or even\nbe possible depends on how those IRIs are created, used, displayed or\ninserted.\n\n\nDo not expose any endpoints that does not need exposing.\n\n\nFor local D-Bus endpoints, consider using a graph partitioning scheme that\nmakes it easy to policy the access to the data when accessed through the\nportal.\n\n\nAvoid the possibility of injection attacks. Use TrackerSparqlStatement\nand avoid string-based approaches to build SPARQL queries from user input.\n\n\nConsider that IRIs are susceptible to homograph attacks. Quoting\nhttps://www.w3.org/TR/sparql11-protocol/#policy-security:\nDifferent IRIs may have the same appearance. Characters in different scripts\nmay look similar (a Cyrillic \"о\" may appear similar to a Latin \"o\"). A\ncharacter followed by combining characters may have the same visual\nrepresentation as another character (LATIN SMALL LETTER E followed by\nCOMBINING ACUTE ACCENT has the same visual representation as LATIN SMALL\nLETTER E WITH ACUTE). Users of SPARQL must take care to construct queries\nwith IRIs that match the IRIs in the data. Further information about matching\nof similar characters can be found in Unicode Security Considerations\n[UNISEC] and Internationalized Resource Identifiers (IRIs) [RFC3987]\nSection 8.\n\nThe situations where this might be a source of confusion or mischief, or even\nbe possible depends on how those IRIs are created, used, displayed or\ninserted.\n\n\n"});