| Summary: | How do you remove all of Samba without gutting TDE? | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Michael <mb_trinity_desktop> |
| Component: | tdenetwork | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | albator78, bugwatch, gamrat.kristopher, mb_trinity_desktop, slavek.banko, wofgdkncxojef |
| Priority: | P5 | ||
| Version: | R14.0.x [Trinity] | ||
| Hardware: | amd64 | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2696 | ||
| Attachments: | tdemultimedia: fix detection on cdda include files when using cmake | ||
|
Description
Michael
2017-07-14 18:12:47 CDT
This is a problem at present. The tdebase package is compiled with smbclient support, so the tdebase-tdeio-plugins package depends on libsmbclient. And libsmbclient package then can depend on samba-libs (in Samba4 case). The only solution would be to split tdeio-smb plugin into a separate package - for example tdebase-tdeio-plugin-smb. However, even that does not work completely - on libsmbclient depends also libxine2-misc-plugins => libxine2. If there will be consent, we can split the tdeio-smb into a separate package. Hi Slávek,
Ofta! Way more work than I desired :( Or would even reasonably expect.
Okay, how about just a guide, FAQ entry?, on how to remove as much as possible of the Samba client and server?
I’ll copy/paste/re-write for a potential FAQ entry:
====
Title: Removing Samba from TDE
Removing Samba from the Trinity Desktop Environment (TDE) is a problem at present. The tdebase package is compiled with smbclient support, so the tdebase-tdeio-plugins package depends on libsmbclient. And libsmbclient package then can depend on samba-libs.
To remove all Samba packages TDE has no dependencies on, run:
$ sudo apt-get purge samba samba-common python-samba {insert all the other non-dependent samba/smb/??? mods}
====
I’m just trying to reduce security exposures, so dumping most of Samba works for me, and unless y’all at TDE think it’s a security issue, I don’t see any need for pulling the base lib’s if the Samba client/server interface can be removed. (As I would expect the attack vector would be against the client/server interface, yes?)
Best,
Michael
PS: I’m blind? Or I just haven’t used this system enough, would someone change this to a Feature Request? I can’t see how it’s really a bug.
Created attachment 2801 [details]
tdemultimedia: fix detection on cdda include files when using cmake
Not for TDE 14.0.4 (still using autotools) but for upcoming 14.0.5 (using cmake), an FTBFS occurs because "cdda_interface.h" is located under '/usr/include/cdda', not '/usr/include'.
Comment on attachment 2801 [details]
tdemultimedia: fix detection on cdda include files when using cmake
Sorry, wrong bug report. I was targeting 2789, not 2788.
Ideally, Samba should not be required at all for a base install of TDE. Not everyone needs or wants it. RPM supports creation of sub-packages, so it's (relatively) simple to split out tdeio-smb and the other tdeio slaves into their own packages when building the RPM packages. What about on the DPKG end? (I'm not too familiar with DPKG from the packager's side of things, so I don't know if it supports sub-packages or not) (In reply to Kristopher from comment #5) > Ideally, Samba should not be required at all for a base install of TDE. Not > everyone needs or wants it. > > RPM supports creation of sub-packages, so it's (relatively) simple to split > out tdeio-smb and the other tdeio slaves into their own packages when > building the RPM packages. > > What about on the DPKG end? (I'm not too familiar with DPKG from the > packager's side of things, so I don't know if it supports sub-packages or > not) See my comment 1. For Debian / Ubuntu resolved by GIT commits 30b61683 (master) and e8dd79c8 (r14.0.x). You forgot to close this, or other distributions are pending? I looked at RPM packages - yes, it seems that here is tdeio-smb as a separate package. So the bug report can be closed. |