The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: sect1/para
Context English State
<literal><systemitem class="fqdomainname">smtp.FreeBSD.org</systemitem>:587</literal> (see also <xref linkend="smtp-setup"/>).
<emphasis><literal>src/</literal> Subversion Root</emphasis>
<literal>svn+ssh://</literal><systemitem class="fqdomainname">repo.FreeBSD.org</systemitem><filename>/base</filename> (see also <xref linkend="svn-getting-started-base-layout"/>).
<emphasis><literal>doc/</literal> Subversion Root</emphasis>
<literal>svn+ssh://</literal><systemitem class="fqdomainname">repo.FreeBSD.org</systemitem><filename>/doc</filename> (see also <xref linkend="svn-getting-started-doc-layout"/>).
<emphasis><literal>ports/</literal> Subversion Root</emphasis>
<literal>svn+ssh://</literal><systemitem class="fqdomainname">repo.FreeBSD.org</systemitem><filename>/ports</filename> (see also <xref linkend="svn-getting-started-ports-layout"/>).
<emphasis>Internal Mailing Lists</emphasis>
developers (technically called all-developers), doc-developers, doc-committers, ports-developers, ports-committers, src-developers, src-committers. (Each project repository has its own -developers and -committers mailing lists. Archives for these lists can be found in the files <filename>/local/mail/<replaceable>repository-name</replaceable>-developers-archive</filename> and <filename>/local/mail/<replaceable>repository-name</replaceable>-committers-archive</filename> on the <systemitem class="fqdomainname">FreeBSD.org</systemitem> cluster.)
<emphasis>Core Team monthly reports</emphasis>
<filename>/home/core/public/monthly-reports</filename> on the <systemitem class="fqdomainname">FreeBSD.org</systemitem> cluster.
<emphasis>Ports Management Team monthly reports</emphasis>
<filename>/home/portmgr/public/monthly-reports</filename> on the <systemitem class="fqdomainname">FreeBSD.org</systemitem> cluster.
<emphasis>Noteworthy <literal>src/</literal> SVN Branches</emphasis>
<literal>stable/</literal><replaceable>n</replaceable> (<replaceable>n</replaceable>-STABLE), <literal>head</literal> (-CURRENT)
<citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry> is required to connect to the project hosts. For more information, see <xref linkend="ssh.guide"/>.
Useful links:
<link xlink:href="@@URL_RELPREFIX@@/internal/">FreeBSD Project Internal Pages</link>
<link xlink:href="@@URL_RELPREFIX@@/internal/machines.html">FreeBSD Project Hosts</link>
<link xlink:href="@@URL_RELPREFIX@@/administration.html">FreeBSD Project Administrative Groups</link>
Open<acronym>PGP</acronym> Keys for FreeBSD
Cryptographic keys conforming to the Open<acronym>PGP</acronym> (<emphasis>Pretty Good Privacy</emphasis>) standard are used by the FreeBSD project to authenticate committers. Messages carrying important information like public <acronym>SSH</acronym> keys can be signed with the Open<acronym>PGP</acronym> key to prove that they are really from the committer. See <link xlink:href="http://www.nostarch.com/pgp_ml.htm">PGP &amp; GPG: Email for the Practical Paranoid by Michael Lucas</link> and <link xlink:href="http://en.wikipedia.org/wiki/Pretty_Good_Privacy"/> for more information.
Creating a Key
Existing keys can be used, but should be checked with <filename>doc/head/share/pgpkeys/checkkey.sh</filename> first. In this case, make sure the key has a FreeBSD user ID.
For those who do not yet have an Open<acronym>PGP</acronym> key, or need a new key to meet FreeBSD security requirements, here we show how to generate one.
Install <filename role="package">security/gnupg</filename>. Enter these lines in <filename>~/.gnupg/gpg.conf</filename> to set minimum acceptable defaults:
fixed-list-mode
keyid-format 0xlong
personal-digest-preferences SHA512 SHA384 SHA256 SHA224
default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 BZIP2 ZLIB ZIP Uncompressed
use-agent
verify-options show-uid-validity
list-options show-uid-validity
sig-notation issuer-fpr@notations.openpgp.fifthhorseman.net=%g
cert-digest-algo SHA512
Generate a key:
<prompt>%</prompt> <userinput>gpg --full-gen-key</userinput>
gpg (GnuPG) 2.1.8; Copyright (C) 2015 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Warning: using insecure memory!
Please select what kind of key you want:
(1) RSA and RSA (default)
(2) DSA and Elgamal
(3) DSA (sign only)
(4) RSA (sign only)
Your selection? <userinput>1</userinput>
RSA keys may be between 1024 and 4096 bits long.
What keysize do you want? (2048) <userinput>2048</userinput> <co xml:id="co-pgp-bits"/>
Requested keysize is 2048 bits
Please specify how long the key should be valid.
0 = key does not expire
&lt;n&gt; = key expires in n days
&lt;n&gt;w = key expires in n weeks
&lt;n&gt;m = key expires in n months
&lt;n&gt;y = key expires in n years
Key is valid for? (0) <userinput>3y</userinput> <co xml:id="co-pgp-expire"/>
Key expires at Wed Nov 4 17:20:20 2015 MST
Is this correct? (y/N) <userinput>y</userinput>

GnuPG needs to construct a user ID to identify your key.

Real name: <userinput><replaceable>Chucky Daemon</replaceable></userinput> <co xml:id="co-pgp-realname"/>
Email address: <userinput><replaceable>notreal@example.com</replaceable></userinput>
Comment:
You selected this USER-ID:
"<replaceable>Chucky Daemon &lt;notreal@example.com&gt;</replaceable>"

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? <userinput>o</userinput>
You need a Passphrase to protect your secret key.
2048-bit keys with a three-year expiration provide adequate protection at present (2013-12). <link xlink:href="http://danielpocock.com/rsa-key-sizes-2048-or-4096-bits"/> describes the situation in more detail.
A three year key lifespan is short enough to obsolete keys weakened by advancing computer power, but long enough to reduce key management problems.

Loading…

No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: sect1/para
Flags
read-only
Source string location
article.translate.xml:181
String age
a year ago
Source string age
a year ago
Translation file
articles/committers-guide.pot, string 36