On 06/30/2017 06:50 PM, William Mattison wrote:
I did what was advised. Still no change. But I think there is a more fundamental
problem here. The grub on my system came from"Boot-Repair-Disk", on a live-usb
stick, not from any dnf install from a Fedora repository. So if Fedora's grub is
c
On 06/28/2017 08:33 PM, William Mattison wrote:
I believe Stan is correct. I built this system 4+ years ago. At that time, it
was my understanding that to get a windows-7 and Fedora dual-boot system, I had
to install windows-7 first. I think that at that time, windows-7 did not
support UEFI
Wow. Hot topic! I view all this here:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
In past threads, the oldest messages were at the top, and the newest at the
bottom. Why is it "upside down" in this thread?!
I have skimmed the responses so far. But I've had to f
Hi,
On Fri, Jun 30, 2017 at 6:41 PM, Ed Greshko wrote:
> On 07/01/17 06:33, Rick Stevens wrote:
>> On 06/30/2017 01:50 PM, Garry T. Williams wrote:
>>> On Thursday, June 29, 2017 11:27:04 PM EDT Alex wrote:
When I attempt to start the service, journalctl -xe shows me:
Validation failed
Good evening,
I did what was advised. Still no change. But I think there is a more
fundamental problem here. The grub on my system came from"Boot-Repair-Disk",
on a live-usb stick, not from any dnf install from a Fedora repository. So if
Fedora's grub is customized or specialized in some wa
On 06/30/2017 06:14 PM, William Oliver wrote:
> On Sat, 2017-07-01 at 10:23 +1000, Cameron Simpson wrote:
>> [snip]
>>
>> If you cannot set up a key on the foreign machine ahead of time, yes
>> stick your
>> "travelling" key on a USB stick and use it. That way you can revoke
>> it if
>> somehow i
On 07/01/17 09:14, William Oliver wrote:
> On Sat, 2017-07-01 at 10:23 +1000, Cameron Simpson wrote:
>> [snip]
>>
>> If you cannot set up a key on the foreign machine ahead of time, yes
>> stick your
>> "travelling" key on a USB stick and use it. That way you can revoke
>> it if
>> somehow it get
On Sat, 2017-07-01 at 10:23 +1000, Cameron Simpson wrote:
> [snip]
>
> If you cannot set up a key on the foreign machine ahead of time, yes
> stick your
> "travelling" key on a USB stick and use it. That way you can revoke
> it if
> somehow it gets comprimised.
>
> Cheers,
> Cameron Simpson
>
On 30Jun2017 16:53, jdow wrote:
On 2017-06-30 16:08, Cameron Simpson wrote:
You omitted way 0: DO NOT ALLOW PASSWORD BASED SSH. This is the single best
thing you can do. Allowing only key-based access simply prevents all password
based access and is cryptographicly strong, instead human-prose-
On 06/30/2017 04:47 PM, George R Goffe wrote:
I have the caps lock key mapped to the ctrl key so when I type ALL caps I have to hold
down the shift key. When I try to insert a space between words I have to release the
shift key, otherwise the space is ignored. This used to work but since I rein
On 2017-06-30 16:08, Cameron Simpson wrote:
On 30Jun2017 10:11, Greg Woods wrote:
On Fri, Jun 30, 2017 at 9:36 AM, Tim wrote:
It's not necessarily a target on *you*, but very probably it's just
targeting any computer that responds to them. Poke, get a response,
keep prodding...
Yeah, prett
Hi,
I'm running Fedora 27 x86_64 (rawhide) and have noticed a problem in text
windows with Firefox.
The problem exists in both the FF released version AND the FF beta version. It
could be Firefox.
The problem exists with KDE and WindowMaker as the desktop manager.
What I'm seeing:
I have the
On 2017-06-30 15:35, Ed Greshko wrote:
On 06/30/17 09:10, jdow wrote:
A rule like this makes cracking your 123456 password a whole lot harder without
changing anything else.
iptables -t filter -A IN_public_deny -p tcp --dport pop3s --syn -m recent --name
pop3s_attack --rcheck --seconds 90 --hitc
On 30Jun2017 10:11, Greg Woods wrote:
On Fri, Jun 30, 2017 at 9:36 AM, Tim wrote:
It's not necessarily a target on *you*, but very probably it's just
targeting any computer that responds to them. Poke, get a response,
keep prodding...
Yeah, pretty much all of this is totally automated these
On Fri, Jun 30, 2017 at 04:02:55PM -0700, Rick Stevens wrote:
> Also make sure you don't allow ssh root logins. Newer sshd configs
> have that set by default but some older ones allow root. Check your
> config to be sure.
Absolutely.
> "Just because I'm paranoid doesn't mean they AREN'T out to ge
On 06/30/2017 03:49 PM, Dave Ihnat wrote:
> On Sat, Jul 01, 2017 at 06:35:54AM +0800, Ed Greshko wrote:
>> On 06/30/17 09:10, jdow wrote:
>> I once did rate limiting on brute force login attempts. But I found
>> that all the attempts were scripted. So instead of an attack from a
>> single IP addr
On Sat, Jul 01, 2017 at 06:35:54AM +0800, Ed Greshko wrote:
> On 06/30/17 09:10, jdow wrote:
> I once did rate limiting on brute force login attempts. But I found
> that all the attempts were scripted. So instead of an attack from a
> single IP address happening for a minute or so the attack simp
On 07/01/17 06:33, Rick Stevens wrote:
> On 06/30/2017 01:50 PM, Garry T. Williams wrote:
>> On Thursday, June 29, 2017 11:27:04 PM EDT Alex wrote:
>>> When I attempt to start the service, journalctl -xe shows me:
>>> Validation failed for option 'ModulesDir' with value
>>> '/usr/local/savapi-sdk-l
On 06/30/17 09:10, jdow wrote:
> A rule like this makes cracking your 123456 password a whole lot harder
> without
> changing anything else.
> iptables -t filter -A IN_public_deny -p tcp --dport pop3s --syn -m recent
> --name
> pop3s_attack --rcheck --seconds 90 --hitcount 2 -j LOG --log-prefix '
On 06/30/2017 01:50 PM, Garry T. Williams wrote:
> On Thursday, June 29, 2017 11:27:04 PM EDT Alex wrote:
>> When I attempt to start the service, journalctl -xe shows me:
>> Validation failed for option 'ModulesDir' with value
>> '/usr/local/savapi-sdk-linux_glibc24_x86_64/modules'. Path cannot be
On Thursday, June 29, 2017 11:27:04 PM EDT Alex wrote:
> When I attempt to start the service, journalctl -xe shows me:
> Validation failed for option 'ModulesDir' with value
> '/usr/local/savapi-sdk-linux_glibc24_x86_64/modules'. Path cannot be
> accessed (no write permission).
>
> ModulesDir is /
On Thu, 29 Jun 2017 23:27:04 -0400
Alex wrote:
> Hi,
> I'm trying to write a service file for a daemon and having some
> problems. I believe the issue is with the ability to give the process
> write and read access to parts of the filesystem which appear to
> somehow be restricted.
[snip]
You'l
On 06/30/2017 10:12 AM, Rick Stevens wrote:
> On 06/29/2017 07:20 PM, Doug wrote:
>>
>> On 06/29/2017 09:08 PM, JD wrote:
>>>
>>>
>>> On 06/29/2017 07:48 PM, Doug wrote:
On 06/29/2017 08:32 PM, JD wrote:
>
>
> On 06/29/2017 07:10 PM, jdow wrote:
>> iptables -t filter -A IN
On 06/29/2017 07:20 PM, Doug wrote:
>
> On 06/29/2017 09:08 PM, JD wrote:
>>
>>
>> On 06/29/2017 07:48 PM, Doug wrote:
>>>
>>> On 06/29/2017 08:32 PM, JD wrote:
On 06/29/2017 07:10 PM, jdow wrote:
> iptables -t filter -A IN_public_deny -p tcp --dport pop3s --syn -m
> recent
On Sat, 01 Jul 2017 01:15:02 +0930
Tim wrote:
> It's not as far-fetched as you might think.
>
> One day I noticed, while in the middle of browsing, that the "camera
> is on" LED had lit up, though not noticing *when* it came on. I
> wasn't doing anything nefarious, so somewhere in the midst o
On Fri, Jun 30, 2017 at 9:36 AM, Tim wrote:
> It's not necessarily a target on *you*, but very probably it's just
> targeting any computer that responds to them. Poke, get a response,
> keep prodding...
>
Yeah, pretty much all of this is totally automated these days. There are
programs out ther
On Fri, 30 Jun 2017 04:29:12 -
"William Mattison" wrote:
> > Add the entry
> > GRUB_DISABLE_SUBMENU=y
> > to the /etc/default/grub file.
>
> That made no difference. Then I did "grub2-mkconfig". Still no
> difference.
Try GRUB_DISABLE_SUBMENU=true
The documentation could be out of date
Allegedly, on or about 29 June 2017, stan sent:
> after the comments in this thread, I think maybe I'm not paranoid
> enough. That the IT security professionals are paranoid enough to
> cover their cameras? If they're that worried they're vulnerable, it's
> a good bet I should be. :-)
It's not
"William Mattison"
>> What's going on? How do I determine where they're coming from? Is
>> there really someone or something trying to hack in? If no, what
>> really is going on?
stan:
> I'd say someone is trying to target your system. I used to see a lot
> of this kind of thing, except it was
On Fri, Jun 30, 2017 at 09:40:30AM +0100, Gary Stainburn wrote:
> However, I still have a number of WinXP machines running – through
> necessity.
I'm so sorry for you. I've gotten rid of all of them at my clients,
through a mixture of software/hardware upgrades, or in the absolute worst
cases run
On Fri, Jun 30, 2017 at 08:53:07AM -0400, Tom Horsley wrote:
> Which is why you can get computer cases that are physically
> secured with keypads and locks and hardware records of when
> case was opened, etc. (of course they get expensive :-).
Eh, not so much; most business-class machines have BIO
On Thu, 29 Jun 2017 23:05:09 -0400
William Oliver wrote:
> He was always amused
> by all this firewall and virus detection stuff; it doesn't mean
> anything when you have a keylogger, a warrant, a flashlight, and hands
> on a box.
Which is why you can get computer cases that are physically
secure
On Thu, 29 Jun 2017 20:08:20 -0600, JD wrote:
> >>> iptables -t filter -A IN_public_deny -p tcp --dport pop3s --syn -m
> >>> recent --name pop3s_attack --rcheck --seconds 90 --hitcount 2 -j LOG
> >>> --log-prefix 'SSH2 REJECT: ' --log-level info
> >> My iptables replied:
> >> iptables: No cha
On Thu, 2017-06-29 at 19:34 -0700, stan wrote:
> The consensus seems to agree with me, that this is a minor threat
> as threats go.
>
> I thought I was paranoid about security. But after the comments in
> this
> thread, I think maybe I'm not paranoid enough. That the IT security
> professionals
On 06/30/17 17:50, jdow wrote:
> On 2017-06-29 23:25, Samuel Sieb wrote:
>> On 06/29/2017 06:24 PM, Doug wrote:
>>> I tried to write this command to a root console in PCLInuxOS, but it got
>>> rejected.
>>>
>>> [root@linux1 doug]# iptables -t filter -A IN_public_deny -p tcp --dport
>>> pop3s
>>>
On 06/30/17 15:01, Frank Elsner wrote:
> for reasons I have to send the input from an audio interface to an other.
>
> I can do this with
>
>pactl load-module module-loopback \
>
> source="alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" \
>sink="alsa_output.usb-M-AUD
On 2017-06-29 23:25, Samuel Sieb wrote:
On 06/29/2017 06:24 PM, Doug wrote:
I tried to write this command to a root console in PCLInuxOS, but it got
rejected.
[root@linux1 doug]# iptables -t filter -A IN_public_deny -p tcp --dport pop3s
--syn -m recent --name pop3s_attack --rcheck --seconds 9
On Friday 30 June 2017 03:59:59 William Oliver wrote:
> The thing that amazes me about the Window and Mac worlds is that people
> never seem to wipe their boxes. I know people who run their machines
> for four or five years without ever doing a clean reinstall. I worked
> at a place that ran Wind
Hello,
for reasons I have to send the input from an audio interface to an other.
I can do this with
pactl load-module module-loopback \
source="alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" \
sink="alsa_output.usb-M-AUDIO_M-Track_Hub-00.analog-stereo"
and this wo
39 matches
Mail list logo
