===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
keystone-18.0.0/doc/source/contributor/service-catalog.rst-154-
keystone-18.0.0/doc/source/contributor/service-catalog.rst:155:Similarly, ``https://object-store.example.com/v1/KEY_\$(project_id)s`` (which
keystone-18.0.0/doc/source/contributor/service-catalog.rst-156-would ultimately be rendered to clients as a project-specific URL, such as
##############################################
keystone-18.0.0/releasenotes/notes/bug-1641645-516709f9da3de26f.yaml-5- RBAC protection was removed from the `Self-service change user password` API
keystone-18.0.0/releasenotes/notes/bug-1641645-516709f9da3de26f.yaml:6: (``/v3/user/$user_id/password``), meaning, a user can now change their password
keystone-18.0.0/releasenotes/notes/bug-1641645-516709f9da3de26f.yaml-7- without a token specified in the ``X-Auth-Token`` header. This change will
##############################################
keystone-18.0.0/releasenotes/notes/catalog_project_id-519f5a70f9f7c4c6.yaml-2-deprecations:
keystone-18.0.0/releasenotes/notes/catalog_project_id-519f5a70f9f7c4c6.yaml:3: - Use of ``$(tenant_id)s`` in the catalog endpoints is deprecated in favor
keystone-18.0.0/releasenotes/notes/catalog_project_id-519f5a70f9f7c4c6.yaml:4: of ``$(project_id)s``.
keystone-18.0.0/releasenotes/notes/catalog_project_id-519f5a70f9f7c4c6.yaml-5-features:
keystone-18.0.0/releasenotes/notes/catalog_project_id-519f5a70f9f7c4c6.yaml:6: - Keystone supports ``$(project_id)s`` in the catalog. It works the same as
keystone-18.0.0/releasenotes/notes/catalog_project_id-519f5a70f9f7c4c6.yaml:7: ``$(tenant_id)s``. Use of ``$(tenant_id)s`` is deprecated and catalog
keystone-18.0.0/releasenotes/notes/catalog_project_id-519f5a70f9f7c4c6.yaml:8: endpoints should be updated to use ``$(project_id)s``.
keystone-18.0.0/releasenotes/notes/catalog_project_id-519f5a70f9f7c4c6.yaml-9-
##############################################
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po-483-msgid ""
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po:484:"Keystone supports ``$(project_id)s`` in the catalog. It works the same as ``"
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po:485:"$(tenant_id)s``. Use of ``$(tenant_id)s`` is deprecated and catalog "
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po:486:"endpoints should be updated to use ``$(project_id)s``."
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po-487-msgstr ""
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po:488:"Keystone supports ``$(project_id)s`` in the catalogue. It works the same as "
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po:489:"``$(tenant_id)s``. Use of ``$(tenant_id)s`` is deprecated and catalogue "
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po:490:"endpoints should be updated to use ``$(project_id)s``."
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po-491-
##############################################
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po-1294-msgid ""
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po:1295:"Use of ``$(tenant_id)s`` in the catalog endpoints is deprecated in favor of "
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po:1296:"``$(project_id)s``."
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po-1297-msgstr ""
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po:1298:"Use of ``$(tenant_id)s`` in the catalogue endpoints is deprecated in favour "
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po:1299:"of ``$(project_id)s``."
keystone-18.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po-1300-
##############################################
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po-432-msgid ""
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po:433:"Keystone supports ``$(project_id)s`` in the catalog. It works the same as ``"
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po:434:"$(tenant_id)s``. Use of ``$(tenant_id)s`` is deprecated and catalog "
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po:435:"endpoints should be updated to use ``$(project_id)s``."
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po-436-msgstr ""
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po:437:"Keystone はカタログでの ``$(project_id)s`` をサポートしました。これは、``"
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po:438:"$(tenant_id)s`` と同じ動作をします。``$(tenant_id)s`` は非推奨になり、カタロ"
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po:439:"グのエンドポイントは、``$(project_id)s`` が使用されるようになります。"
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po-440-
##############################################
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po-1225-msgid ""
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po:1226:"Use of ``$(tenant_id)s`` in the catalog endpoints is deprecated in favor of "
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po:1227:"``$(project_id)s``."
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po-1228-msgstr ""
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po:1229:"カタログエンドポイントでの ``$(tenant_id)s`` の使用は非推奨となり、 ``"
keystone-18.0.0/releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po-1230-"$(project_id)s`` になりました。"
##############################################
keystone-18.0.0/tools/test-setup.sh-45-root_roles=$(sudo -H -u postgres psql -t -c "
keystone-18.0.0/tools/test-setup.sh:46: SELECT 'HERE' from pg_roles where rolname='$DB_USER'")
keystone-18.0.0/tools/test-setup.sh-47-if [[ ${root_roles} == *HERE ]];then
##############################################
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh-7-
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh:8:TOKEN=`gawk 'match ($0, /^admin_token\s?=\s?(.*)/, ary){ print ary[1]}' /etc/keystone/keystone.conf`
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh-9-export SERVICE_TOKEN=${TOKEN:-"ADMIN"}
##############################################
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh-19-create_role() {
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh:20: id=`keystone role-list | grep " $1 " | awk '{ print $2 }'`
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh-21- if [ -z $id ]; then
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh:22: id=`keystone role-create --name=$1 | grep " id " | awk '{ print $4 }'`
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh-23- echo "Created role $1 with id $id"
##############################################
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh-37-
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh:38:ADMIN_TENANT=`keystone tenant-create --name=admin | awk '/ id / { print $4 }'`
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh:39:DEMO_TENANT=`keystone tenant-create --name=demo | awk '/ id / { print $4 }'`
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh:40:SERVICE_TENANT=`keystone tenant-create --name=service | awk '/ id / { print $4 }'`
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh-41-
##############################################
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh-58-keystone service-create --name=nova --type=compute --description="Nova Compute Service"
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh:59:NOVA_USER=`keystone user-create --name=nova --pass="nova" --email=nova@example.com | awk '/ id / { print $4 }'`
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh-60-keystone user-role-add --user $NOVA_USER --role $ADMIN_ROLE --tenant_id $SERVICE_TENANT
##############################################
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh-62-keystone service-create --name=glance --type=image --description="Glance Image Service"
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh:63:GLANCE_USER=`keystone user-create --name=glance --pass="glance" --email=glance@example.com | awk '/ id / { print $4 }'`
keystone-18.0.0/debian/docs/scripts/keystone.base-deployment.sh-64-keystone user-role-add --user $GLANCE_USER --role $ADMIN_ROLE --tenant_id $SERVICE_TENANT
##############################################
keystone-18.0.0/debian/keystone.postinst.in-57- # Validate that the choosen endpoint is an IPv4, IPv6 or FQDN
keystone-18.0.0/debian/keystone.postinst.in:58: KEYSTONE_ENDPOINT_IP=`echo "${RET}" | egrep ${REG_ENDPOINT_IPV4_REGEX}` || true
keystone-18.0.0/debian/keystone.postinst.in-59- if [ -z "${KEYSTONE_ENDPOINT_IP}" ] ; then
keystone-18.0.0/debian/keystone.postinst.in:60: KEYSTONE_ENDPOINT_IP=`echo "${RET}" | egrep ${REG_ENDPOINT_IPV6_REGEX}` || true
keystone-18.0.0/debian/keystone.postinst.in-61- if [ -z ${KEYSTONE_ENDPOINT_IP} ] ; then
keystone-18.0.0/debian/keystone.postinst.in:62: KEYSTONE_ENDPOINT_IP=`echo ${RET} | egrep ${REG_ENDPOINT_FQDN_REGEX}` || true
keystone-18.0.0/debian/keystone.postinst.in-63- if [ -z ${KEYSTONE_ENDPOINT_IP} ] ; then
##############################################
keystone-18.0.0/debian/keystone.postinst.in-70- # Validate that the region name has only chars, dashes and dots
keystone-18.0.0/debian/keystone.postinst.in:71: my_REGION_NAME=`echo "${REGION_NAME}" | egrep ${REG_ENDPOINT_REGION_REGEX}` || true
keystone-18.0.0/debian/keystone.postinst.in-72- if [ -z "${my_REGION_NAME}" ] ; then