In addition to EmmArrBee's bug report that TW should not send spoofed mails, I would like to add something on top. Nowadays, admins might want to reassure their users that mails from a Tiki installation really are genuine. There are several ways towards this goal.
I would like to sort them by importance and ease of integration like this:
DKIM needs at least some assistance by the ISP, but some parts can be integrated into Tiki. DKIM will soon become necessary for not getting spam-filtered.
Signing and encrypting actually do not need much, because the cryptographic part can be fully outsourced to a pre-existing GPG. It should be checked whether GPG_PATH is set (usually to /opt/gnupg/bin/gpg). A keyring must exist or be created,
The only tricky thing that comes to my mind is the handling of the passphrase. As we cannot ask the admin to enter the passphrase each and every time, we must store it somewhere, which opens a security risk of it getting compromised. So admins should be advised that they create a key and passphrase that can be easily exchanged if compromised. Admins shall be advised to not use their (or someone else's) personal keys for this purpose under ANY circumstance! For comfort, the revoking of the old key could become a Tiki feature somewhere.
Show.tiki.org snapshot creation is in progress... Please monitor http:///snapshots/ for progress. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Password reset was successful
Password reset failed
Show.tiki.org instance destruction is in progress... Please wait...
The public/private keys configured to connect to show2.tikiwiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is currently under maintenance. Sorry for the inconvenience.
Unable to get information from show2.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is in the progress of creating the new instance. Please continue waiting for a minute or two. If this continues on for more than 10 minutes, please let us know of the problem so that we can do something about it. Thanks.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tikiwiki.org instance. To start, simply select a version and click on "Create show2.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tikiwiki.org.
The URL for the show2.tikiwiki.org instance that demonstrates this bug is at: http://. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http:///info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tikiwiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http:///snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".Create new snapshot
|No attachments for this item|