Click here to Skip to main content
16,020,114 members
Home / Discussions / Linux Programming
   

Linux Programming

 
GeneralRe: Opening JavaFX jar on Ubuntu Pin
Valentinor10-Jun-19 5:08
Valentinor10-Jun-19 5:08 
GeneralRe: Opening JavaFX jar on Ubuntu Pin
Richard MacCutchan10-Jun-19 5:16
mveRichard MacCutchan10-Jun-19 5:16 
GeneralRe: Opening JavaFX jar on Ubuntu Pin
Valentinor10-Jun-19 5:22
Valentinor10-Jun-19 5:22 
QuestionEDITED Where and how to change DBus security access to "name "? ( Added Link at the front of the original post.) Pin
Vaclav_2-Jun-19 5:19
Vaclav_2-Jun-19 5:19 
Addendum

The following link MAY hold the answer.
I need time to study it.

dbus-daemon[^]




I have posted the following in another (Linux) forum and got no response.
I am hoping I do better here.



The enclosed error tells me to change dbus "configuration" file.
There are few problems with such laconic error.

#1 There are no such things as single "configuration " file.
#2 What I assume is main "session.conf"( NOT configuration - just conf ) has been deleted and replaced by others in THREE different folders.
#3 The instruction in ONE of them - "session.conf" tells specifically NOT to modify this file. That is fine , I generally can follow instruction how to supplement this file BUT

#4 Is this "session.conf" the correct file to supplement ?
#5 Where / HOW EXACTLY do I change this "security " - using "session.conf" as template to be able to name my own dbus ?

PS
I understand the "session.conf" is NOT just plain script / text file so I ma reluctant to "change " anything anyway in it. (Just found out it is in HTML format, I have no experience with HTML!)

Here is the compiler error output:

conn = 0xadff00
register our name on the bus, and check for errors
TESTtest.signal.source
err.message = Connection ":1.77" is not allowed to own the service "TESTtest.signal.source" due to security policies in the configuration file
Failed dbus_bus_request_name: : Resource temporarily unavailable 


Addendum:
I have found two x.conf "system.conf" and "session.conf". Neither one of them is very intuitive to let me change the "naming" security to correct the error.



I am enclosing a copy of full "session.conf" I am supposedly modify / copy / use to change the "naming" security. I hope somebody can point out to me what needs to be changed and how to duplicate / make the "supplemental file" as instructed.

FYI - the only entry mentioning "name " is in "system.conf"

<!-- <limit name="max_connections_per_user">256</limit> -->
 <!-- <limit name="max_pending_service_starts">512</limit> -->
 <!-- <limit name="max_names_per_connection">512</limit> -->
 <!-- <limit name="max_match_rules_per_connection">512</limit> -->
 <!-- <limit name="max_replies_per_connection">128</limit> -->



PS
I have not figured out how to copy the entire "terminal" output , so there may be duplicates.
The file is included to help to identify WHAT needs to be changed.


  GNU nano 2.5.3                               File: session.conf                                                                    

<!-- This configuration file controls the per-user-login-session message bus.
     Add a session-local.conf and edit that rather than changing this
     file directly. -->

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
  <!-- Our well-known bus type, don't change this -->
  <type>session</type>

  <!-- If we fork, keep the user's original umask to avoid affecting
       the behavior of child processes. -->
  <keep_umask/>

  <listen>unix:tmpdir=/tmp</listen>

  <!-- On Unix systems, the most secure authentication mechanism is
  EXTERNAL, which uses credential-passing over Unix sockets.

  This authentication mechanism is not available on Windows,
  is not suitable for use with the tcp: or nonce-tcp: transports,
  and will not work on obscure flavours of Unix that do not have
  a supported credentials-passing mechanism. On those platforms/transports,
  comment out the <auth> element to allow fallback to DBUS_COOKIE_SHA1. -->
  <auth>EXTERNAL</auth>

  <standard_session_servicedirs />

  <policy context="default">
    <!-- Allow everything to be sent -->
    <allow send_destination="*" eavesdrop="true"/>
    <!-- Allow everything to be received -->
    <allow eavesdrop="true"/>
    <!-- Allow anyone to own anything -->
    <allow own="*"/>
  </policy>

  <!-- Include legacy configuration location -->
  <include ignore_missing="yes">/etc/dbus-1/session.conf</include>

  <!-- Config files are placed here that among other things,
       further restrict the above policy for specific services. -->
  <includedir>session.d</includedir>

  <includedir>/etc/dbus-1/session.d</includedir>

  <!-- This is included last so local configuration can override what's
       in this standard file -->
  <include ignore_missing="yes">/etc/dbus-1/session-local.conf</include>

 <!-- Include legacy configuration location -->
  <include ignore_missing="yes">/etc/dbus-1/session.conf</include>

  <!-- Config files are placed here that among other things,
       further restrict the above policy for specific services. -->
  <includedir>session.d</includedir>

  <includedir>/etc/dbus-1/session.d</includedir>

  <!-- This is included last so local configuration can override what's
       in this standard file -->
  <include ignore_missing="yes">/etc/dbus-1/session-local.conf</include>

  <include if_selinux_enabled="yes" selinux_root_relative="yes">contexts/dbus_contexts</include>

  <!-- For the session bus, override the default relatively-low limits
       with essentially infinite limits, since the bus is just running
       as the user anyway, using up bus resources is not something we need
       to worry about. In some cases, we do set the limits lower than
       "all available memory" if exceeding the limit is almost certainly a bug,
       having the bus enforce a limit is nicer than a huge memory leak. But the
       intent is that these limits should never be hit. -->

  <!-- the memory limits are 1G instead of say 4G because they can't exceed 32-bit signed int max -->
  <limit name="max_incoming_bytes">1000000000</limit>
  <limit name="max_incoming_unix_fds">250000000</limit>
  <limit name="max_outgoing_bytes">1000000000</limit>
  <limit name="max_outgoing_unix_fds">250000000</limit>
  <limit name="max_message_size">1000000000</limit>
  <!-- We do not override max_message_unix_fds here since the in-kernel
       limit is also relatively low -->
  <limit name="service_start_timeout">120000</limit>
  <limit name="auth_timeout">240000</limit>
  <limit name="pending_fd_timeout">150000</limit>
  <limit name="max_completed_connections">100000</limit>
  <limit name="max_incomplete_connections">10000</limit>
  <limit name="max_connections_per_user">100000</limit>

 <limit name="service_start_timeout">120000</limit>
  <limit name="auth_timeout">240000</limit>
  <limit name="pending_fd_timeout">150000</limit>
  <limit name="max_completed_connections">100000</limit>
  <limit name="max_incomplete_connections">10000</limit>
  <limit name="max_connections_per_user">100000</limit>
  <limit name="max_pending_service_starts">10000</limit>
  <limit name="max_names_per_connection">50000</limit>
  <limit name="max_match_rules_per_connection">50000</limit>
  <limit name="max_replies_per_connection">50000</limit>

</busconfig>



As always , any help would be greatly appreciated.
Cheers



Addendum:
Here is what is in the "removed " "session.conf" file.
Which helps a little but bring up another "question"
What is "session.d" folder for - which is empty ?

jim@jim-desktop:/usr/DBUS/share/dbus-1$ ls
services  session.conf  session.d  system.conf  system.d  system-services
jim@jim-desktop:/usr/DBUS/share/dbus-1$ cd session.d
jim@jim-desktop:/usr/DBUS/share/dbus-1/session.d$ ls


I guess I need for have
<busconfig> element containing configuration directives
in my supplemental file.


<!--
This configuration file is no longer required and may be removed.

In older versions of dbus, this file defined the behaviour of the well-known
session bus. That behaviour is now determined by
/usr/DBUS/share/dbus-1/session.conf, which should not be edited.

For local configuration changes, create a file
session-local.conf or files matching session.d/*.conf in the same directory
as this one, with a <busconfig> element containing configuration directives.
These directives can override D-Bus or OS defaults.

For upstream or distribution-wide defaults that can be overridden
by a local sysadmin, create files matching
/usr/DBUS/share/dbus-1/session.d/*.conf instead.
-->
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig></busconfig>


modified 2-Jun-19 21:12pm.

QuestionPost deleted by author Pin
Vaclav_24-May-19 4:54
Vaclav_24-May-19 4:54 
AnswerRe: Help with analyzing bluetooth "hci_inquiry" function Pin
Richard MacCutchan24-May-19 5:01
mveRichard MacCutchan24-May-19 5:01 
AnswerRe: Post deleted by author Pin
Richard MacCutchan27-May-19 5:28
mveRichard MacCutchan27-May-19 5:28 
QuestionLooking to figure out how to design a desktop and theme for an operating system based off of Linux. Can anyone point me in the right direction on how to do this? Anyone know of any books? Any tips? Any pointers? Any Forums? etc. The other parts are a Pin
justinsloan3217-May-19 22:18
justinsloan3217-May-19 22:18 
AnswerRe: Looking to figure out how to design a desktop and theme for an operating system based off of Linux. Can anyone point me in the right direction on how to do this? Anyone know of any books? Any tips? Any pointers? Any Forums? etc. The other parts a Pin
Richard MacCutchan17-May-19 22:21
mveRichard MacCutchan17-May-19 22:21 
QuestionPARTIALLY SOLVED hcitool scan with grep pipe Pin
Vaclav_17-May-19 14:14
Vaclav_17-May-19 14:14 
AnswerRe: analyze "grep" pipe Pin
Richard MacCutchan17-May-19 21:18
mveRichard MacCutchan17-May-19 21:18 
QuestionHow to retrieve "terminal" output? Pin
Vaclav_17-May-19 7:26
Vaclav_17-May-19 7:26 
AnswerRe: How to retrieve "terminal" output? Pin
Richard MacCutchan17-May-19 9:27
mveRichard MacCutchan17-May-19 9:27 
QuestionTheoretical server/site setup Pin
pyango58-May-19 12:00
pyango58-May-19 12:00 
QuestionSOLVED "configure" script option PKG_CONFIG_DEBUG_SPEW fails to run on X86 Pin
Vaclav_4-May-19 3:51
Vaclav_4-May-19 3:51 
GeneralRe: "configure" script option PKG_CONFIG_DEBUG_SPEW fails to run on X86 Pin
Richard MacCutchan4-May-19 4:56
mveRichard MacCutchan4-May-19 4:56 
Questionmissing mount.pc Pin
Vaclav_12-Apr-19 3:49
Vaclav_12-Apr-19 3:49 
AnswerRe: missing mount.pc Pin
Gerry Schmitz12-Apr-19 4:53
mveGerry Schmitz12-Apr-19 4:53 
GeneralRe: missing mount.pc Pin
Vaclav_12-Apr-19 7:53
Vaclav_12-Apr-19 7:53 
QuestionBad UDP length 736 > IP payload length Len = 728 packet drop Pin
sarali8-Apr-19 18:35
sarali8-Apr-19 18:35 
AnswerRe: Bad UDP length 736 > IP payload length Len = 728 packet drop Pin
Gerry Schmitz9-Apr-19 6:22
mveGerry Schmitz9-Apr-19 6:22 
AnswerRe: Bad UDP length 736 > IP payload length Len = 728 packet drop Pin
Randor 10-Apr-19 21:26
professional Randor 10-Apr-19 21:26 
GeneralRe: Bad UDP length 736 > IP payload length Len = 728 packet drop Pin
sarali12-Apr-19 20:43
sarali12-Apr-19 20:43 
GeneralRe: Bad UDP length 736 > IP payload length Len = 728 packet drop Pin
Randor 28-Apr-19 12:50
professional Randor 28-Apr-19 12:50 
GeneralRe: Bad UDP length 736 > IP payload length Len = 728 packet drop Pin
sarali10-May-19 2:55
sarali10-May-19 2:55 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.