On Sat, Dec 07, 2019 at 04:24:33PM -0700, Charles Curley wrote:
> On Sat, 07 Dec 2019 19:20:09 +0100
> Hans wrote:
>
> > maybe owncloud or nextcloud are interesting options for you. As the
> > name says: Your own cloud.
>
> Thank you for recommending those before I did. I run nextcloud here,
> a
On Sat, Dec 07, 2019 at 11:39:42PM +, Brian wrote:
> On Sat 07 Dec 2019 at 18:23:27 -0500, Jude DaShiell wrote:
[Account of break in which we can't either prove or disprove, yet]
> There was no break-in.
That there was no break-in is a myth. You never provided any
evidence. That is enough fo
On Sat, 7 Dec 2019 16:24:33 -0700
Charles Curley wrote:
> On Sat, 07 Dec 2019 19:20:09 +0100
> Hans wrote:
...
> > But in the debian repo I only found the client stuff, however I might
> > to remember, the server site were also available in debian (I might
> > be wrong).
>
> I don't see the s
On Sat, 07 Dec 2019 19:20:09 +0100
Hans wrote:
> maybe owncloud or nextcloud are interesting options for you. As the
> name says: Your own cloud.
Thank you for recommending those before I did. I run nextcloud here,
and prefer it over owncloud. It seems to have advanced considerably
over owncloud
On Sat 07 Dec 2019 at 18:23:27 -0500, Jude DaShiell wrote:
> I had to close my original account as a result of the break in, and you
> know what was really interesting? The account compromise happened after
> I set the account to two-step authentication. For a while it had been a
> lesser securi
I had to close my original account as a result of the break in, and you
know what was really interesting? The account compromise happened after
I set the account to two-step authentication. For a while it had been a
lesser security account.
It's possible the break in happened since at the time I
On Sat 07 Dec 2019 at 16:45:34 -0500, Jude DaShiell wrote:
> One first-hand experience on google account hacking and contacting
> others who were not surprised when I described my situation in earlier
> email.
Widespread breaking into Google accounts is a myth. You and your
correspondents never p
One first-hand experience on google account hacking and contacting
others who were not surprised when I described my situation in earlier
email.
Two, no change password dropbox will not allow login, so not possible to
ignore.
On Sat, 7 Dec 2019, Brian wrote:
> Date: Sat, 7 Dec 2019 15:56:28
> From
On Sat 07 Dec 2019 at 12:06:37 -0500, Jude DaShiell wrote:
> Recently I created a dropbox account with my gmail account. Very shortly
> after creation I was refused access since dropbox claimed someone tried
> to change the password on my account and they weren't sure it was me so
> got prompted
On Friday, December 6, 2019 6:06:10 PM CET, songbird wrote:
result=`echo "summary: \"\"" | sed -e "s/^summary: .*$/summary:
\"${old_summary}\"/"`
of course this doesn't work. since you use '/' (slash) as delimiter in the
sed expression, the slash in $old_summary is interpreted as the delimite
On Vi, 06 dec 19, 14:50:51, Greg Wooledge wrote:
> On Fri, Dec 06, 2019 at 02:40:49PM -0500, songbird wrote:
> > Greg Wooledge wrote:
> > ...
> > > Ideally, you'd just stop trying to use sed with user-supplied variables
> > > injected into the code. Sed was never built to be safe for that kind of
Hi Jude,
maybe owncloud or nextcloud are interesting options for you. As the name says:
Your own cloud.
But in the debian repo I only found the client stuff, however I might to
remember, the server site were also available in debian (I might be wrong).
Best
Hans
signature.asc
Description:
On Vi, 06 dec 19, 14:40:49, songbird wrote:
>
> the point of doing something in bash is to do it quick and
> see if the concept is useful enough. if enough people decide
> to use it then it can be more formalized.
We often build prototypes / proof-of-concept / experiments that live
much longe
On Sat, 7 Dec 2019, Hans wrote:
> Date: Sat, 7 Dec 2019 12:49:17
> From: Hans
> To: debian-user@lists.debian.org
> Subject: Re: dropbox security situation
>
> Am Samstag, 7. Dezember 2019, 18:06:37 CET schrieb Jude DaShiell:
> Hi Jude,
>
> I know, there were several security issues with dropbox i
Am Samstag, 7. Dezember 2019, 18:06:37 CET schrieb Jude DaShiell:
Hi Jude,
I know, there were several security issues with dropbox in the past, that
frightened me. So dropbox would not be my first choice, although it is most
used by people. (Windows is also most used by people, think of your own
Recently I created a dropbox account with my gmail account. Very shortly
after creation I was refused access since dropbox claimed someone tried
to change the password on my account and they weren't sure it was me so
got prompted to change my password.
What I don't know is if high probability exis
On Sat, 7 Dec 2019, at 14:20, songbird wrote:
> The Wanderer wrote:
>
> ... about various characters and then @ in particular ...
>
> > As far as I can see, at least on my keyboard, that pretty much just
> > leaves @. It does still sometimes occur in paths and filenames, so it's
> > not really i
On Sat 07 Dec 2019 at 09:27:59 (-0500), rhkra...@gmail.com wrote:
> On Saturday, December 07, 2019 07:20:35 AM The Wanderer wrote:
> > Yep - using '/' is only a standard convention, it's not required. When
> > writing an s-expression which I know will be passed a path, I generally
> > use '@' mysel
Andrei POPESCU wrote:
...
pre processing for that one character using a different delimiter
and then processing the results of that with the original delimiter
seems to cover everything i'm worried about. :)
> One trick to avoid this problems is to use a different delimiter, e.g. '|'.
>
> Acco
The Wanderer wrote:
... about various characters and then @ in particular ...
> As far as I can see, at least on my keyboard, that pretty much just
> leaves @. It does still sometimes occur in paths and filenames, so it's
> not really ideal, but it's probably less common there than any of the
>
On Saturday, December 07, 2019 07:20:35 AM The Wanderer wrote:
> Yep - using '/' is only a standard convention, it's not required. When
> writing an s-expression which I know will be passed a path, I generally
> use '@' myself; that A: is conveniently typable on the keyboard, B: is a
> comparativel
On 2019-12-07 at 04:43, Andrei POPESCU wrote:
> On Vi, 06 dec 19, 16:15:51, songbird wrote:
>
>> The Wanderer wrote:
>>>
>>> For example, 's/hello/newstring/' would be a valid sed
>>> 's'-expression, but 's/a/b/newstring/' would not; the former
>>> contains three instances of the delimiting toke
On Vi, 06 dec 19, 16:15:51, songbird wrote:
> The Wanderer wrote:
> >
> > For example, 's/hello/newstring/' would be a valid sed 's'-expression,
> > but 's/a/b/newstring/' would not; the former contains three instances of
> > the delimiting token, which is valid, but the former contains four,
> > w
D. R. Evans wrote:
> Nope, all just black.
>
> But I could log in via ssh, and started backing out recent changes (I'm
> not sure how long the problem had existed, as I don't normally look at the
> console screen once X has started).
>
> One of the changes was to switch to the Trinity desktop ma
24 matches
Mail list logo
