/contrib/bind9/bin/dnssec/dnssec-signzone.docbook

https://bitbucket.org/freebsd/freebsd-head/ · Unknown · 695 lines · 640 code · 55 blank · 0 comment · 0 complexity · 34ef981e9af694f1aa4567156ed8fa3e MD5 · raw file

  1. <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
  2. "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
  3. [<!ENTITY mdash "&#8212;">]>
  4. <!--
  5. - Copyright (C) 2004-2009 Internet Systems Consortium, Inc. ("ISC")
  6. - Copyright (C) 2000-2003 Internet Software Consortium.
  7. -
  8. - Permission to use, copy, modify, and/or distribute this software for any
  9. - purpose with or without fee is hereby granted, provided that the above
  10. - copyright notice and this permission notice appear in all copies.
  11. -
  12. - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
  13. - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
  14. - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
  15. - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
  16. - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
  17. - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  18. - PERFORMANCE OF THIS SOFTWARE.
  19. -->
  20. <!-- $Id: dnssec-signzone.docbook,v 1.44 2009/12/03 23:18:16 each Exp $ -->
  21. <refentry id="man.dnssec-signzone">
  22. <refentryinfo>
  23. <date>June 05, 2009</date>
  24. </refentryinfo>
  25. <refmeta>
  26. <refentrytitle><application>dnssec-signzone</application></refentrytitle>
  27. <manvolnum>8</manvolnum>
  28. <refmiscinfo>BIND9</refmiscinfo>
  29. </refmeta>
  30. <refnamediv>
  31. <refname><application>dnssec-signzone</application></refname>
  32. <refpurpose>DNSSEC zone signing tool</refpurpose>
  33. </refnamediv>
  34. <docinfo>
  35. <copyright>
  36. <year>2004</year>
  37. <year>2005</year>
  38. <year>2006</year>
  39. <year>2007</year>
  40. <year>2008</year>
  41. <year>2009</year>
  42. <holder>Internet Systems Consortium, Inc. ("ISC")</holder>
  43. </copyright>
  44. <copyright>
  45. <year>2000</year>
  46. <year>2001</year>
  47. <year>2002</year>
  48. <year>2003</year>
  49. <holder>Internet Software Consortium.</holder>
  50. </copyright>
  51. </docinfo>
  52. <refsynopsisdiv>
  53. <cmdsynopsis>
  54. <command>dnssec-signzone</command>
  55. <arg><option>-a</option></arg>
  56. <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
  57. <arg><option>-d <replaceable class="parameter">directory</replaceable></option></arg>
  58. <arg><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
  59. <arg><option>-e <replaceable class="parameter">end-time</replaceable></option></arg>
  60. <arg><option>-f <replaceable class="parameter">output-file</replaceable></option></arg>
  61. <arg><option>-g</option></arg>
  62. <arg><option>-h</option></arg>
  63. <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
  64. <arg><option>-k <replaceable class="parameter">key</replaceable></option></arg>
  65. <arg><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
  66. <arg><option>-i <replaceable class="parameter">interval</replaceable></option></arg>
  67. <arg><option>-I <replaceable class="parameter">input-format</replaceable></option></arg>
  68. <arg><option>-j <replaceable class="parameter">jitter</replaceable></option></arg>
  69. <arg><option>-N <replaceable class="parameter">soa-serial-format</replaceable></option></arg>
  70. <arg><option>-o <replaceable class="parameter">origin</replaceable></option></arg>
  71. <arg><option>-O <replaceable class="parameter">output-format</replaceable></option></arg>
  72. <arg><option>-p</option></arg>
  73. <arg><option>-P</option></arg>
  74. <arg><option>-r <replaceable class="parameter">randomdev</replaceable></option></arg>
  75. <arg><option>-S</option></arg>
  76. <arg><option>-s <replaceable class="parameter">start-time</replaceable></option></arg>
  77. <arg><option>-T <replaceable class="parameter">ttl</replaceable></option></arg>
  78. <arg><option>-t</option></arg>
  79. <arg><option>-u</option></arg>
  80. <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
  81. <arg><option>-x</option></arg>
  82. <arg><option>-z</option></arg>
  83. <arg><option>-3 <replaceable class="parameter">salt</replaceable></option></arg>
  84. <arg><option>-H <replaceable class="parameter">iterations</replaceable></option></arg>
  85. <arg><option>-A</option></arg>
  86. <arg choice="req">zonefile</arg>
  87. <arg rep="repeat">key</arg>
  88. </cmdsynopsis>
  89. </refsynopsisdiv>
  90. <refsect1>
  91. <title>DESCRIPTION</title>
  92. <para><command>dnssec-signzone</command>
  93. signs a zone. It generates
  94. NSEC and RRSIG records and produces a signed version of the
  95. zone. The security status of delegations from the signed zone
  96. (that is, whether the child zones are secure or not) is
  97. determined by the presence or absence of a
  98. <filename>keyset</filename> file for each child zone.
  99. </para>
  100. </refsect1>
  101. <refsect1>
  102. <title>OPTIONS</title>
  103. <variablelist>
  104. <varlistentry>
  105. <term>-a</term>
  106. <listitem>
  107. <para>
  108. Verify all generated signatures.
  109. </para>
  110. </listitem>
  111. </varlistentry>
  112. <varlistentry>
  113. <term>-c <replaceable class="parameter">class</replaceable></term>
  114. <listitem>
  115. <para>
  116. Specifies the DNS class of the zone.
  117. </para>
  118. </listitem>
  119. </varlistentry>
  120. <varlistentry>
  121. <term>-C</term>
  122. <listitem>
  123. <para>
  124. Compatibility mode: Generate a
  125. <filename>keyset-<replaceable>zonename</replaceable></filename>
  126. file in addition to
  127. <filename>dsset-<replaceable>zonename</replaceable></filename>
  128. when signing a zone, for use by older versions of
  129. <command>dnssec-signzone</command>.
  130. </para>
  131. </listitem>
  132. </varlistentry>
  133. <varlistentry>
  134. <term>-d <replaceable class="parameter">directory</replaceable></term>
  135. <listitem>
  136. <para>
  137. Look for <filename>dsset-</filename> or
  138. <filename>keyset-</filename> files in <option>directory</option>.
  139. </para>
  140. </listitem>
  141. </varlistentry>
  142. <varlistentry>
  143. <term>-E <replaceable class="parameter">engine</replaceable></term>
  144. <listitem>
  145. <para>
  146. Uses a crypto hardware (OpenSSL engine) for the crypto operations
  147. it supports, for instance signing with private keys from
  148. a secure key store. When compiled with PKCS#11 support
  149. it defaults to pkcs11; the empty name resets it to no engine.
  150. </para>
  151. </listitem>
  152. </varlistentry>
  153. <varlistentry>
  154. <term>-g</term>
  155. <listitem>
  156. <para>
  157. Generate DS records for child zones from
  158. <filename>dsset-</filename> or <filename>keyset-</filename>
  159. file. Existing DS records will be removed.
  160. </para>
  161. </listitem>
  162. </varlistentry>
  163. <varlistentry>
  164. <term>-K <replaceable class="parameter">directory</replaceable></term>
  165. <listitem>
  166. <para>
  167. Key repository: Specify a directory to search for DNSSEC keys.
  168. If not specified, defaults to the current directory.
  169. </para>
  170. </listitem>
  171. </varlistentry>
  172. <varlistentry>
  173. <term>-k <replaceable class="parameter">key</replaceable></term>
  174. <listitem>
  175. <para>
  176. Treat specified key as a key signing key ignoring any
  177. key flags. This option may be specified multiple times.
  178. </para>
  179. </listitem>
  180. </varlistentry>
  181. <varlistentry>
  182. <term>-l <replaceable class="parameter">domain</replaceable></term>
  183. <listitem>
  184. <para>
  185. Generate a DLV set in addition to the key (DNSKEY) and DS sets.
  186. The domain is appended to the name of the records.
  187. </para>
  188. </listitem>
  189. </varlistentry>
  190. <varlistentry>
  191. <term>-s <replaceable class="parameter">start-time</replaceable></term>
  192. <listitem>
  193. <para>
  194. Specify the date and time when the generated RRSIG records
  195. become valid. This can be either an absolute or relative
  196. time. An absolute start time is indicated by a number
  197. in YYYYMMDDHHMMSS notation; 20000530144500 denotes
  198. 14:45:00 UTC on May 30th, 2000. A relative start time is
  199. indicated by +N, which is N seconds from the current time.
  200. If no <option>start-time</option> is specified, the current
  201. time minus 1 hour (to allow for clock skew) is used.
  202. </para>
  203. </listitem>
  204. </varlistentry>
  205. <varlistentry>
  206. <term>-e <replaceable class="parameter">end-time</replaceable></term>
  207. <listitem>
  208. <para>
  209. Specify the date and time when the generated RRSIG records
  210. expire. As with <option>start-time</option>, an absolute
  211. time is indicated in YYYYMMDDHHMMSS notation. A time relative
  212. to the start time is indicated with +N, which is N seconds from
  213. the start time. A time relative to the current time is
  214. indicated with now+N. If no <option>end-time</option> is
  215. specified, 30 days from the start time is used as a default.
  216. <option>end-time</option> must be later than
  217. <option>start-time</option>.
  218. </para>
  219. </listitem>
  220. </varlistentry>
  221. <varlistentry>
  222. <term>-f <replaceable class="parameter">output-file</replaceable></term>
  223. <listitem>
  224. <para>
  225. The name of the output file containing the signed zone. The
  226. default is to append <filename>.signed</filename> to
  227. the
  228. input filename.
  229. </para>
  230. </listitem>
  231. </varlistentry>
  232. <varlistentry>
  233. <term>-h</term>
  234. <listitem>
  235. <para>
  236. Prints a short summary of the options and arguments to
  237. <command>dnssec-signzone</command>.
  238. </para>
  239. </listitem>
  240. </varlistentry>
  241. <varlistentry>
  242. <term>-i <replaceable class="parameter">interval</replaceable></term>
  243. <listitem>
  244. <para>
  245. When a previously-signed zone is passed as input, records
  246. may be resigned. The <option>interval</option> option
  247. specifies the cycle interval as an offset from the current
  248. time (in seconds). If a RRSIG record expires after the
  249. cycle interval, it is retained. Otherwise, it is considered
  250. to be expiring soon, and it will be replaced.
  251. </para>
  252. <para>
  253. The default cycle interval is one quarter of the difference
  254. between the signature end and start times. So if neither
  255. <option>end-time</option> or <option>start-time</option>
  256. are specified, <command>dnssec-signzone</command>
  257. generates
  258. signatures that are valid for 30 days, with a cycle
  259. interval of 7.5 days. Therefore, if any existing RRSIG records
  260. are due to expire in less than 7.5 days, they would be
  261. replaced.
  262. </para>
  263. </listitem>
  264. </varlistentry>
  265. <varlistentry>
  266. <term>-I <replaceable class="parameter">input-format</replaceable></term>
  267. <listitem>
  268. <para>
  269. The format of the input zone file.
  270. Possible formats are <command>"text"</command> (default)
  271. and <command>"raw"</command>.
  272. This option is primarily intended to be used for dynamic
  273. signed zones so that the dumped zone file in a non-text
  274. format containing updates can be signed directly.
  275. The use of this option does not make much sense for
  276. non-dynamic zones.
  277. </para>
  278. </listitem>
  279. </varlistentry>
  280. <varlistentry>
  281. <term>-j <replaceable class="parameter">jitter</replaceable></term>
  282. <listitem>
  283. <para>
  284. When signing a zone with a fixed signature lifetime, all
  285. RRSIG records issued at the time of signing expires
  286. simultaneously. If the zone is incrementally signed, i.e.
  287. a previously-signed zone is passed as input to the signer,
  288. all expired signatures have to be regenerated at about the
  289. same time. The <option>jitter</option> option specifies a
  290. jitter window that will be used to randomize the signature
  291. expire time, thus spreading incremental signature
  292. regeneration over time.
  293. </para>
  294. <para>
  295. Signature lifetime jitter also to some extent benefits
  296. validators and servers by spreading out cache expiration,
  297. i.e. if large numbers of RRSIGs don't expire at the same time
  298. from all caches there will be less congestion than if all
  299. validators need to refetch at mostly the same time.
  300. </para>
  301. </listitem>
  302. </varlistentry>
  303. <varlistentry>
  304. <term>-n <replaceable class="parameter">ncpus</replaceable></term>
  305. <listitem>
  306. <para>
  307. Specifies the number of threads to use. By default, one
  308. thread is started for each detected CPU.
  309. </para>
  310. </listitem>
  311. </varlistentry>
  312. <varlistentry>
  313. <term>-N <replaceable class="parameter">soa-serial-format</replaceable></term>
  314. <listitem>
  315. <para>
  316. The SOA serial number format of the signed zone.
  317. Possible formats are <command>"keep"</command> (default),
  318. <command>"increment"</command> and
  319. <command>"unixtime"</command>.
  320. </para>
  321. <variablelist>
  322. <varlistentry>
  323. <term><command>"keep"</command></term>
  324. <listitem>
  325. <para>Do not modify the SOA serial number.</para>
  326. </listitem>
  327. </varlistentry>
  328. <varlistentry>
  329. <term><command>"increment"</command></term>
  330. <listitem>
  331. <para>Increment the SOA serial number using RFC 1982
  332. arithmetics.</para>
  333. </listitem>
  334. </varlistentry>
  335. <varlistentry>
  336. <term><command>"unixtime"</command></term>
  337. <listitem>
  338. <para>Set the SOA serial number to the number of seconds
  339. since epoch.</para>
  340. </listitem>
  341. </varlistentry>
  342. </variablelist>
  343. </listitem>
  344. </varlistentry>
  345. <varlistentry>
  346. <term>-o <replaceable class="parameter">origin</replaceable></term>
  347. <listitem>
  348. <para>
  349. The zone origin. If not specified, the name of the zone file
  350. is assumed to be the origin.
  351. </para>
  352. </listitem>
  353. </varlistentry>
  354. <varlistentry>
  355. <term>-O <replaceable class="parameter">output-format</replaceable></term>
  356. <listitem>
  357. <para>
  358. The format of the output file containing the signed zone.
  359. Possible formats are <command>"text"</command> (default)
  360. and <command>"raw"</command>.
  361. </para>
  362. </listitem>
  363. </varlistentry>
  364. <varlistentry>
  365. <term>-p</term>
  366. <listitem>
  367. <para>
  368. Use pseudo-random data when signing the zone. This is faster,
  369. but less secure, than using real random data. This option
  370. may be useful when signing large zones or when the entropy
  371. source is limited.
  372. </para>
  373. </listitem>
  374. </varlistentry>
  375. <varlistentry>
  376. <term>-P</term>
  377. <listitem>
  378. <para>
  379. Disable post sign verification tests.
  380. </para>
  381. <para>
  382. The post sign verification test ensures that for each algorithm
  383. in use there is at least one non revoked self signed KSK key,
  384. that all revoked KSK keys are self signed, and that all records
  385. in the zone are signed by the algorithm.
  386. This option skips these tests.
  387. </para>
  388. </listitem>
  389. </varlistentry>
  390. <varlistentry>
  391. <term>-r <replaceable class="parameter">randomdev</replaceable></term>
  392. <listitem>
  393. <para>
  394. Specifies the source of randomness. If the operating
  395. system does not provide a <filename>/dev/random</filename>
  396. or equivalent device, the default source of randomness
  397. is keyboard input. <filename>randomdev</filename>
  398. specifies
  399. the name of a character device or file containing random
  400. data to be used instead of the default. The special value
  401. <filename>keyboard</filename> indicates that keyboard
  402. input should be used.
  403. </para>
  404. </listitem>
  405. </varlistentry>
  406. <varlistentry>
  407. <term>-S</term>
  408. <listitem>
  409. <para>
  410. Smart signing: Instructs <command>dnssec-signzone</command> to
  411. search the key repository for keys that match the zone being
  412. signed, and to include them in the zone if appropriate.
  413. </para>
  414. <para>
  415. When a key is found, its timing metadata is examined to
  416. determine how it should be used, according to the following
  417. rules. Each successive rule takes priority over the prior
  418. ones:
  419. </para>
  420. <variablelist>
  421. <varlistentry>
  422. <listitem>
  423. <para>
  424. If no timing metadata has been set for the key, the key is
  425. published in the zone and used to sign the zone.
  426. </para>
  427. </listitem>
  428. </varlistentry>
  429. <varlistentry>
  430. <listitem>
  431. <para>
  432. If the key's publication date is set and is in the past, the
  433. key is published in the zone.
  434. </para>
  435. </listitem>
  436. </varlistentry>
  437. <varlistentry>
  438. <listitem>
  439. <para>
  440. If the key's activation date is set and in the past, the
  441. key is published (regardless of publication date) and
  442. used to sign the zone.
  443. </para>
  444. </listitem>
  445. </varlistentry>
  446. <varlistentry>
  447. <listitem>
  448. <para>
  449. If the key's revocation date is set and in the past, and the
  450. key is published, then the key is revoked, and the revoked key
  451. is used to sign the zone.
  452. </para>
  453. </listitem>
  454. </varlistentry>
  455. <varlistentry>
  456. <listitem>
  457. <para>
  458. If either of the key's unpublication or deletion dates are set
  459. and in the past, the key is NOT published or used to sign the
  460. zone, regardless of any other metadata.
  461. </para>
  462. </listitem>
  463. </varlistentry>
  464. </variablelist>
  465. </listitem>
  466. </varlistentry>
  467. <varlistentry>
  468. <term>-T <replaceable class="parameter">ttl</replaceable></term>
  469. <listitem>
  470. <para>
  471. Specifies the TTL to be used for new DNSKEY records imported
  472. into the zone from the key repository. If not specified,
  473. the default is the minimum TTL value from the zone's SOA
  474. record. This option is ignored when signing without
  475. <option>-S</option>, since DNSKEY records are not imported
  476. from the key repository in that case. It is also ignored if
  477. there are any pre-existing DNSKEY records at the zone apex,
  478. in which case new records' TTL values will be set to match
  479. them.
  480. </para>
  481. </listitem>
  482. </varlistentry>
  483. <varlistentry>
  484. <term>-t</term>
  485. <listitem>
  486. <para>
  487. Print statistics at completion.
  488. </para>
  489. </listitem>
  490. </varlistentry>
  491. <varlistentry>
  492. <term>-u</term>
  493. <listitem>
  494. <para>
  495. Update NSEC/NSEC3 chain when re-signing a previously signed
  496. zone. With this option, a zone signed with NSEC can be
  497. switched to NSEC3, or a zone signed with NSEC3 can
  498. be switch to NSEC or to NSEC3 with different parameters.
  499. Without this option, <command>dnssec-signzone</command> will
  500. retain the existing chain when re-signing.
  501. </para>
  502. </listitem>
  503. </varlistentry>
  504. <varlistentry>
  505. <term>-v <replaceable class="parameter">level</replaceable></term>
  506. <listitem>
  507. <para>
  508. Sets the debugging level.
  509. </para>
  510. </listitem>
  511. </varlistentry>
  512. <varlistentry>
  513. <term>-x</term>
  514. <listitem>
  515. <para>
  516. Only sign the DNSKEY RRset with key-signing keys, and omit
  517. signatures from zone-signing keys. (This is similar to the
  518. <command>dnssec-dnskey-kskonly yes;</command> zone option in
  519. <command>named</command>.)
  520. </para>
  521. </listitem>
  522. </varlistentry>
  523. <varlistentry>
  524. <term>-z</term>
  525. <listitem>
  526. <para>
  527. Ignore KSK flag on key when determining what to sign. This
  528. causes KSK-flagged keys to sign all records, not just the
  529. DNSKEY RRset. (This is similar to the
  530. <command>update-check-ksk no;</command> zone option in
  531. <command>named</command>.)
  532. </para>
  533. </listitem>
  534. </varlistentry>
  535. <varlistentry>
  536. <term>-3 <replaceable class="parameter">salt</replaceable></term>
  537. <listitem>
  538. <para>
  539. Generate an NSEC3 chain with the given hex encoded salt.
  540. A dash (<replaceable class="parameter">salt</replaceable>) can
  541. be used to indicate that no salt is to be used when generating the NSEC3 chain.
  542. </para>
  543. </listitem>
  544. </varlistentry>
  545. <varlistentry>
  546. <term>-H <replaceable class="parameter">iterations</replaceable></term>
  547. <listitem>
  548. <para>
  549. When generating an NSEC3 chain, use this many interations. The
  550. default is 10.
  551. </para>
  552. </listitem>
  553. </varlistentry>
  554. <varlistentry>
  555. <term>-A</term>
  556. <listitem>
  557. <para>
  558. When generating an NSEC3 chain set the OPTOUT flag on all
  559. NSEC3 records and do not generate NSEC3 records for insecure
  560. delegations.
  561. </para>
  562. <para>
  563. Using this option twice (i.e., <option>-AA</option>)
  564. turns the OPTOUT flag off for all records. This is useful
  565. when using the <option>-u</option> option to modify an NSEC3
  566. chain which previously had OPTOUT set.
  567. </para>
  568. </listitem>
  569. </varlistentry>
  570. <varlistentry>
  571. <term>zonefile</term>
  572. <listitem>
  573. <para>
  574. The file containing the zone to be signed.
  575. </para>
  576. </listitem>
  577. </varlistentry>
  578. <varlistentry>
  579. <term>key</term>
  580. <listitem>
  581. <para>
  582. Specify which keys should be used to sign the zone. If
  583. no keys are specified, then the zone will be examined
  584. for DNSKEY records at the zone apex. If these are found and
  585. there are matching private keys, in the current directory,
  586. then these will be used for signing.
  587. </para>
  588. </listitem>
  589. </varlistentry>
  590. </variablelist>
  591. </refsect1>
  592. <refsect1>
  593. <title>EXAMPLE</title>
  594. <para>
  595. The following command signs the <userinput>example.com</userinput>
  596. zone with the DSA key generated by <command>dnssec-keygen</command>
  597. (Kexample.com.+003+17247). Because the <command>-S</command> option
  598. is not being used, the zone's keys must be in the master file
  599. (<filename>db.example.com</filename>). This invocation looks
  600. for <filename>dsset</filename> files, in the current directory,
  601. so that DS records can be imported from them (<command>-g</command>).
  602. </para>
  603. <programlisting>% dnssec-signzone -g -o example.com db.example.com \
  604. Kexample.com.+003+17247
  605. db.example.com.signed
  606. %</programlisting>
  607. <para>
  608. In the above example, <command>dnssec-signzone</command> creates
  609. the file <filename>db.example.com.signed</filename>. This
  610. file should be referenced in a zone statement in a
  611. <filename>named.conf</filename> file.
  612. </para>
  613. <para>
  614. This example re-signs a previously signed zone with default parameters.
  615. The private keys are assumed to be in the current directory.
  616. </para>
  617. <programlisting>% cp db.example.com.signed db.example.com
  618. % dnssec-signzone -o example.com db.example.com
  619. db.example.com.signed
  620. %</programlisting>
  621. </refsect1>
  622. <refsect1>
  623. <title>SEE ALSO</title>
  624. <para><citerefentry>
  625. <refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
  626. </citerefentry>,
  627. <citetitle>BIND 9 Administrator Reference Manual</citetitle>,
  628. <citetitle>RFC 4033</citetitle>.
  629. </para>
  630. </refsect1>
  631. <refsect1>
  632. <title>AUTHOR</title>
  633. <para><corpauthor>Internet Systems Consortium</corpauthor>
  634. </para>
  635. </refsect1>
  636. </refentry><!--
  637. - Local variables:
  638. - mode: sgml
  639. - End:
  640. -->