blob: 9463d1448f5b308be6c73769ee3e6f80b290d777 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] [changelog] [RPM] cauldron core/release wireshark-1.8.4-2.mga3
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%09wireshark-1.8.4-2.mga3&In-Reply-To=%3Ckb4tuo%24vb%241%40ger.gmane.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="020829.html">
<LINK REL="Next" HREF="020830.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] [changelog] [RPM] cauldron core/release wireshark-1.8.4-2.mga3</H1>
<B>David Walser</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%09wireshark-1.8.4-2.mga3&In-Reply-To=%3Ckb4tuo%24vb%241%40ger.gmane.org%3E"
TITLE="[Mageia-dev] [changelog] [RPM] cauldron core/release wireshark-1.8.4-2.mga3">luigiwalser at yahoo.com
</A><BR>
<I>Sat Dec 22 19:25:30 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="020829.html">[Mageia-dev] [changelog] [RPM] cauldron core/release wireshark-1.8.4-2.mga3
</A></li>
<LI>Next message: <A HREF="020830.html">[Mageia-dev] python guru?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20886">[ date ]</a>
<a href="thread.html#20886">[ thread ]</a>
<a href="subject.html#20886">[ subject ]</a>
<a href="author.html#20886">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Jani Välimaa wrote:
><i> On Mon, 17 Dec 2012 09:57:13 +0000
</I>><i> Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote:
</I>><i>
</I>>><i> 'Twas brillig, and Olivier Blin at 17/12/12 09:55 did gyre and gimble:
</I>>><i> > wally <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">buildsystem-daemon at mageia.org</A>> writes:
</I>>><i> >
</I>>><i> >> Name : wireshark Relocations: (not
</I>>><i> >> relocatable) Version : 1.8.4
</I>>><i> >> Vendor: Mageia.Org Release : 2.mga3
</I>>><i> >> Build Date: Sat Dec 1 17:48:14 2012 Install Date: (not
</I>>><i> >> installed) Build Host: jonund.mageia.org
</I>>><i> >> Group : Monitoring Source RPM: (none)
</I>>><i> >> Size : 24192404 License: GPLv2+ and
</I>>><i> >> GPLv3 Signature : (none) Packager : wally <wally>
</I>>><i> >> URL : <A HREF="http://www.wireshark.org">http://www.wireshark.org</A>
</I>>><i> >> Summary : Network traffic analyzer
</I>>><i> >> Description :
</I>>><i> >> Wireshark is a network traffic analyzer for Unix-ish operating
</I>>><i> >> systems. It is based on GTK+, a graphical user interface library,
</I>>><i> >> and libpcap, a packet capture and filtering library.
</I>>><i> >>
</I>>><i> >> wally <wally> 1.8.4-2.mga3:
</I>>><i> >> + Revision: 324195
</I>>><i> >> - install dumpcap setuid root as upstream suggests (to allow to
</I>>><i> >> start wireshark as normal user)
</I>>><i> >> - drop run-as-root hacks
</I>>><i> >
</I>>><i> > Hi,
</I>>><i> >
</I>>><i> > It seems you introduced a security flaw: now all users are able to
</I>>><i> > capture the network traffic.
</I>>><i> >
</I>>><i> > This should be reverted, or restrictions should be added (maybe by
</I>>><i> > making consolekit add acls if possible).
</I>>><i>
</I>>><i> Perhaps only make it only work for users in the wheel group?
</I>>><i>
</I>><i>
</I>><i> Ah, yes. Didn't think that much. :\
</I>><i>
</I>><i> As Colin suggested we could "chgrp wheel /usr/bin/dumpcap && chmod
</I>><i> 4750 /usr/bin/dumpcap". Or we could create wireshark group for it and
</I>><i> do the same.
</I>
I see you did the wireshark group (better choice than wheel for sure). Personally I prefer Olivier's consolekit suggestion, to allow the
user logged into the physical console to use it. Much less of a management headache in most cases. The restricting it to a group should be
something an administrator can enforce with msec if they want it (and it could even be added to the default restrictions for the secure
level).
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="020829.html">[Mageia-dev] [changelog] [RPM] cauldron core/release wireshark-1.8.4-2.mga3
</A></li>
<LI>Next message: <A HREF="020830.html">[Mageia-dev] python guru?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20886">[ date ]</a>
<a href="thread.html#20886">[ thread ]</a>
<a href="subject.html#20886">[ subject ]</a>
<a href="author.html#20886">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
