Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #97282 > unrolled thread

Calendar spam!

Back to article view | Back to comp.sys.mac.system

Contents

  Calendar spam! Tim McNamara <timmcn@bitstream.net> - 2016-11-25 16:52 -0600
    Re: Calendar spam! Savageduck <savageduck1@{REMOVESPAM}me.com> - 2016-11-25 15:12 -0800
      Re: Calendar spam! nospam <nospam@nospam.invalid> - 2016-11-25 18:21 -0500
        Re: Calendar spam! Savageduck <savageduck1@{REMOVESPAM}me.com> - 2016-11-25 15:46 -0800
        Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-25 18:55 -0500
    Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-25 18:29 -0500
      Re: Calendar spam! Savageduck <savageduck1@{REMOVESPAM}me.com> - 2016-11-25 15:47 -0800
      Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-25 16:05 -0800
        Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-25 19:09 -0500
          Re: Calendar spam! Savageduck <savageduck1@{REMOVESPAM}me.com> - 2016-11-25 16:13 -0800
            Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-25 19:15 -0500
      Re: Calendar spam! Lewis <g.kreme@gmail.com.dontsendmecopies> - 2016-11-26 00:57 +0000
        Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-25 17:25 -0800
        Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-25 20:31 -0500
        Re: Calendar spam! Savageduck <savageduck1@{REMOVESPAM}me.com> - 2016-11-25 17:36 -0800
    Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-25 15:59 -0800
    Re: Calendar spam! Alrescha <alrescha@gmail.com> - 2016-11-25 19:20 -0500
      Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-25 16:25 -0800
        Re: Calendar spam! Alrescha <alrescha@gmail.com> - 2016-11-25 19:34 -0500
      Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-25 19:28 -0500
        Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-25 16:29 -0800
          Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-25 19:31 -0500
    Re: Calendar spam! Lewis <g.kreme@gmail.com.dontsendmecopies> - 2016-11-26 00:53 +0000
      Re: Calendar spam! Tim McNamara <timmcn@bitstream.net> - 2016-11-26 14:01 -0600
        Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-26 15:14 -0500
        Re: Calendar spam! Lewis <g.kreme@gmail.com.dontsendmecopies> - 2016-11-26 20:14 +0000
        Re: Calendar spam! Alrescha <alrescha@gmail.com> - 2016-11-26 15:24 -0500
        Re: Calendar spam! Jolly Roger <jollyroger@pobox.com> - 2016-11-27 00:48 +0000
          Re: Calendar spam! Tim McNamara <timmcn@bitstream.net> - 2016-11-28 22:52 -0600
    Re: Calendar spam! Doc O'Leary  <droleary@2015usenet1.subsume.com> - 2016-11-26 16:52 +0000
      Re: Calendar spam! Jolly Roger <jollyroger@pobox.com> - 2016-11-26 17:01 +0000
        Re: Calendar spam! dempson@actrix.gen.nz (David Empson) - 2016-11-28 09:17 +1300
          Re: Calendar spam! Doc O'Leary  <droleary@2015usenet1.subsume.com> - 2016-11-28 02:48 +0000
            Re: Calendar spam! Jolly Roger <jollyroger@pobox.com> - 2016-11-28 04:00 +0000
            SSH to another port (was Re: Calendar spam!) David Ritz <dritz@mindspring.com> - 2016-11-28 17:15 -0600
              Re: SSH to another port (was Re: Calendar spam!) Doc O'Leary  <droleary@2015usenet1.subsume.com> - 2016-11-29 14:21 +0000
                Re: SSH to another port (was Re: Calendar spam!) Alrescha <alrescha@gmail.com> - 2016-11-29 12:51 -0500
                  Re: SSH to another port (was Re: Calendar spam!) Lewis <g.kreme@gmail.com.dontsendmecopies> - 2016-11-29 21:47 +0000
                    Re: SSH to another port (was Re: Calendar spam!) Alrescha <alrescha@gmail.com> - 2016-11-29 18:12 -0500
                  Re: SSH to another port (was Re: Calendar spam!) Doc O'Leary  <droleary@2015usenet1.subsume.com> - 2016-11-30 17:02 +0000
                    Re: SSH to another port (was Re: Calendar spam!) Alrescha <alrescha@gmail.com> - 2016-11-30 13:27 -0500
                      Re: SSH to another port (was Re: Calendar spam!) Doc O'Leary  <droleary@2015usenet1.subsume.com> - 2016-12-01 14:40 +0000
      Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-26 12:06 -0500
      Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-26 16:45 -0800
        Re: Calendar spam! Doc O'Leary  <droleary@2015usenet1.subsume.com> - 2016-11-27 16:27 +0000
          Re: Calendar spam! Jolly Roger <jollyroger@pobox.com> - 2016-11-27 16:53 +0000
          Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-27 13:00 -0800
            Re: Calendar spam! Doc O'Leary  <droleary@2015usenet1.subsume.com> - 2016-11-28 02:32 +0000
              Re: Calendar spam! nospam <nospam@nospam.invalid> - 2016-11-27 21:41 -0500
              Re: Calendar spam! Jolly Roger <jollyroger@pobox.com> - 2016-11-28 03:39 +0000
              Re: Calendar spam! Lewis <g.kreme@gmail.com.dontsendmecopies> - 2016-11-28 06:29 +0000
              Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-28 02:00 -0800
                Re: Calendar spam! Doc O'Leary  <droleary@2015usenet1.subsume.com> - 2016-11-28 19:02 +0000
                  Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-28 12:36 -0800
                    Re: Calendar spam! Doc O'Leary  <droleary@2015usenet1.subsume.com> - 2016-11-29 14:44 +0000
                      Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-29 08:50 -0800
                        Re: Calendar spam! Jolly Roger <jollyroger@pobox.com> - 2016-11-29 18:26 +0000
                      Re: Calendar spam! Jolly Roger <jollyroger@pobox.com> - 2016-11-29 18:23 +0000
                  Re: Calendar spam! Jolly Roger <jollyroger@pobox.com> - 2016-11-28 20:37 +0000
                  Re: Calendar spam! Lewis <g.kreme@gmail.com.dontsendmecopies> - 2016-11-29 01:38 +0000
              Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-28 13:01 -0800
              Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-28 16:54 -0500
                Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-29 17:20 -0500
                  Re: Calendar spam! Alan Baker <alangbaker@telus.net> - 2016-11-29 14:22 -0800
    Re: Calendar spam! MeV <michael.vilain@gmail.com> - 2016-11-26 11:32 -0800
      Re: Calendar spam! Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-26 14:41 -0500
    Re: Calendar spam! Electric Comet <electric-comet@mail.invalid> - 2016-11-26 19:59 -0800
      Re: Calendar spam! Tim McNamara <timmcn@bitstream.net> - 2016-11-28 22:53 -0600

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

#97303

On 2016-11-25 4:28 PM, Alan Browne wrote:
> On 2016-11-25 19:20, Alrescha wrote:
>> On 2016-11-25 22:52:52 +0000, Tim McNamara <timmcn@bitstream.net> said:
>>
>>> Today I got my first and second Calendar.app spam on my Mac...
>>
>> Mail/Preferences/General/Add invitations to Calendar:  Never
>
> Violates automagically.
>
>

You've already been told how to turn it off via the icloud.com website...

[toc] | [prev] | [next] | [standalone]

#97304

On 2016-11-25 19:29, Alan Baker wrote:
> On 2016-11-25 4:28 PM, Alan Browne wrote:
>> On 2016-11-25 19:20, Alrescha wrote:
>>> On 2016-11-25 22:52:52 +0000, Tim McNamara <timmcn@bitstream.net> said:
>>>
>>>> Today I got my first and second Calendar.app spam on my Mac...
>>>
>>> Mail/Preferences/General/Add invitations to Calendar:  Never
>>
>> Violates automagically.
>>
>>
>
> You've already been told how to turn it off via the icloud.com website...

Above = humour.

-- 
She hummed to herself because she was an unrivaled botcher of lyrics.
   -Nick (Gone Girl), Gillian Flynn.

[toc] | [prev] | [next] | [standalone]

#97307

In message <slrno3hg67.8d4.timmcn@sugaree.local> 
  Tim McNamara <timmcn@bitstream.net> wrote:
> Today I got my first and second Calendar.app spam on my Mac, from a Web 
> site that purports to sell Ugg boots followed by one purporting to sell 
> RayBans. Since the "organizer's" name for both ads are in Chinese 
> characters, I can only assume that (1) the sites are skeezy at best and 
> (2) Apple has created a huge fucking hole in the OS to allow this sort 
> of bullshit.

Yeah, Apple created the whole spammer problem, damn them! It's ALL THEIR
FAULT.

Please.

There are spammers. They are fucking shits who deserve having their
fingers smashed to bits with large mallets. But, since we can't do that
we deal with the spam.

Having a tizzie fit and stamping your precious foot about how evil
non-spammer company is makes you look like a fool.

tl;dr: Don't let the door hit you too hard on the ass on your way out.


-- 
I NO LONGER WANT MY MTV Bart chalkboard Ep. 3G02

[toc] | [prev] | [next] | [standalone]

#97328

On Sat, 26 Nov 2016 00:53:46 -0000 (UTC), Lewis 
<g.kreme@gmail.com.dontsendmecopies> wrote:
>
> Yeah, Apple created the whole spammer problem, damn them! It's ALL 
> THEIR FAULT.
>
> Please.
>
> There are spammers. They are fucking shits who deserve having their 
> fingers smashed to bits with large mallets. But, since we can't do 
> that we deal with the spam.

And Apple doesn't have to facilitate the the spamers by default.  That's 
the problem here.

Simple solution: the default setting should be that you can only send me 
calendar events and have them entered *if I invite you.*

My Google calendar has not (yet) shown this problem.

> Having a tizzie fit and stamping your precious foot about how evil 
> non-spammer company is makes you look like a fool.
>
> tl;dr: Don't let the door hit you too hard on the ass on your way out.

Oh, gee, that's put me in my place.  LOL!

[toc] | [prev] | [next] | [standalone]

#97329

On 2016-11-26 15:01, Tim McNamara wrote:

> Simple solution: the default setting should be that you can only send me
> calendar events and have them entered *if I invite you.*

Chicken and egg.

-- 
She hummed to herself because she was an unrivaled botcher of lyrics.
   -Nick (Gone Girl), Gillian Flynn.

[toc] | [prev] | [next] | [standalone]

#97330

In message <slrno3jqh6.941.timmcn@sugaree.local> 
  Tim McNamara <timmcn@bitstream.net> wrote:
> On Sat, 26 Nov 2016 00:53:46 -0000 (UTC), Lewis 
> <g.kreme@gmail.com.dontsendmecopies> wrote:
>>
>> Yeah, Apple created the whole spammer problem, damn them! It's ALL 
>> THEIR FAULT.
>>
>> Please.
>>
>> There are spammers. They are fucking shits who deserve having their 
>> fingers smashed to bits with large mallets. But, since we can't do 
>> that we deal with the spam.

> And Apple doesn't have to facilitate the the spamers by default.  That's 
> the problem here.

> Simple solution: the default setting should be that you can only send me 
> calendar events and have them entered *if I invite you.*

Yeah, they used to do that. They got way too many complaints from people
who were not getting their meeting invites and the default was changed.

> My Google calendar has not (yet) shown this problem.

Hah! I stopped using Google calendars a few years ago because of the
constant pollution from spammers.

-- 
You came in that thing? You're braver than I thought!

[toc] | [prev] | [next] | [standalone]

#97331

On 2016-11-26 20:01:34 +0000, Tim McNamara <timmcn@bitstream.net> said:

> My Google calendar has not (yet) shown this problem.

Not calendar, but:

	https://www.seroundtable.com/archives/019318.html

(that's a Google Docs spam article from *2009* and from recent reports 
I have seen it's still an ongoing problem.  Google hasn't solved it in 
~seven years - now that's something to get outraged about)

A.

[toc] | [prev] | [next] | [standalone]

#97334

On 2016-11-26, Tim McNamara <timmcn@bitstream.net> wrote:
>
> And Apple doesn't have to facilitate the the spamers by default.  That's 
> the problem here.

Yes, the problem is one of trust. Apple designed this feature naively,
and people are using it for nefarious purposes. Due to the fact that
invites are recognized within e-mail messages, people who are untrusted
(strangers) are being allowed to send invitations to you, which your
computer then automatically adds to your calendar.

> Simple solution: the default setting should be that you can only send
> me calendar events and have them entered *if I invite you.*

If it were me, I would only allow invites to be added if the sender is
in your contacts. I'd provide a preferences setting to allow users to
optionally allow even invites from strangers to be added to their
calendars. And I'd even consider adding an option to "ask" (display a
dialog) each time to let the user decide on a case-by-case basis:

Automatically add invited events to my calendar:
* Only from my contacts 
* From anyone
* After asking me

And I would let the user ignore any event /without/ notifying the host
at *any* time.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#97433

On 27 Nov 2016 00:48:40 GMT, Jolly Roger <jollyroger@pobox.com> wrote:
>
> And I would let the user ignore any event /without/ notifying the host 
> at *any* time.

That would be good- a one tap approach.

I got a spam text today (interestingly enough I was in a business 
meeting with another Apple iPhone owner who got the same spam text 
within a second of me).  Unlike the calndar spam, this was flagged as 
being from someone not in my address book, coming through my iCloud 
account and having an option to report it as spam.

[toc] | [prev] | [next] | [standalone]

#97323

For your reference, records indicate that 
Tim McNamara <timmcn@bitstream.net> wrote:

> Today I got my first and second Calendar.app spam on my Mac,

You don’t do a very good job in explaining what this is.  Alan suggested 
it might just be Mail pulling events out of a regular (unfiltered?) 
spam.  If that’s the case, Mail already has a preference to stop that.  
If it’s something else, you really need to describe the avenue used by 
the spammer to access your calendars.

> Also, WTF is the seller thinking?  This is only going to really piss off 
> every person who gets this; there will be zero sales from this.  So 
> either the would-be seller is an idiot or the goal must be something 
> else- confirming working iCloud accounts or e-mail addresses, perhaps, 
> since they get a notification when the victim declines the invite?  
> Phishing for something else than sales?

Spam stopped being a first-order issue a long time ago.  It has almost 
nothing to do with actual sales and everything to do with the spammer 
convincing someone that the *potential* for new sales outweighs the 
costs.  If it does, the spammer gets repeat business from that same 
client.  If it doesn’t, there’s always another sucker to move on to, 
because the constant flow of spam convinces some people that spam 
*must* work.

I have no idea what the true nature is of the problem you’re seeing.  
I have no idea what you’re doing that allows spammers to contact you 
in any fashion.  You have yet to make the case that Apple is at fault.  
I say that as a person who has *provably* been spammed via Apple:

https://www.impossiblystupid.com/node/122/?content=apple-sells-me-out

-- 
"Also . . . I can kill you with my brain."
River Tam, Trash, Firefly

[toc] | [prev] | [next] | [standalone]

#97324

On 2016-11-26, Doc O'Leary <droleary@2015usenet1.subsume.com> wrote:
> I say that as a person who has *provably* been spammed via Apple:
>
> https://www.impossiblystupid.com/node/122/?content=apple-sells-me-out

Nope. There's no proof there that Apple sold or gave your address to
anyone.  Often spammers will blindly send messages to addresses they
don't even know exist, routinely using dictionary words in different
combinations with random or sequential numbers or other characters for
user names, where they send messages to a huge list of user names at a
given host just to see what bounces. It's quite possible your address
was part of one of those operations and had nothing at all to do with
Apple specifically. Until you rule that out, you can stop pointing your
finger at Apple over this.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#97367

Jolly Roger <jollyroger@pobox.com> wrote:

> On 2016-11-26, Doc O'Leary <droleary@2015usenet1.subsume.com> wrote:
> > I say that as a person who has *provably* been spammed via Apple:
> >
> > https://www.impossiblystupid.com/node/122/?content=apple-sells-me-out
> 
> Nope. There's no proof there that Apple sold or gave your address to
> anyone.  Often spammers will blindly send messages to addresses they
> don't even know exist, routinely using dictionary words in different
> combinations with random or sequential numbers or other characters for
> user names, where they send messages to a huge list of user names at a
> given host just to see what bounces.

I also got three items of "calendar spam" in the last few days, almost
certainly via iCloud. Thanks nospam for the tip about where to disable
the feature.

One of them which I looked at more closely had a visible list of
recipients. My iCloud account was among dozens of seemingly random
alphabetically nearby account names in @icloud.com. Looked like trolling
for valid addresses.

> It's quite possible your address was part of one of those operations and
> had nothing at all to do with Apple specifically. Until you rule that out,
> you can stop pointing your finger at Apple over this.

Agreed.

-- 
David Empson
dempson@actrix.gen.nz

[toc] | [prev] | [next] | [standalone]

#97391

For your reference, records indicate that 
dempson@actrix.gen.nz (David Empson) wrote:

> Jolly Roger <jollyroger@pobox.com> wrote:
> 
> > It's quite possible your address was part of one of those operations and
> > had nothing at all to do with Apple specifically. Until you rule that out,
> > you can stop pointing your finger at Apple over this.
> 
> Agreed.

No.  JR is an idiot who makes wild assumptions; agree with him at your 
own risk.  I, on the other hand, run my own mail server and generate 
email addresses in a variety of very specific ways.  I’d know if someone 
was just trying to dictionary attack me (and, hell, I even see that for 
SSH all the time).  But I get isolated email messages to very specific 
addresses, so I *know* what has happened in those cases.

-- 
"Also . . . I can kill you with my brain."
River Tam, Trash, Firefly

[toc] | [prev] | [next] | [standalone]

#97393

On 2016-11-28, Doc O'Leary <droleary@2015usenet1.subsume.com> wrote:
> For your reference, records indicate that 
> dempson@actrix.gen.nz (David Empson) wrote:
>
>> Jolly Roger <jollyroger@pobox.com> wrote:
>> 
>> > It's quite possible your address was part of one of those operations and
>> > had nothing at all to do with Apple specifically. Until you rule that out,
>> > you can stop pointing your finger at Apple over this.
>> 
>> Agreed.
>
> No.  JR is an idiot

Since you've decided to descend into personal insult territory, I'll go
ahead and retort: Takes one to know one. 

Here's a prime example of idiocy: Holding a grudge against company X
based purely on the flawed assumption that merely receiving an email
message means company X gave your address away - especially considering
the software algorithms spammers use to generate addresses are well
known in the tech community, and those algorithms clearly make it
possible (even easy) to spam literally any address on any domain. Such
is the nature of email, whether you want to believe it or not.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#97423 — SSH to another port (was Re: Calendar spam!)

[Multipart message — attachments visible in raw view] — view raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday, 28 November 2016 02:48 -0000, 
 in article <o1g5t5$puh$2@dont-email.me>, 
 Doc O'Leary <droleary@2015usenet1.subsume.com> wrote:

> I’d know if someone was just trying to dictionary attack me (and, 
> hell, I even see that for SSH all the time).

Try setting up your router to forward the port of your choosing to 
port 22.  Alternatively, you could choose to have sshd run using a 
different port.  I assure you, you'll see a dramatic drop in the 
number of rejected ssh login attempts as root and the contents of the 
dictionary.

- -- 
David Ritz <dritz@mindspring.com>
 Be kind to animals; kiss a shark.

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAlg8up0ACgkQUrwpmRoS3utF/wCbBxZDHcHvooAY6AwMwhi4iA17
4IEAoJy3DnCTpTEiUgcqXQ1elQd0+2GZ
=2AjU
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#97435 — Re: SSH to another port (was Re: Calendar spam!)

For your reference, records indicate that 
David Ritz <dritz@mindspring.com> wrote:

> Try setting up your router to forward the port of your choosing to 
> port 22.  Alternatively, you could choose to have sshd run using a 
> different port.  I assure you, you'll see a dramatic drop in the 
> number of rejected ssh login attempts as root and the contents of the 
> dictionary.

Why would I do that?  I *want* to know who is trying to attack my 
system, and how.  That’s part of the point in using unique emails, 
too.  That’s why I don’t do any spam filtering, either.  It is a 
mistake to think of abuse on a per-port or per-IP basis.  If someone 
is enough of a bother, they get their whole network dropped into the 
firewall.

-- 
"Also . . . I can kill you with my brain."
River Tam, Trash, Firefly

[toc] | [prev] | [next] | [standalone]

#97438 — Re: SSH to another port (was Re: Calendar spam!)

On 2016-11-29 14:21:53 +0000, Doc O'Leary  
<droleary@2015usenet1.subsume.com> said:

> Why would I do that?  I *want* to know who is trying to attack my
> system, and how.

For those of us not in (or no longer in) security research, the answer 
is "life's too short".  I used to dutifully review my firewall logs and 
investigate all those IP addresses.  I quickly learned that someone, 
somewhere, is constantly checking to see if the door is locked - a 
million passing fingers testing the doorknob on their way by.  I just 
switched my inbound SSH port*.  The logs got a lot smaller, and I 
invested that time in making sure the door was locked.

Regarding email addresses, I used a vendor-specific email scheme for 
many years.  Only two email addresses out of the hundreds were 
subsequently used for spam, which would indicate that spammers are not 
exceptionally energetic when trying to guess new victims' addresses.  
Were those two guessed or leaked, who can say?

A.

* In today's world, I no longer think it is acceptable to have any 
ports open at home.  If you must, I recommend an inbound IPsec VPN.  
Personally, I simply do without.

[toc] | [prev] | [next] | [standalone]

#97441 — Re: SSH to another port (was Re: Calendar spam!)

In message <o1kf4o$lhh$1@dont-email.me> 
  Alrescha <alrescha@gmail.com> wrote:
> * In today's world, I no longer think it is acceptable to have any 
> ports open at home.  If you must, I recommend an inbound IPsec VPN.  
> Personally, I simply do without.

I run servers at home, so I have the usual set of ports open.


-- 
There is a road, no simple highway, between the dawn and the dark of
night

[toc] | [prev] | [next] | [standalone]

#97450 — Re: SSH to another port (was Re: Calendar spam!)

On 2016-11-29 21:47:56 +0000, Lewis <g.kreme@gmail.com.dontsendmecopies> said:

> I run servers at home, so I have the usual set of ports open.

If you need it, you need it.  I occasionally miss having access to my 
IMAP server when I am out and about, but not often enough to make me 
expose the port.

A.

[toc] | [prev] | [next] | [standalone]

#97464 — Re: SSH to another port (was Re: Calendar spam!)

For your reference, records indicate that 
Alrescha <alrescha@gmail.com> wrote:

> On 2016-11-29 14:21:53 +0000, Doc O'Leary  
> <droleary@2015usenet1.subsume.com> said:
> 
> > Why would I do that?  I *want* to know who is trying to attack my
> > system, and how.
> 
> For those of us not in (or no longer in) security research, the answer 
> is "life's too short".

Well, you *do* know they make computers to handle that sort of thing, 
right?  :-). I let fail2ban do most of the work when it comes to 
keeping out the riffraff.  And I sleep better at night knowing that I 
already cut off the jerk who was trying to do a drive-by on my SSH 
last week from trying to find an PHP exploit *this* week.  It’s not 
just an abstract gathering of evidence for research purposes, it is 
simply best practices for ongoing security.

> Were those two guessed or leaked, who can say?

Everyone who has the evidence can say.  Sure, it may not matter a 
great deal for minor accounts you have on random web sites, but I’ve 
had the misfortune of having financial institutions leak my info, and 
*everyone* who had a clue took it much more seriously when multiple 
people using unique addresses report the same issue.

Spammers don’t generally “guess” anything.  They have a limited number 
of tries at doing that sort of thing before alarm bells ring at any 
competently run organization.  They’ll be happy enough if the emails 
that are *on* a list they buy work.  Closest I ever see to a 
dictionary attack are a couple lame tries at sales@ or info@ 
addresses.

-- 
"Also . . . I can kill you with my brain."
River Tam, Trash, Firefly

[toc] | [prev] | [next] | [standalone]

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

Back to top | Article view | comp.sys.mac.system

csiph-web