-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

This page serves as informational purpose for any news related to
Paranoid Secure Hosting. All updates on this page are signed with the
 Paranoid Secure Hosting OpenPGP key.

The binary OpenPGP public key can be imported from (for ascii armored add .asc to url):
https://d9ping.nl/.well-known/openpgpkey/hu/t5s8ztdbon8yzntexy6oz5y48etqsnbb
Fingerprint: 7637487CEB21CFBF21AA448B4267880693D1329E
Algorithm: RSA 4096 bits
Long Key-ID: 4267880693D1329E
Valid till: 2027-01-01(YYYY-MM-DD)
Previous valid till: 2024-01-01(YYYY-MM-DD)
And previous valid till: 2023-01-01(YYYY-MM-DD)
And also previous valid till: 2021-01-01(YYYY-MM-DD)

Any message before before 2018-01-01(YYYY-MM-DD) 12:00(UTC) were signed with our olds
Algorithm: RSA 3072 bits
Fingerprint: C7570F0C16D6ED56C4D5E9C240F7B86E9A1ECAD2
Valid till: 2018-01-01(YYYY-MM-DD) 12:00(UTC).
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEdjdIfOshz78hqkSLQmeIBpPRMp4FAmhFs7oACgkQQmeIBpPR
Mp7NbxAAiPmbkcX1Lgpc4HR+BJ39TccjqVzofQXFur7cBBu2VkbzEiFAhzbDcEhF
mAoGDHPmbj9ZO46VLDmTESjOQZ+yAI9yQlfrYg2pBqXXV7ShMmcxU8BBUv0vLvxP
X6NSECezpqCp4bUmoy8ybKOC+uWbgp8foces+Xv+lfrGMWvrNB7F62hzC/UMyBZg
cRJ11XZPLcta11CqQ4sAjeOccurUspxhYbhpglfrvusvg+8szd+VOK6Wr4CBmTjz
ORlHAp1d8XVcu9axgaibsN1rbLjkcwdxA2R5xzP2UEkMCebKGYuIJg92NeJ5q874
FJTXcm1haCMOIfvkPwkb0Gg76ohqsEErlYLy2Q8SRarYdlbzCKkp2KvXvj5axiKU
1etGu3n1HR3sCmIoWtLvHPmrnDDl94+SwszefQm5r4FtiXFUckaiTIsMAjY6CNpn
+IsVRF6ITonQCOw+tQ89nDbpTJ0BVjgA3Xh+UdebCe0GrP+korjD6xNCxndGwQKf
dPoMsP7DJwT8Ix24y1ZO4h78UfdVevMEgvyynJVpTrzddhO89WtqhfV5rkWTynNm
N4sKPmJu+7AIjaAxnhX3zuljSIikoY49LRprFiXVUsC/oHzPeQZjBvPqow5mKg0A
ban/KjDeTnQuCULQm3VgK1VlFMpCt4skLJByfahxRbVRQZO6ODw=
=dbpk
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Paranoid Secure Hosting was asked what the bug bounty reward is.
Paranoid Secure Hosting likes to publicly response to this here.
Currently Paranoid Secure Hosting has no generous bug bounty 
reward due to the fact we have only a few small clients and no high profile websites hosted.
So currently we offer a hall of fame mention and 
a reward of 1 Litecoin for a low issue to 1 Bitcoin for a really critical issue.
We choice to pay our reward in Bitcoins or Litecoins because it's quick
 and offers some privacy for the hacker who receives it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19

iQGcBAEBCAAGBQJR6xhnAAoJEED3uG6aHsrS8/sL/A1mFJj+6hcGBFFvB3M2cJG8
QrYR4jYFOuhyVsTpNyxClo6AdnTVVutZplb9+05OvrXRqPae7YDsLsXqDohdimlN
X8sK80eAtgmB1Z/M9SZbWgFLK5+AOTjPpvYdy8l6qiEv3Mdesrr5cwRubMjaN4wc
kz8zEUbKdtQiSVIV1SUrK8xT8EA7c/NJr9ywiK4o1vwKYREOsOG2q5ea+NUY3fbE
bafEn+OP1PyugWd8gOiHOCogG5MAI1WbBK74beAjsjdHmoI0MVPxfKiZNt+2FfSh
tqO+/neG1h7FcWSi/CaZ46p+l0RD6NSGXtyghez0ViG35mWpThW8C907wT5R4z6j
0+NlZxVPfHPA93k8wXRJWItGeOiD3qkqQqMiy9EDoG+URkGoPE1h0BGGcvYUESGr
x1VQpgCVJyD+LPfFGeyOIg6rBp5X16ZrQbsftGHOT7dtFML+7X6RexL9th2ALD8s
f4PdHl/WT8feL+7sBdovfmEGu4H8iPZyRZ3kKMcucw==
=bm+G
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Notice on recent Intel RdRand possible random number backdoor allegations.
Paranoid Secure Hosting does not used RdRand optimization for generating any certificate 
because Paranoid Secure Hosting does not use Intel processors. Thus the random numbers 
generated for encryption used by Paranoid Secure Hosting remain safe from any possible
random number backdoor in Intel RdRand random number generator because it's simply not used here.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19

iQGcBAEBCAAGBQJR4yd+AAoJEED3uG6aHsrSZYgL/3EtnRjaeWrllixj9v/8xt7e
Mz+2qmviRP8U2rtoLRe1/Se3hP4FRUKTLOTm9hJYFNDTTW/gt/2WYCESWEE5iyZa
H5JZiQ+jkPekJMtnLehM8qlOjOT+yXpq0NgmCzQBDGyiCUL/N6xva0hlCIQ9llhl
PwreD1o3+rnCYstSW3OLitqMunqUqNP2Jw55HhOFJ72uJQuwTVOXk5ml7JzjUL8X
AQ+W0mBTo3e0BoKrtI07UdHIF9iHH9Bdn5cO7USgXfD/YCP782zcTuZCJMO4VBJC
KHtiQGk2BNkNcLALWDyjp8t/YvUp+fFjtoBosw5eQM6WA+Ovcf/2DHSDornufTDQ
P5P2jPGxsRGt2UqwaIrw5k4ma0bi1Xp0cbc4MzWslNv5mId3EHa526Ff3DGyVKBU
4qbOdpsHaUrcyg+lDdAurH+YpNZVANRlK5isIcnpIeKxZ7sMeEJnFGB5is5nYTOB
Eoqb7DX+NlvK1fnwc+nx2jGarm8/OxvPUPUJQxY+Kg==
=HHF8
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Update on TLS connection errors.
After a full reboot of the server the TLS connection errors has gona away.
We suspect this connection errors was caused by a bug of GnuTLS.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19

iQGcBAEBCAAGBQJR3VthAAoJEED3uG6aHsrSm5ML/14hxswVhNntvbLu+6Qx6rE3
M/UpXpp5lrPt6HHAx7zlURGP1q9/SV8fljiInt4Ao8363fOl95x+9y/M+Tv6VGwe
fxG2WxinWaj77DhLSJ0Sg3egCNqzSxm3R7UMpupWgTqRH0XYTSwOYJEuvc1XOp5S
vIV/ps9OuyKMAHmy/OI1zzOrwOwAPjxFjFa1gf+h7oyDHZEiqYbgZPGjnQV1kztg
lClMh9PGYvCX0iqdKm5S8/HQGbD4MQZulfY+vqR8tQ5Rjamxs7rSr390T5MO0K7l
vJVAyQZjMUaO3bQVs2XngZma487HZC/I7AlY+bYZvrfs8o19BVYzCSMZcJi3uiT3
dXawSDUXaiOFf0KqHj//cP87FKb41tPVF/9GYsbDPMf9T60R1Ak+r9BQsgVRHE89
D/DJvVS5pGxDcYjI1H2jv0DlWaVnLimEPA9fle1BYmfBAjcHQbKCKuK3+ec0YJc9
9f3nRXWSg0qdTtBWPKU4oR5CHLAFq6s5EekXI9lg5g==
=DZy3
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

We are aware of a DNSSEC error at d9ping.nl making dns unresolvable for d9ping.nl.
This issue is being resolved by disabling and enabling DNSSEC again at mijndomein.nl 
the registar of d9ping.nl. 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19

iQGcBAEBCAAGBQJR3Vh+AAoJEED3uG6aHsrSESUL/3/nsyp/+9XlOi45HbaVBg6V
zxal+RuBTwHYxDon08eFONnTwClpgo8/ld3+AwSYBvmw/gFge5pAJCHyFD6nX5ol
UIL2wq72CMLMYeXocfSG293sct8oLiw1nj9BBilZOVeuTRCM48nGzrNOghq4fRL0
xND5+WN4RBgqvRTGzpzbb18ir/6dO4len6UI7UZorFvRtJ934hDbVGV8ZFNqkfEK
htzlP77XydLwnvPTfZ+Lze+HSJoXu2Myee/6b1ZzSIrkL2K/zRrQwSFnX57FBQ8L
ZihJmD7SM5zI8HZRDOfaVgvqmIBPGIWB6YDbFsNvP7HRCA1hALBgpsf9S+qbqkzX
1uT79dJL/m/AyCOR7BJIBvjjjto7lvyL3Q5m0Tqp/OeVCpkuLadEmKKABaRv/BM+
0Q1qP6sZuIiwfQJmgeX+cMTGbt/Q0jvhEUucf+zXL1xKxNDI9ucyPgEZpgiJa9Z+
sRFQhqKs059leA7JjH7nyfwEoMCrJJKuwffpXPnJqA==
=VK9v
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

We are aware of connection issues with connecting with TLS to any of our websites
we are still investigating what is going on why TLS would not work.
We suspect that the server TLS cache got corrupted, but using a new fresh cache hasn't
 yet resolved our TLS connection issues. 
 So more investigating on what is causing TLS connections to abort is needed.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19

iQGcBAEBCAAGBQJR3VUEAAoJEED3uG6aHsrSbn4L/RiLD33kk0g2cFDK8V0ECEDi
0Da3HO569QEQud68lDDISVne2Xv2/ghdBd3OXYgCRWT82eWliZk+D+vAOj+6jBNh
KdCB1e9LgLzloIG1ZM6QvGS/gCtvejuEezc/i2PXSuLLvRNKOVmPW9SmJgUZeTtC
RkJKFV21771dMTIeEIPVaWIarYvhqnQxMA6uemMgpw5kfzEmQj1ai1f1ksVr7kRe
1RGoR5HD7AULImpHy7U9kax63nSTMvBry7/Ah/2+ohT4DMuoGXkSJkXT5RmDiFVZ
VGkgQmoMy+XDD7soW+9mYKYlHDqiZRGBD5sGub6XKqW/2UR10EVyS1LZYoSOOdv7
OHhBnCmibBu4hvulq1/4AMQXz8q2NEEDi7EKb+/vygqqQyJ7rYqXiAtHyID9E3jc
Mx9Sy2dc3LCsWQoJPWuYZrdEwVicviFqK2EWokgL1idyLCRP+8oP5CwzWNZ4wnWf
5jWoRn64eTaAbL3gnAOzBiKHGBVpZgmhSuE6pBJwhQ==
=VRYK
-----END PGP SIGNATURE-----