News for hackers. Stuff that matters.
Re:FCC must reveal IP addresses and user-agent headers of ne... by ogre_codes on Monday May 04, 2020 @04:59PM (#23073176)
> Second, the FCC objects to producing the relevant materials from the API proxy server log because to do so requires creating a script, which demands "research" rather than simply a "search."

Funny how a government agency considers it overly burdensome to write what is likely a 4 line script, so goes through a lawsuit that costs taxpayers likely millions of dollars to avoid it. Unless their infrastructure is well and truly F*ed, this is a 30-60 minute task for a junior server admin. Most likely they already ran it and didn't like what it revealed so it's even less effort.

Re:FCC must reveal IP addresses and user-agent headers of ne... by pc86 on Monday May 04, 2020 @05:10PM (#23073297)
Don't underestimate the absolutely jaw-dropping incompetence from even senior "tech" folks employed by governments.

Within the last couple years, I've overheard senior, so-called technical government employees 1) complain about Git and wonder aloud why we weren't using Visual Source Safe; 2) insist that rotating through a list of 12 hard-coded passwords, in code, checked into Git, was totally fine; 3) refuse to believe that automated deployments were possible (not hard, or against norms, but physically impossible); 4) try to explain to another so-called technical gov't employee the difference between CSS and JavaScript, and get it wrong; 5) stand up in the middle of a conversation and walk out the door because it's 2:30 PM and their day is over; 6) even more nonsense you wouldn't believe if I showed you a video of it.

I would hope Federal is a little better than State, but I'm not convinced.

Re:FCC must reveal IP addresses and user-agent headers of ne... by goostavos on Monday May 04, 2020 @06:12PM (#23073977)
Number 5 sounds kind of nice, actually.

I worked with Federal briefly. I was at a startup at the time, and we had this integration with the Dept. Homeland Security. I was young and stoked. I was the one who was going to wire everything together. It seemed really big and important. I thought it'd be a gold star on my resume.

Reality was super disappointing. So much "we're working on a document for when we can give a date for a date on another document" kind of bureaucracy. I'm sure down in the deep cores of these agencies there are super bright and talented people. The ones at the edges, though.. the problem seems to be that you have to be more of a politician than an engineer to actually get anything done.

Re:FCC must reveal IP addresses and user-agent headers of ne... by shrimp_emoji on Monday May 04, 2020 @06:59PM (#23074367)
>seems to be that you have to be more of a politician than an engineer to actually get anything done.

In Red Mars, they try to colonize Mars. At first, the challenges are completely technical, and the engineers prevail. But the success is chased by increasing bureaucracy and involvement of stakeholders, and it quickly becomes all politics. c:

Re:FCC must reveal IP addresses and user-agent headers of ne... by ethbro on Monday May 04, 2020 @07:27PM (#23074583)
> But the success is chased by increasing bureaucracy and involvement of stakeholders, and it quickly becomes all politics.

And then quickly becomes colonial revolution.

Re:FCC must reveal IP addresses and user-agent headers of ne... by JaimeThompson on Monday May 04, 2020 @05:29PM (#23073526)
To be fair I know of people in private industry who have said some of the exact same things. It isn't limited to just government employees.
Re:FCC must reveal IP addresses and user-agent headers of ne... by pc86 on Monday May 04, 2020 @06:29PM (#23074123)
If you work for a modern software company (not a service company that sells software), and you honestly suggest Visual Source Safe, you'll get fired. There's just no reasonably intelligent reason to suggest it.

You practically have to assault someone in the break room to get fired from a government job.

Re:FCC must reveal IP addresses and user-agent headers of ne... by JeremyNT on Monday May 04, 2020 @06:44PM (#23074254)
But if your org is using $oldtech and some new person comes in recommending $newtech, you'll be in great company if you argue that $newtech sucks and you wish you could just keep using $oldtech.

Organizational inertia is definitely a thing, and technology trends do not move as quickly in all sectors.

Re:FCC must reveal IP addresses and user-agent headers of ne... by tomc1985 on Monday May 04, 2020 @09:42PM (#23075486)
But how good is $newtech really? Is it someone trying to screw over other older employees in the name of his job security? Is Mr. $newtech in touch with the salespeople hawking this product? Is he being incentivized to advocate for it? How many secondary changes will $newtech result in, and will they deliver so much more value as to justify the expense, inconvenience, retraining, and tears that will come from replacing $oldtech?

My guess is, in most circumstances, probably not

"New tech" lately feels more and more like whatever the next breed of inexperienced geeks decided to reinvent

Re:FCC must reveal IP addresses and user-agent headers of ne... by gregoryl on Monday May 04, 2020 @10:39PM (#23075825)
Well, to move back from the abstraction, Visual Source Safe is truly awful, and you're never safe from it losing your code :)
Re:FCC must reveal IP addresses and user-agent headers of ne... by stult on Tuesday May 05, 2020 @05:48AM (#23078220)
Whatever your perspective on fad-chasing in software development, some things just suck down through the ages...
Re:FCC must reveal IP addresses and user-agent headers of ne... by erik_seaberg on Tuesday May 05, 2020 @04:38AM (#23077823)
I worked for a startup with ex-Microsoft management in the 1990s, so we used VSS. All joking aside, we actually did lose about a day's work to that pile of fun.

I'm told that at this point sales will quietly try to talk you out of buying it.

Re:FCC must reveal IP addresses and user-agent headers of ne... by barbecue_sauce on Monday May 04, 2020 @07:30PM (#23074609)
Would you get fired, or would people just assume you were being sarcastic?
Re:FCC must reveal IP addresses and user-agent headers of ne... by to11mtm on Monday May 04, 2020 @07:41PM (#23074686)
I'd ask whether to set up the build pipeline for VB6 or ASMX Services, lol
Re:FCC must reveal IP addresses and user-agent headers of ne... by dan-robertson on Tuesday May 05, 2020 @03:21AM (#23077382)
You would not get fired. Probably everyone would forget you even said it.

If you want people in a company to be able to produce good ideas, they must have reasonable leeway to disagree or be contrarian.

Re:FCC must reveal IP addresses and user-agent headers of ne... by pc86 on Monday May 04, 2020 @07:40PM (#23074675)
> > honestly
Re:FCC must reveal IP addresses and user-agent headers of ne... by a1369209993 on Monday May 04, 2020 @11:51PM (#23076304)
The question isn't whether you honestly suggest it; the question is whether they believe you when you express sincerity.
Re:FCC must reveal IP addresses and user-agent headers of ne... by bcrosby95 on Monday May 04, 2020 @08:30PM (#23075009)
> 5) stand up in the middle of a conversation and walk out the door because it's 2:30 PM and their day is over;

My dad would do the same stuff. He worked at Samsung. When he got into his 50s, it was like a switch turned on and he just wouldn't stay beyond a standard work day. Got a meeting you scheduled late in the day? Too bad, he was there at 6am and was going home. He was always home at the same time.

In comparison, during this period of time my mom would go into the office at 8am and stay as late as 1am. She would even pick up 2nd dinner for me on her way home.

Re:FCC must reveal IP addresses and user-agent headers of ne... by pc86 on Monday May 04, 2020 @08:38PM (#23075069)
There's a difference between saying "I saw you scheduled a meeting for 2-3, just so you know my day is over at 2:30, can we reschedule?" (which I have done, and will always do), and cutting someone off mid-sentence to say your day is over because your clock beeped, and being out the door and in your car 15 seconds later.
Re:FCC must reveal IP addresses and user-agent headers of ne... by a1369209993 on Monday May 04, 2020 @11:56PM (#23076328)
Sure, but the latter is completely resonable when the person scheduling the meeting is a pointer-haired twit who would respond to the former with "sure, sure, sounds good" <later> "okay, we rescheduled for 2:00-3:00", which from what I've seen/heard seems to be typical of government work.
Re:FCC must reveal IP addresses and user-agent headers of ne... by linuxftw on Monday May 04, 2020 @11:55PM (#23076319)
Often times government contractors aren't authorized to work overtime. It's illegal to do unpaid work.
Re:FCC must reveal IP addresses and user-agent headers of ne... by nroach on Tuesday May 05, 2020 @11:23AM (#23080979)
Some people that work early-shifted days do so because they have child care obligations. Many day cares charge by the minute for late pick-ups. So an abrupt departure may not be 100% attributable to laziness. Failure to communicate those constrains ahead of the meeting very well might be.
Re:FCC must reveal IP addresses and user-agent headers of ne... by rapind on Tuesday May 05, 2020 @04:20PM (#23084525)
On the flip side, does your employer care if you clock out at 2:25 because you're bored? I bet some employers (like large bureaucracies) don't like that. We lack context.
Re:FCC must reveal IP addresses and user-agent headers of ne... by fanatic2pope on Monday May 04, 2020 @11:34PM (#23076209)
I've seen worse in private companies. For example I once did some consulting for a company that manages an industrial production line using software written by a single "rock star" programmer leading a team of imbeciles. Dude is adamantly opposed to version control and his "process" for deploying new code to production hardware is to manually rename the active version to .BAK and copy over the new one. He keeps track of versions by remembering which computer has which version installed. This is in a company where if the line goes down, it's hundreds of thousands of dollars an hour till it comes back up.
Re:FCC must reveal IP addresses and user-agent headers of ne... by na85 on Monday May 04, 2020 @06:30PM (#23074129)
>Don't underestimate the absolutely jaw-dropping incompetence from even senior "tech" folks employed by governments.

When I was in training with the RCAF, I was in lecture where the Information Systems Security Officer (i.e. the senior most infosec person at this base of 6-8000 people) told us about a time where "two guys were emailing back and forth and just picked up a virus".

I made the mistake of pointing out that that's not really how computers work, i.e. an email can't just pick up a virus in transit like a dog picks up a tick.

I learned two lessons that day:

1. Militaries don't like it when people stand out

2. Governments are fundamentally incompetent

Re:FCC must reveal IP addresses and user-agent headers of ne... by dallasgutauckis on Monday May 04, 2020 @07:00PM (#23074379)
Sounds like those two guys were man-in-the-middled
Re:FCC must reveal IP addresses and user-agent headers of ne... by CamperBob2 on Monday May 04, 2020 @07:44PM (#23074706)
When you hear hoofbeats, think horses, not zebras.
Re:FCC must reveal IP addresses and user-agent headers of ne... by na85 on Monday May 04, 2020 @07:06PM (#23074424)
Or, you know, the guy caught some malware through an entirely separate vector.
Re:FCC must reveal IP addresses and user-agent headers of ne... by barbecue_sauce on Monday May 04, 2020 @07:31PM (#23074627)
My firewall protects you, and your firewall protects me.
Re:FCC must reveal IP addresses and user-agent headers of ne... by ThePowerOfFuet on Tuesday May 05, 2020 @05:50AM (#23078236)
Ain't the CF grand?
Re:FCC must reveal IP addresses and user-agent headers of ne... by na85 on Tuesday May 05, 2020 @09:54AM (#23080028)
Nope. It's a joke of a military that can't possibly defend Canada. The people and the technology are all obsolete.
Re:FCC must reveal IP addresses and user-agent headers of ne... by ogre_codes on Monday May 04, 2020 @05:34PM (#23073588)
Regardless of how incompetent they are. Incompetence should not be the benchmark for which terms like "Reasonable Burden" are applied against.
Re:FCC must reveal IP addresses and user-agent headers of ne... by nickff on Monday May 04, 2020 @06:01PM (#23073854)
Each part of the government tends to give a great deal of deference to the other parts of the government.
Re:FCC must reveal IP addresses and user-agent headers of ne... by refurb on Monday May 04, 2020 @09:10PM (#23075296)
This reminds me of when I worked on a public policy project for a biotech company. Our product didn't fit in the current Medicare policies, so we decided to approach Medicare and suggest a solution.

Medicare spent months just digging into the laws and talking to their lawyers just to prove they actually had the jurisdiction to change the policy. That really blew me away. One of their bigger concerns was "this might not be our job".

Re:FCC must reveal IP addresses and user-agent headers of ne... by prostheticvamp on Monday May 04, 2020 @11:10PM (#23076048)
CMS, as a regulatory agency, does have a high priority in making sure it’s got the legal right to make regulations pertaining to a thing. Because otherwise those regs are illegal, which causes lawsuits and chaos.

You make it sound like they spent months trying to finagle a way out of working.

Re:FCC must reveal IP addresses and user-agent headers of ne... by fedthrowaway on Monday May 04, 2020 @06:37PM (#23074195)
Throwaway account because I still work this job.

> Don't underestimate the absolutely jaw-dropping incompetence from even senior "tech" folks employed by governments.

100% agree. Except each agency can significantly change on this. Some agencies (DEA, USCIS) can and are completely competent. I've seen then turn around on certain moderately complex tasks within hours.

Then you have the idiots at HISN and VA that takes a year for even basic one-way integration. Or, they will argue with you how SAML works (or doesnt) for weeks at a time.

> 1) complain about Git and wonder aloud why we weren't using Visual Source Safe;

Ah so you were talking with their developers. Sounds DoD'ish as that's what they use, along with Firebird.

> 2) insist that rotating through a list of 12 hard-coded passwords, in code, checked into Git, was totally fine;

Ive dealt with network infrastructure entities that did similar for the commercial side of things. I wish it were the "OMG" exception. There's more terrible out there than this, admittedly.

> 3) refuse to believe that automated deployments were possible (not hard, or against norms, but physically impossible);

Well, they ARE impossible by policy. FedRAMP and FISMA requires manual and intentional deployments. Of course we all know that this is the norm for a software SaaS company - but its not the norm when you have to go through a VPN with a CAC or PIV card, and then another VPN to either the testnet or prodnet... And the only software support for both are Windows. (And the VPNs will also kick you out if you're not running windows.)

> 4) try to explain to another so-called technical gov't employee the difference between CSS and JavaScript, and get it wrong;

I've had screaming fights break out in calls when technical issues came up like this. And usually its the single real employee screaming at the legions of 3rd party contractors. And also, Snowden was correct in that 95% of the "government employees" aren't. They are contractors working for Accenture or the host of other Gino (govt in name only) employees. They don't get govt benefits, nor do they have whistleblower protections. Snowden in Hawaii was such a 3rd party govt employee.

I have only ran across 1 fed employee (contractor or real) that was in any way and shape competent.

> 5) stand up in the middle of a conversation and walk out the door because it's 2:30 PM and their day is over;

I get your point. But it's usually 4p. Ive also seen government employees (employed by the local/state/fed) get in trouble for working non-critical issues outside their hours.

> 6) even more nonsense you wouldn't believe if I showed you a video of it.

One thing I've learned is that there is almost always a reason (and a decent one too) of why there is a rule. It's because someone previously abused something, or did something that broke stuff, and the new rule is the usual overcompensation so that anybody in power can claim "They didnt follow our rules, which protect against that." And remember, it's not far up the foodchain to an elected official.

But yeah, there's absolutely crazy shit out there, especially in the fed side of things. And much of it is for complete show. One such tempest in a teacup issue is the new (as of 2017) NIST password guidelines: not a single fed has implemented them. They still enforce the old and terrible ruleset.

Re:FCC must reveal IP addresses and user-agent headers of ne... by pc86 on Monday May 04, 2020 @08:00PM (#23074822)
Loved your insights here. I never contracted for DOD, this was for a handful of state agencies in Pennsylvania.
Re:FCC must reveal IP addresses and user-agent headers of ne... by westmeal on Tuesday May 05, 2020 @01:56AM (#23076947)
This most likely explains why I didn't get a dime of my unemployment money. Thanks PA.
Re:FCC must reveal IP addresses and user-agent headers of ne... by count on Monday May 04, 2020 @09:34PM (#23075440)
Where do FedRAMP/FISMA require manual deployments?
Re:FCC must reveal IP addresses and user-agent headers of ne... by nl on Tuesday May 05, 2020 @03:22AM (#23077387)
Totally made up answer ahead, but based on lived experience in a different country.

It probably happened like this: In 1995 people started planning for this Y2K bug. Some developer said "Nah it's not an issue I'll just change this field" so they changed it like they change everything else, and then 6 months later people got paid the wrong amount because a date calculation was wrong.

So they went looking for someone to blame. They fire the developer of course, but they want someone responsible, who signed off on the release. There was no one, so and with the biggest software fixing exercise in their history coming up they figured they should make sure this problem didn't happen again.

So they introduced sign-off procedures, where someone above a certain level had to sign off on things.

And that is how manual deployments are "banned". They probably aren't exactly, but some poor person will have to put their job on the line to sign off on automating them.

Re:FCC must reveal IP addresses and user-agent headers of ne... by count on Sunday May 10, 2020 @04:39PM (#23135969)
'sign off' procedures, and 'automated deployments' are not different ends of the spectrum.

Nobody who gives a shit about their product/service is deploying from a developer directly into production without any kind of, you know, code review, pipeline testing, etc.

It's 'automated' in that you git push. The pipeline handles code reviews, sign-offs, etc., and then automatically deploys the approved code change.

This isn't banned at all.

Just randomly pushing shit to production is banned (separation of concerns, amongst other controls). You can still have everything be fully automated, just not fully autonomous. Someone reviewing a change and then clicking 'LGTM' is still an automated, continuously integrated and deployed system.

Re:FCC must reveal IP addresses and user-agent headers of ne... by a1369209993 on Tuesday May 05, 2020 @12:07AM (#23076381)
Because someone, somewhere, sometime years/decades ago, auto-deployed buggy/incomplete code to production, and it destroyed something important, and the 'solution' they came up with was "all deployments must be conducted manually by team lead^W^Wan approved engineer^W^W^Wsome random shmuck".
Re:FCC must reveal IP addresses and user-agent headers of ne... by count on Sunday May 10, 2020 @04:40PM (#23135971)
'Where', not 'why'.

I know 'why' people might think that, and make assumptions. The actual controls are pretty level headed though.

Re:FCC must reveal IP addresses and user-agent headers of ne... by echelon on Monday May 04, 2020 @07:22PM (#23074544)
> Don't underestimate the absolutely jaw-dropping incompetence from even senior "tech" folks employed by governments.

How do we replace them with folks that know what they're doing? It almost sounds like it would be better for the government to outsource to a tech firm.

These people have huge salaries and pensions, too, right?

Re:FCC must reveal IP addresses and user-agent headers of ne... by pc86 on Monday May 04, 2020 @07:51PM (#23074764)
You let government fire incompetent people, which is very hard to do with unions like AFSCME in place, in part because "incompetent" in this context is extremely subjective. I'm not saying unions are bad but they do make it objectively harder to fire these borderline folks.

Huge salaries? No. The agencies I contracted for topped out for senior folks in the $85-90k range while the same title in the private sector is going to be about 40-50% higher than that. They have pensions but unless you're already 15 years in you really need to work the system to get anything out of it. New hires (rightly) have to put a lot of money into the system so it's not much better than a private retirement plan in terms of returns, however it is guaranteed by the taxpayers.

There are exceptions, though. If you're retiring from any of the agencies I contracted for, and you worked there your entire career, you're probably getting a lump sum $80-100k vacation time payout and anywhere from $60-100k/yr for the rest of your life depending on your exact job. This is in addition to whatever personal retirement accounts you might have. Obviously no 401(k) with the pension in place, but it was not unheard to have some of the higher ups cashing in just enough vacation every year to fully fund their Roth.

So yeah you can set up a nice retirement nest egg if you're willing to commit to the state (at least where I live). But for short term stuff it's terrible. You don't even vest any pension benefits until I think 5 years now, and then you're getting something like 5-10% from age 70 on or something.

Re:FCC must reveal IP addresses and user-agent headers of ne... by pottertheotter on Monday May 04, 2020 @11:20PM (#23076120)
Does that mean these people never take vacations? Or do they get a ton of vacation time?
Re:FCC must reveal IP addresses and user-agent headers of ne... by s1artibartfast on Tuesday May 05, 2020 @12:36AM (#23076542)
Based on my observations, too much vacation to take.

State employees with 25 years get 54 days of leave a year[1] and 10 federal holidays. Additionally many agencies work 9 hour days, adding every other friday off, for an extra 26 days. All told, that is 90 days off a year, or more than 1 in 3 work days.

https://www.calhr.ca.gov/employees/Pages/vacation-vs-annual-...

Re:FCC must reveal IP addresses and user-agent headers of ne... by echelon on Tuesday May 05, 2020 @01:50AM (#23076921)
I am incredibly jealous and somewhat outraged.

$80k/yr with pension benefits and a third of your work days off is better than a lot of private sector comp. I'd happily take that last benefit.

Re:FCC must reveal IP addresses and user-agent headers of ne... by s1artibartfast on Tuesday May 05, 2020 @09:04AM (#23079562)
I wanted to correct myself, the vacation and annual leave I linked to are not additive. Annual leave is the greater of the two and 30 days opposed to 54. This would be a total of 66 vacation days.
Re:FCC must reveal IP addresses and user-agent headers of ne... by munk-a on Monday May 04, 2020 @07:40PM (#23074676)
Just to clarify #5 - the hour difference here is suspicious, were you working with an EST person from the west coast? If so scheduling a meeting that overruns 5:30 PM is a pretty unfortunate arrangement.
Re:FCC must reveal IP addresses and user-agent headers of ne... by pc86 on Monday May 04, 2020 @07:57PM (#23074798)
Suspicious how?

The agencies I worked at routinely had employees' shifts ending at various times, anywhere from 2:30 until 5.

Re:FCC must reveal IP addresses and user-agent headers of ne... by ur-whale on Tuesday May 05, 2020 @02:41AM (#23077184)
You just described standard govt competency levels in any field.
Re:FCC must reveal IP addresses and user-agent headers of ne... by btrettel on Monday May 04, 2020 @07:54PM (#23074779)
The FOIA request was probably not denied because the FCC lacks the technical abilities to fulfill the request. In my experience it's likely that no technical people were consulted on it. A FOIA office simply looks for any excuse they can use to deny a request if they want to deny it. The reason doesn't need to make sense or be their true reason.

Here's an example from my own experience:

I can recall a FOIA request I made for the results of searches in an internal government database in spreadsheet format. To my knowledge this can be exported using existing functionality in the web interface for the internal database. The request was denied, and I appealed. They claimed that the information was publicly available, which is absurd. In the appeal I showed that actually almost none of what I wanted was publicly available and the independent appeals office agreed (after a long delay). Then it became clear that the FOIA office thought the request would be burdensome and they tried to deny it on those grounds. I insisted that no, it wouldn't be burdensome.

When it finally went to the person who would actually do the work, apparently it took only a few hours to do, and they declined to charge me anything for it. I assume the majority of that time was writing some useful comments in the headers of the spreadsheets. They didn't need to write the comments, so clearly they weren't pressed for time.

In the end, the FOIA office spent far more time trying to deny this request than it would have taken to fulfill it.

Re:FCC must reveal IP addresses and user-agent headers of ne... by ogre_codes on Monday May 04, 2020 @08:17PM (#23074929)
> A FOIA office simply looks for any excuse they can use to deny a request if they want to deny it. The reason doesn't need to make sense or be their true reason.

That's exactly what I was hinting at here. The agency has no interest in the public finding out how much of that feedback was bullshit.

> In my experience it's likely that no technical people were consulted on it.

From the sounds of it, they did at some point consult someone technical and tried to parse their answer as part of their justification for not executing the FOIA request. The fact that they knew it would take a script to extract the data as opposed to just dropping it into a search tool suggests as much anyhow. Though more likely it would just be a couple `sed` commands, a perl/ Python script, or a few command line tools.

Re:FCC must reveal IP addresses and user-agent headers of ne... by irrational on Monday May 04, 2020 @10:35PM (#23075800)
Once upon a time, my company lawyers came to me and asked me if we had certain historical data that I could pull from a database and how long it would take to pull it. It only took me an hour or so, so I just pulled the data, stuck it in an excel file and sent it to them. They were not happy. Apparently they had already told the judge that the data was unduly burdensome to pull and would take too long.
Re:FCC must reveal IP addresses and user-agent headers of ne... by ikeboy on Monday May 04, 2020 @05:08PM (#23073266)
This is a technical legal point. You can be forced to produce information you have, but generally not to create new information.
Re:FCC must reveal IP addresses and user-agent headers of ne... by ogre_codes on Monday May 04, 2020 @05:32PM (#23073555)
They are arguing that finding data that's in log files is creating new data (because they have to write a script to parse it) which is specious. Logs are designed to be parsed and searched. You might as well claim that running an SQL script to query data is creating new information.
Re:FCC must reveal IP addresses and user-agent headers of ne... by sl1ck731 on Monday May 04, 2020 @06:37PM (#23074189)
That is true but more likely they try to push back against every request that isn't simply zip up files or documents and deposit them.

They are using the "defense" that it may be difficult to do, but their aim (avoiding the more sinister possibilities) is to stop precedent for other unwieldy requests.

Re:FCC must reveal IP addresses and user-agent headers of ne... by ogre_codes on Monday May 04, 2020 @08:21PM (#23074958)
In my experience, government agencies fulfill requests if it's easy and won't put the agency or administration in a bad light. I suspect this falls more into the latter case than the former, they don't want people to see the logs because they know the bulk of the comments are bogus.
Re:FCC must reveal IP addresses and user-agent headers of ne... by kortilla on Monday May 04, 2020 @06:19PM (#23074044)
> Logs are designed to be parsed and searched

You’ve never dealt with a bad log setup. Things I’ve seen:

- inconsistent format depending on which part of the software was logging (think of some modules using logging lib and others using print())

- multiline logs without any indication they are multiline

- logs in some dumb binary format that requires the original software to reverse into legible text

There are more, but the point is that logs are not often designed to be parsed and searched. They are normally added by developers to be human readable means of reversing internal state to debug issues. Anything above that is (shockingly) bonus material that doesn’t make it into home-grown enterprise/govt software.

Re:FCC must reveal IP addresses and user-agent headers of ne... by ogre_codes on Monday May 04, 2020 @06:49PM (#23074297)
> You’ve never dealt with a bad log setup. Things I’ve seen:

I'm not sure how this is relevant. I've seen miles of incompetence in my career, that someone can fudge something up royally doesn't change the fundamental purpose of the thing. The point of log files is to store and make retrievable data about server state and actions over time. That someone somewhere can screw that up doesn't change that.

In this particular case, I find it unlikely they rolled some custom bizarro log file format regardless because of the nature of the subject matter: Proxy server log files. It's unlikely they rolled their own proxy server (and they certainly don't imply any particular difficulties like that in court statements) so we're most likely talking about reading standard Apache logs or something similar.

Re:FCC must reveal IP addresses and user-agent headers of ne... by kortilla on Thursday May 07, 2020 @12:52AM (#23099844)
> The point of log files

That’s a point of log files. However, it’s not the point tons of developers have in mind when they add log statements. Developers are primarily concerned with state required to reproduce bugs, not long term standardized storage containing enough information for useful attribution or even all important state transitions. You would be surprised how many developers don’t even bother logging item deletions because it’s such a trivial code path.

You’re idea of “the fundamental purpose” is from an operators view. It rarely lines up with the developers’ views and you’re in for a bad time if you think people who don’t see your perspective are “fudging something up royally” with “miles of incompetence”.

Re:FCC must reveal IP addresses and user-agent headers of ne... by jatone on Monday May 04, 2020 @07:11PM (#23074461)
uh they're text.... they don't need to be formatted well to be indexed and searched lol.
Re:FCC must reveal IP addresses and user-agent headers of ne... by kortilla on Thursday May 07, 2020 @12:53AM (#23099847)
Uh, you do know a field has to actually be present in a line for it to be indexed? And it has to be consistently formatted placed to be parsed lol.
Re:FCC must reveal IP addresses and user-agent headers of ne... by colejohnson66 on Monday May 04, 2020 @06:14PM (#23073996)
Well, if we’re following that logic, then anytime data is moved from a disk to ram, we’re “creating new data.” Well, yes, it wasn’t there before, so it’s “new data,” but it’s also a copy of old data.
Re:FCC must reveal IP addresses and user-agent headers of ne... by Erwin on Monday May 04, 2020 @07:46PM (#23074724)
There have been some weird legal discussions about whether turning on a computer breaks the copyright depending on who does it:

https://en.wikipedia.org/wiki/MAI_Systems_Corp._v._Peak_Comp....

Re:FCC must reveal IP addresses and user-agent headers of ne... by jacoblambda on Monday May 04, 2020 @09:03PM (#23075242)
That's actually a fairly interesting case. I haven't read into it too much but it seems that they agree that it isn't necessarily a copyright violation based on who does it. It looks like what they got Peak on was instead the fact that they had unlicensed copies of MAI software at their HQ and were loaning MAI equipment in such a way that violated the license agreements.

P.S. Please correct me if I got any of this wrong.

Re:FCC must reveal IP addresses and user-agent headers of ne... by zerocrates on Tuesday May 05, 2020 @02:48AM (#23077219)
There are some details in the case that are as you say, about Peak having "unclean hands" in effect, but they're fairly beside the point for the case's broader significance.

What it really stands/stood for is the notion that a "copy" sufficient for the operation of copyright law occurs when a program is loaded from disk to RAM, and therefore it's possible to infringe copyright merely by using software that you aren't personally licensed for.

MAI basically used this theory to make third-party maintenance of their systems illegal, so Congress responded by amending the Copyright Act, but in an extremely narrow way: there's a carve out specifically for maintenance and repair.

Re:FCC must reveal IP addresses and user-agent headers of ne... by vageli on Monday May 04, 2020 @05:11PM (#23073310)
They have the information (note that they did not contest that point), the script would presumably allow them to surface that information more quickly.
Re:FCC must reveal IP addresses and user-agent headers of ne... by zelon88 on Monday May 04, 2020 @06:37PM (#23074191)
Technically you can open that logfile in Notepad and Ctrl+F the thing. If I was the judge and you pulled that argument someone at your agency would now be using that method instead of "researching" a grep query.
Re:FCC must reveal IP addresses and user-agent headers of ne... by rasengan on Monday May 04, 2020 @07:29PM (#23074604)
How do we know if the IP and headers supplied will be legitimate? There have been other acts in the past [1] that have been covered in government.

[1] https://www.vice.com/en_us/article/4xaqz9/hillary-clinton-te...

Re:FCC must reveal IP addresses and user-agent headers of ne... by erichurkman on Monday May 04, 2020 @07:25PM (#23074573)
And when the Government is on the other side with requests, warrants, and subpoenas, they aggressively push with little regard to cost, complexity, or even feasibility.

If we replied to a lawful order with "This demands 'research' instead of simply a 'search'," they would tell us tough-shit.

Re:FCC must reveal IP addresses and user-agent headers of ne... by SamPatt on Tuesday May 05, 2020 @12:15AM (#23076425)
And that's when they're being "nice."

Otherwise they would send armed men to steal your stuff.

Re:FCC must reveal IP addresses and user-agent headers of ne... by zamalek on Tuesday May 05, 2020 @12:34AM (#23076532)
Realistically fabricating comments/evidence is a much larger script. Once you start lying, you have to keep lying.