openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842017-10-05T17:36:44ZopenSUSE Project Management Tool
Redmine invisAD-setup - action #25802 (Closed): Switch to firewalldhttps://progress.opensuse.org/issues/258022017-10-05T17:36:44Zflaccostefan@invis-server.org
<p>The upcoming openSUSE leap 15 replaces the traditional SuSEfirewall2 with the firewalld system. Therefor we have to migrate our fw-settings from SuSEfirewall2 to firewalld. SuSEfirewall2 is not completely replaced, but we decided to switch firewalld. The migration script susefirewall2-to-firewalld will help to migrate.</p>
invisAD-setup - action #25532 (Closed): Combine z-push and owncloud vHostshttps://progress.opensuse.org/issues/255322017-09-23T15:40:15Zflaccostefan@invis-server.org
<p>A lot of possible recipients of an owncloud share-link are behind of a proxy server. The most proxy servers block the access to ports different from the standard http(s) ports 80 and 443.</p>
invisAD-setup - action #25198 (Rejected): invis-Server Upgrade Systemhttps://progress.opensuse.org/issues/251982017-09-12T05:53:59Zflaccostefan@invis-server.org
<p>We should build an upgrade System or Script for invis-Server to support minor-release jumps.</p>
<p>Such a system has to do only the projectable things like adding new stuff (schema addons, data) to Active-Directory or setting new Versionnumbers. To do the whole upgrades automatically is impossible in my opinion. </p>
<p>Any suggestions to this topic?</p>
invisAD-setup - action #25128 (Closed): invis-Portal default configurationhttps://progress.opensuse.org/issues/251282017-09-09T10:46:30Zflaccostefan@invis-server.org
<p>We should add a default-configuration file for invis-Portal which will be updated with every new version of the invis-server portal. All entries in this default config will be overwritten with settings in /etc/invis/portal/config.php.</p>
<p>This should make updates easier, if an update contains new configuration directives.</p>
invis-server - action #24736 (Closed): Repositories are brokenhttps://progress.opensuse.org/issues/247362017-09-07T10:06:51Zflaccostefan@invis-server.org
<p>If I do a zypper ref on invis-servers I get the following answer from zypper:</p>
<p>Metadaten von Repository 'Common packages for invis-Server stable & unstable (openSUSE_42.2)' abrufen --------------------------------------[/]<br>
Datei './repodata/a710cf170ceff2acfcccc3bc4919f44d06ce7246231c684c587dced0ed348855-primary.xml.gz' auf Medium '<a href="http://download.opensuse.org/repositories/spins:/invis:/common/openSUSE_Leap_42.2/" class="external">http://download.opensuse.org/repositories/spins:/invis:/common/openSUSE_Leap_42.2/</a>' nicht gefunden</p>
<p>Abbrechen, wiederholen, ignorieren? <a href="a" class="external">a/w/i/...? zeigt alle Optionen</a>:</p>
<p>This happens with all our repos. </p>
invis-backup - action #23882 (Closed): Compare borgbackup with rdiff-backuphttps://progress.opensuse.org/issues/238822017-09-03T09:38:09Zflaccostefan@invis-server.org
<p>openSUSE 42.3 comes with the backup-software "borgbackup". It seems that borgbackup has the same advanteges to rdiff-backup and some cool features on top. A fuse driver for borg repos is available.</p>
invis-server - action #23880 (Closed): Chemnitzer Linux Tage 2018https://progress.opensuse.org/issues/238802017-09-02T21:43:55Zflaccostefan@invis-server.org
<p>Presenting invis-Server at CLT 2018</p>
invis-backup - action #23794 (Rejected): Implementing rdiff-backup-web to invis-serverhttps://progress.opensuse.org/issues/237942017-08-30T18:53:30Zflaccostefan@invis-server.org
<p>The invis-server own backup-solution "invis-rdbu" uses rdiff-backup as the main backup-tool. </p>
<p>Restoring Data from a rdiff-backup repository isn't easy enough to give our users the oportunity to restore data from the backup by themself. Implemting the fuse-based rdiff-backup Filesystem in combination with rdiff-backup-web makes it much more easy to do this job. </p>
<p>Ingo has allready build a rdiff-backup-fs package in our OBS Repos, no we can start implementing and testing rdiff-backup-web.</p>
<p>rdiff-backup-web on Sourceforge: <a href="http://rdiffbackupweb.sourceforge.net/" class="external">http://rdiffbackupweb.sourceforge.net/</a></p>
<p>Caution: This software is in an early alpha state, perhaps it isn't stabel enough for our needs. </p>
invisAD-setup - action #23792 (Closed): Showing invis-Server and openSUSE version numbers in invi...https://progress.opensuse.org/issues/237922017-08-30T18:45:29Zflaccostefan@invis-server.org
<p>We should extend the invis-portal status site, to let her show the version numbers of invis-server and openSUSE.</p>
invisAD-setup - action #23758 (Closed): Using directory templates for groupshares, create groups ...https://progress.opensuse.org/issues/237582017-08-29T09:52:56Zflaccostefan@invis-server.org
<p>If we add a new group via invis-portal on an invis-server, the server automatically creates a working-directory for this group. Only the groupmembers can access and use it.</p>
<a name="First-feature"></a>
<h2 >First feature<a href="#First-feature" class="wiki-anchor">¶</a></h2>
<p>It would be a nice addon, if we could select a directory-template from collection of templates, for creating the new workingdirectory for a new group.</p>
<p>invis-portal launches a shell-script called "creategroupshare". I added the possibility to use template-dirs to this script before. For using this feature it's only neccessary to give it the path to the templatedir as a position parameter:</p>
<p>creategroupshare /path/to/templatedir</p>
<p>To use this feature we have to add the template-dir selection to invis-portal. The selection should be a dropdown list.</p>
<a name="Second-feature"></a>
<h2 >Second feature<a href="#Second-feature" class="wiki-anchor">¶</a></h2>
<p>It should be possible to create groups without a share/directory. We will add a checkbox to the group creation dialog to disable the share creation. Default is enabled. We integrated this option in the dropdown list. The list contains "Leeres Verzeichnis" (default), "Kein Verzeichnis" and then the template directories, if there are any.</p>
<a name="Third-feature"></a>
<h2 >Third feature<a href="#Third-feature" class="wiki-anchor">¶</a></h2>
<p>The template directory needs acls. We will create a group "diradmins" with sine2. Only members of this group should be able to create, delete or modify the template directories.</p>
invisAD-setup - action #23746 (Closed): Adding sudoers rules to active directory.https://progress.opensuse.org/issues/237462017-08-29T08:02:07Zflaccostefan@invis-server.org
<p>Like described in an "Linux Administrator Magazin" article we should add support for providing sudo rules to active directory.</p>
<p>Info: <a href="http://jhrozek.livejournal.com/3860.html" class="external">http://jhrozek.livejournal.com/3860.html</a></p>
invis-backup - action #23672 (Rejected): add encryption to invis-rdbu https://progress.opensuse.org/issues/236722017-08-26T11:28:04Zflaccostefan@invis-server.org
<p>We should extend our own backup-solution invis-rdbu to support encrypted harddisks or volumes.</p>
<p>invis-rdbu can use external eSATA or USB Disks as backup targets. These targes should be encrypted for security reasons.</p>
<p>I think that it's not necessary to encrypt the backup target in case if the target is a backup-server.</p>
invis-server - action #23664 (Closed): OpenRheinRuhrhttps://progress.opensuse.org/issues/236642017-08-26T07:19:14Zflaccostefan@invis-server.org
<p>Presenting invis-Server at OpenRheinRuhr.</p>
<p>Staff: Stefan, Ines, Ingo, (Dimitri?)</p>
invis-server - action #23662 (Closed): Kieler Linux Tagehttps://progress.opensuse.org/issues/236622017-08-26T07:10:26Zflaccostefan@invis-server.org
<p>Presenting invis-Server at Kieler Linux Tage.</p>
<p>Staff: Stefan, Ines</p>
<p>invis-Server Talk: <a href="http://www.kilux.de/index.php?seite=programm.html&untermenu=Besucher-Info#325" class="external">http://www.kilux.de/index.php?seite=programm.html&untermenu=Besucher-Info#325</a></p>
invisAD-setup - action #23652 (Closed): create apparmor profiles for samba ad componentshttps://progress.opensuse.org/issues/236522017-08-25T16:41:17Zflaccostefan@invis-server.org
<p>At frOSCon 12 we started to build new apparmor profiles for samba_ad.</p>
<p>These profiles are added to the invis-server setup package but not yet ready. With these profiles samba starts as expected, but joining the domain with a computer for example didn't work.</p>
<p>In difference to samba "classic" there is one ne daemon called samba which starts a lot of subprocesses like smbd and winbindd. This new daemon substitutes the classic single daemons like "smbd" and "nmbd". Their apparmor profiles didn't work for samba with active directory.</p>
<p>This job is a showstopper for our new 13.0 release. We have to decide if we fix this immediately or release the 13.0 without activated apparmor.</p>