4.5 KiB
Runtime Reconnaissance
This document records read-only reconnaissance findings for the regalamiunsorriso runtime environment. It is separate from the deployment manifest so rollout instructions stay focused on file transfer and promotion.
Shell Behavior On 83.149.164.4
- The remote login shell behaves as
tcsh. - POSIX shell constructs like
for ...; do ...; donefail unless you explicitly run them throughsh -c. - The server
shdoes not support-l, so usesh -c, notsh -lc. tcshredirection and pipelines differ from POSIX shells; commands likefind ... 2>/dev/null | headcan fail withAmbiguous output redirectunless the whole payload runs undersh -c.- Prefer one remote command per SSH invocation for reconnaissance. Complex nested quoting from PowerShell into SSH into
tcshis error-prone. - If PowerShell shows the continuation prompt
? >, the command was malformed locally before SSH executed it. - Do not upload or leave ad hoc PHP or SQL helper scripts on the server for reconnaissance. Any future live DB query method must be explicitly approved first.
Mail Template Directories Found On Server
- Live rollout target:
/home/sites/regalamiunsorriso/www/mailMessage - Staging copy:
/home/marco/regalamiunsorriso/incoming/www/mailMessage - Older duplicate tree:
/home/sites/regalamiunsorriso/wwwLang/mailMessage - Archived duplicate tree:
/home/sites/regalamiunsorriso/wwwOld/www/mailMessage
Representative checksum comparisons showed that www/mailMessage and wwwLang/mailMessage are not interchangeable copies:
noMorePic.html: live2188047161 3645,wwwLang2803737061 3775userMsg_itCC.html: live324589227 5628,wwwLang429470199 4921
Runtime Resolution Path
- The Java application lives under
/home/sites/regalamiunsorriso/rus/WEB-INF. DBAdapter.getDocBase()resolves togetParm("DOCBASE").getTesto().Parm.findByCodice()readsPARMrows withselect A.* from PARM AS A where A.codice='...'.- Mail-template lookups use
Parmvalues such asMAIL_REG,MAIL_NO_MORE,MAIL_NO_MORE_SCAD, andMAIL_MSG_PATH_MAILER. rus/WEB-INF/lib/pg_src/com/ablia/pg/Users.javaseeds defaults forMAIL_MSG_RINNOVOasmailMessage/rinnovoMsg.htmlandMAIL_MSG_COUPON_OMAGGIOasmailMessage/couponOmaggioMsg.htmlwhen parameters are missing.dbcomuni.properties,rus.properties, andtruckservice.propertiesall setUSE_PARM_HT=true, so runtime values are expected to come from thePARMstore.
Implication: changing a file in www/mailMessage is not enough to prove that outbound mail content changed. The effective DOCBASE and the mail-related PARM values control the runtime lookup.
Live Configuration Evidence
www Webapp
Local and live www/WEB-INF/web.xml contain the strongest SQL host evidence:
dbDriver=17database=//192.168.10.250/pgcatalog=pguser=rootpassword=root- description hint for server password:
250658# - description hint for alternate endpoint:
//localhost:3308/pg
rus Webapp
rus/WEB-INF/web.xml appears to reflect an older or alternate local configuration:
dbDriver=3database=//localhost/pguser=rootpassword=root
Local source in DriversJdbc.java maps dbDriver=3 to MySQL Connector/J.
Confirmed Read-Only SQL Findings
Read-only validation performed during this reconnaissance confirmed that the live application data is reachable on the network SQL host:
- host:
192.168.10.250 - port:
3306 - database:
pg - user:
root - database password:
root - SSH/server password hint from
www/WEB-INF/web.xmldescription:250658# 127.0.0.1:3308refused connections from the shell during the same investigation
The following live PARM values were recovered:
DOCBASE=/home/www/regalamiunsorriso/doMAIL_MSG_PATH_MAILER=phpmailer/regala_un_sorriso/MAIL_NO_MORE=mail_no_more.htmlMAIL_NO_MORE_SCAD=mail_no_more_scad.htmlMAIL_REG=mail_reg.html
Implication: the current outbound mail path is not driven directly by the deployed www/mailMessage/noMorePic*.html files. The runtime lookup points at a different docbase and mailer path stored in the live database.
Recon Scope Note
- The
RUSentry under/home/sites/regalamiunsorrisois a symlink to/mnt/da1/foto. - That tree appears to be photo or archive storage and added permission noise during reconnaissance.
- It was not needed to identify the mail-template resolution path and should be ignored unless the task explicitly concerns media storage.