Home Esplora Aiuto
Accedi
SoftwareDesign
/
csu3_am335x
8
0
Forka 0
File Problemi 0 Pull Requests 0 Wiki
Ramo (Branch): master
Rami (Branch) Tag
csu3_am335x
/
EVSE
/
GPL
/
dropbear-2022.82
/
SMALL

SMALL 1.9 KB
Permalink Cronologia Originale

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950 
  1. Tips for a small system:
    2. 

  2. 

  3. If you only want server functionality (for example), compile with
    4. 

  4. 	make PROGRAMS=dropbear
    5. 

  5. rather than just
    6. 

  6. 	make dropbear
    7. 

  7. so that client functionality in shared portions of Dropbear won't be included.
    8. 

  8. The same applies if you are compiling just a client.
    9. 

  9. 

  10. ---
    11. 

  11. 

  12. The following are set in localoptions.h:
    13. 

  13. 

  14. 	- If you're compiling statically, you can turn off host lookups
    15. 

  15. 

  16. 	- You can disable either password or public-key authentication, though note
    17. 

  17. 	  that the IETF draft states that pubkey authentication is required.
    18. 

  18. 

  19. 	- Similarly with DSS and RSA, you can disable one of these if you know that
    20. 

  20. 	  all clients will be able to support a particular one. The IETF draft
    21. 

  21. 	  states that DSS is required, however you may prefer to use RSA. 
    22. 

  22. 	  DON'T disable either of these on systems where you aren't 100% sure about
    23. 

  23. 	  who will be connecting and what clients they will be using.
    24. 

  24. 

  25. 	- Disabling the MOTD code and SFTP-SERVER may save a small amount of codesize
    26. 

  26. 

  27. 	- You can disable x11, tcp and agent forwarding as desired. None of these are
    28. 

  28. 	  essential, although agent-forwarding is often useful even on firewall boxes.
    29. 

  29. 

  30. ---
    31. 

  31. 

  32. If you are compiling statically, you may want to disable zlib, as it will use
    33. 

  33. a few tens of kB of binary-size (./configure --disable-zlib).
    34. 

  34. 

  35. You can create a combined binary, see the file MULTI, which will put all
    36. 

  36. the functions into one binary, avoiding repeated code.
    37. 

  37. 

  38. If you're compiling with gcc, you might want to look at gcc's options for
    39. 

  39. stripping unused code. The relevant vars to set before configure are:
    40. 

  40. 

  41. LDFLAGS=-Wl,--gc-sections
    42. 

  42. CFLAGS="-ffunction-sections -fdata-sections"
    43. 

  43. 

  44. You can also experiment with optimisation flags such as -Os, note that in some
    45. 

  45. cases these flags actually seem to increase size, so experiment before
    46. 

  46. deciding.
    47. 

  47. 

  48. Of course using small C libraries such as uClibc and dietlibc can also help.
    49. 

  49. 

  50. If you have any queries, mail me and I'll see if I can help.
    51.