| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2023-10-10 | s4-echo: Remove the "echo" server (port 7, RFC 862) in production builds | Andrew Bartlett | 1 | -1/+1 | |
| This demonstration should never be enabled in production, if echo service is required other software is far better positioned to provide it. Reflection attacks on echo are a known issue. This is removed for consistency with the removal of rpcecho, but was never enabled in the default smb.conf so is mostly harmless. Signed-off-by: Andrew Bartlett <abartlet@samba.org> | |||||
| 2012-05-23 | Introduce system MIT krb5 build with --with-system-mitkrb5 option. | Alexander Bokovoy | 1 | -1/+2 | |
| System MIT krb5 build also enabled by specifying --without-ad-dc When --with-system-mitkrb5 (or --withou-ad-dc) option is passed to top level configure in WAF build we are trying to detect and use system-wide MIT krb5 libraries. As result, Samba 4 DC functionality will be disabled due to the fact that it is currently impossible to implement embedded KDC server with MIT krb5. Thus, --with-system-mitkrb5/--without-ad-dc build will only produce * Samba 4 client libraries and their Python bindings * Samba 3 server (smbd, nmbd, winbindd from source3/) * Samba 3 client libraries In addition, Samba 4 DC server-specific tests will not be compiled into smbtorture. This in particular affects spoolss_win, spoolss_notify, and remote_pac rpc tests. | |||||
| 2010-12-09 | s4: Implement UDP echo server example | Kai Blin | 1 | -0/+9 | |
| This is a simple UDP-based echo server. It is mainly intended as an example on how to do server service tasks in s4. | |||||
