tde-devels

devels@trinitydesktop.org

6 participants
3856 discussions

Re: [trinity-devel] Distro ISOs with 3.5.13.2
by Darrell Anderson 22 Nov '13

22 Nov '13

>For example Ubuntu 12.04 (LTS) LiveCD? > >http://ppa.quickbuild.pearsoncomputing.net/trinity/cdimages/kubuntu >/precise/tde-3.5.13.2-ubuntu-12.04.2-desktop-amd64.iso Thank you. What was the final Qt3 version number in 3.5.13.2? 3.3.8.d? Darrell

2 1

Distro ISOs with 3.5.13.2
by Darrell Anderson 21 Nov '13

21 Nov '13

All, For testing purposes I need a copy of 3.5.13.2. I appreciate direct links to any premade distro ISO images made with 3.5.13.2. Thank you! :-) Darrell

2 1

R14.0.0 README
by Darrell Anderson 14 Nov '13

14 Nov '13

All, I posted an initial draft of a README file to be used with the official R14.0.0 release. Please review and edit! http://trinity.etherpad.trinitydesktop.org/78 Darrell

1 0

TDE in Arch Linux?
by Axel Schöner 12 Nov '13

12 Nov '13

Hello, how is the status to get TDE running in Arch Linux? Are there any plans to get this working in nearest future? Axel Schöner

4 4

Re: [trinity-devel] Solution for hardcoded sudo in konsole schemas
by Darrell Anderson 10 Nov '13

10 Nov '13

>to resolve bug report 853 is ready a patch that selects between >"sudo su" >and "su" depending on the build option WITH_SUDO_TDESU_BACKEND. > >But as we have noticed, also on Ubuntu is used >WITH_SUDO_TDESU_BACKEND=OFF. >This would mean that even Ubuntu would not be used "sudo". > >That's why I asked what solution to choose for Ubuntu packaging? > >1) Apply the patch and leave WITH_SUDO_TDESU_BACKEND=OFF >2) Apply the patch, but change WITH_SUDO_TDESU_BACKEND=ON >3) Make a separate build option WITH_SUDO_KONSOLE_BACKEND > >See: http://bugs.pearsoncomputing.net/show_bug.cgi?id=853 I'm not an Ubuntu user but I'm fine with adding WITH_SUDO_KONSOLE_BACKEND as a new option. Would the default be WITH_SUDO_KONSOLE_BACKEND=OFF, meaning sudo- based disto packagers would have to explicitly change that option to WITH_SUDO_KONSOLE_BACKEND=ON? Darrell

2 1

Solution for hardcoded sudo in konsole schemas
by Slávek Banko 10 Nov '13

10 Nov '13

Hi all, to resolve bug report 853 is ready a patch that selects between "sudo su" and "su" depending on the build option WITH_SUDO_TDESU_BACKEND. But as we have noticed, also on Ubuntu is used WITH_SUDO_TDESU_BACKEND=OFF. This would mean that even Ubuntu would not be used "sudo". That's why I asked what solution to choose for Ubuntu packaging? 1) Apply the patch and leave WITH_SUDO_TDESU_BACKEND=OFF 2) Apply the patch, but change WITH_SUDO_TDESU_BACKEND=ON 3) Make a separate build option WITH_SUDO_KONSOLE_BACKEND See: http://bugs.pearsoncomputing.net/show_bug.cgi?id=853 Thank you Slavek

1 0

RE: [trinity-devel] Possible security glitch with switching users?
by Darrell Anderson 10 Nov '13

10 Nov '13

>Agreed, the behavior should be as you described and should be >consistent all the times. >Since you can reproduce the problem several times, I think there >is enough material to open a new bug report. Tim implied the witnessed behavior is correct. One of you gurus would have to walk through the code to determine whether locking is expected when not explicitly selected from the menu. Darrell

1 0

Re: [trinity-devel] Possible security glitch with switching users?
by Darrell Anderson 10 Nov '13

10 Nov '13

>Darrell, how long did you work in one session before switching to >the other one? Just wondering if there is some kind of inactivity >timer that locks a session when not being used for a while. That >may explain the different behavior you have seen, even though it >sounds a little weird to say the least Not long, about 5 seconds. Another person suggested there might be a timeout of some sort regulating when the lock dialog appears. Yet I'm confused. Seems to me there should be no password required when using 'Start New Session' --- that is what the 'Lock Current & Start New Session' option should be for. Darrell

2 1

Re: [trinity-devel] Possible security glitch with switching users?
by Darrell Anderson 10 Nov '13

10 Nov '13

>AFAIK "Start New Session" does not lock the current session, >whereas >selecting an existing session will lock the current session. On my >systems >there is a second menu entry for "Lock Current & Start New >Session" if it >is desired to lock the screen before starting the new session. That is confusing behavior to me. I'll guess confusing to others too. Darrell

1 0

Re: [trinity-devel] Possible security glitch with switching users?
by Darrell Anderson 10 Nov '13

10 Nov '13

>I don't know whether this is a security glitch or PEBKAC. > >I was testing the graphical login with TDM: > >* I logged in as User 1. >* From the TDE menu I selected Switch User->Start New Session. >* I logged in as User 2. >* I switched to User 1 *without* needing a password. >* I switched to User 2 and needed a password. >* I typed the password, switched to User 1, and needed a password. > >I repeated this exercise three times with a system reboot each >time. Each time the first instance of switching did not require a >password. > >Further, I was not always asked for a password on subsequent >switching, especially when I used the keyboard toggles of Ctrl-Alt- > >F7 and Ctrl-Alt-F8. > >SAK is disabled. > >I only used Switch User->Start New Session. I did not use Switch >User->Lock Current & Start New Session. > >Thoughts? BTW, seems to me there should be no password required when using 'Start New Session' --- that is what the 'Lock Current & Start New Session' option should be for? Darrell

3 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels