revi-archive/phorge-arcanist
1
0
Fork 0
mirror of https://we.phorge.it/source/arcanist.git synced 2024-11-23 07:12:40 +01:00
Code Issues Releases Wiki Activity

Add resources/ssl/custom.pem to .gitignore

Browse source 
Summary:
When arcanist connects to a phorge site which uses an SSL certificate signed by a local CA, then the client needs to have a resources/ssl/custom.pem file as per resources/ssl/README

As this is client specific it should be in the .gitignore file.

Also update resources/ssl/README to replace [Pp]habricator with [Pp]horge.

Test Plan:
```
touch resources/ssl/custom.pem
git status
```
The 'git status' should show no changes.

Reviewers: O1 Blessed Committers, valerio.bozzolan

Reviewed By: O1 Blessed Committers, valerio.bozzolan

Subscribers: speck, tobiaswiese, valerio.bozzolan, Matthew, Cigaryno

Differential Revision: https://we.phorge.it/D25304
This commit is contained in:
Steve Campbell 2023-06-21 19:56:41 +01:00
parent 677e117b97
commit 8130241a11
2 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
.gitignore vendored
View file

@ -11,6 +11,7 @@
# User extensions
/externals/includes/*
/src/extensions/*
/resources/ssl/custom.pem
# XHPAST
/support/xhpast/*.a

8
resources/ssl/README
View file

@ -34,11 +34,11 @@ If "custom.pem" is present, that file will be used instead of "default.pem".
If you receive errors using your "custom.pem" file, you can test it directly
with `curl` by running a command like this:
curl -v --cacert path/to/your/custom.pem https://phabricator.example.com/
curl -v --cacert arcanist/resources/ssl/custom.pem https://phorge.example.com/
Replace "path/to/your/custom.pem" with the path to your "custom.pem" file,
and replace "https://phabricator.example.com" with the real URL of your
Phabricator install.
Replace "arcanist/resources/ssl/custom.pem" with the path to your "custom.pem"
file, and replace "https://phorge.example.com" with the real URL of your Phorge
install.
The initial lines of output from `curl` should give you information about the
SSL handshake and certificate verification, which may be helpful in resolving