X-Git-Url: https://git.adam-barratt.org.uk/?a=blobdiff_plain;f=templates%2Fwelcome-message-800;h=822243f50ba2b6628ecdca89ad2657ab1072bd71;hb=58a147022e85f28e98cf68f5b4cd2d1afdadd42e;hp=c41802818f763a50f011065874819c2ed8b93712;hpb=dfa27144a51a18b67460df682e5d2a3811424f0d;p=mirror%2Fuserdir-ldap.git diff --git a/templates/welcome-message-800 b/templates/welcome-message-800 index c418028..822243f 100644 --- a/templates/welcome-message-800 +++ b/templates/welcome-message-800 @@ -1,11 +1,11 @@ -To: "__REALNAME__" <__EMAIL__> +To: "__ENCODED_REALNAME__" <__EMAIL__> From: __WHOAMI__ MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit -Subject: New Debian maintainer __REALNAME__ -Cc: da-manager@debian.org, debian-admin@debian.org -Reply-To: da-manager@debian.org +Subject: New Debian developer __ENCODED_REALNAME__ +Cc: nm@debian.org, debian-admin@debian.org +Reply-To: nm@debian.org Date: __DATE__ User-Agent: nm-create script run by __WHOAMI__ @@ -17,35 +17,52 @@ Dear __REALNAME__! Your account '__LOGIN__' has just been created in the central LDAP database of the Debian project. Please note that it needs a bit of time until this information is synced with all developer-accessible machines. -You should be able to login or upload packages after about 30-60 minutes. -The password for this account can be found appended to this message, -encrypted with your GPG key. +You should be able to login into debian.org machines after about 30-60 +minutes. If you applied for Debian Developer with uploading rights, +you should be able to upload packages already. Email sent to <__LOGIN__@debian.org> will be forwarded to <__EMAIL__>, to change this visit . -The Debian mail setup allows verious per-user settings, like enabling -greylisting and sender-verify-callouts and per-user dns blocklists. +The Debian mail setup allows various per-user settings, like enabling +greylisting, sender-verify-callouts and per-user dns blocklists. Please refer to on how to change these settings. Some may also be exposed via the web interface behind . +Your password to access db.debian.org can be found encrypted with your +PGP key and appended to this message. It cannot be used to log into +our machines; see the paragraph on SSH keys below. + You now have access to various project machines, for a list of them take a look at . Please remember that you accepted the Debian Machine Usage Policy in your NM process (available at ). -If you need additional software installed on one of the machines (either -in the host system or a chroot environment) please contact -debian-admin@lists.debian.org, but keep in mind that not all software is -available on all architectures. The chroot environments can be -entered with the 'dchroot' command; take a look at the list of machines -to know which one has chroots available for you. +If you need additional software installed on one of the machines (in the +host system) please contact debian-admin@lists.debian.org, but keep in +mind that not all software is available on all architectures. + +On porter machines, the chroot environments can be entered with the +'schroot' command, depending on setup; take a look at the list of +machines to know which are our porterboxes. You can install build +dependencies yourself once you instantiated a session. Please +consult for more information +and ask your fellow DDs if you need any help. You need to use ssh to log into the machines; telnet and rlogin are -disabled for security reasons. The LDAP directory is able to share RSA -ssh keys among machines, please see -Please be aware of the security implications of using RSA authentication -and ssh agents. +disabled for security reasons. On debian.org servers the only ssh +authentication method available is publickey. The LDAP directory is +able to share RSA ssh keys among machines, please see +. Please be aware of the +security implications of using RSA authentication and ssh agents. The +SSH fingerprints for all Debian machines can be looked up at + or a known_hosts file can be +downloaded from . + +Debian secures some of its websites using SSL. The SSL certificates +used are signed by the intermediate CA ca.debian.org. ca.debian.org +itself is signed by SPI CA which is part of the Debian package +ca-certificates. To give you a quick overview here is a list of the most important machines from the project you can access. There is the main archive @@ -106,7 +123,9 @@ You can find much more information useful to developers at Also, please subscribe to the mailing list debian-devel-announce, if you haven't done so already. All Debian developers are required to read -this list, as important announcements are made there. +this list, as important announcements are made there. Changes to +Debian's infrastructure and maintenance of it are announced to the +debian-infrastructure-announce mailing list. We strongly suggest that you use your __LOGIN__@debian.org address for the maintainer field in your packages, because that one will be valid